From: Matthias Fischer <matthias.fischer@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: Problem building perl on ipfire 2.x on Ubuntu 64 bit...Another try two years later
Date: Wed, 16 Aug 2017 17:48:36 +0200 [thread overview]
Message-ID: <2c19a35a-60a8-f57c-9407-ff7dffcfdc41@ipfire.org> (raw)
In-Reply-To: <1502895580.2543.31.camel@ipfire.org>
[-- Attachment #1: Type: text/plain, Size: 1320 bytes --]
On 16.08.2017 16:59, Michael Tremer wrote:
> Hi,
>
> On Wed, 2017-08-16 at 09:47 -0400, William Pechter wrote:
>> Michael Tremer wrote:
>> > Hello,
>> >
>> > are you trying to build the toolchain here?
>> >
>> > If so, you can just download a pre-compiled one with:
>> >
>> > ./make.sh gettoolchain
>> >
>> > Sometimes it is a bit tricky to compile them on various host
>> > systems.
>> >
>> > Best,
>> > -Michael
>> >
>> > On Wed, 2017-08-09 at 19:24 -0400, William Pechter wrote:
>> > \
>> > > A couple of years ago I reported the issue but had to drop it due
>> > > to
>> > > a
>> > > lack of time on my part.
>> > >
>> > > Perl 5.12.3 fails to build on my Ubuntu 17.04 system (was
>> > > upgraded
>> > > from
>> > > the 14.04 I was using a couple of years ago.
>> > > perl [ 5.12.3
>> > > ] [ 92
>> > > ] [
>> > > FAIL ]
>> > >
>>
>> I tried it both ways. No luck. Building 32 bit under 32 bit CentOS
>> works fine.
>> I'm going to try again on a clean 17.04 install.
>
> Yes, I am using Fedora on my machine, too and that works fine.
>
> I just don't understand why Ubuntu is different.
>
> Anybody else using Ubuntu?
Yes. Me. Ubuntu 16.04.3 LTS. Since the beginning. No problems so far.
;-)
Best,
Matthias
>
> -Michael
>
>>
>> Bill
>>
>
prev parent reply other threads:[~2017-08-16 15:48 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-09 23:24 William Pechter
2017-08-16 13:45 ` Michael Tremer
2017-08-16 13:47 ` William Pechter
2017-08-16 14:59 ` Michael Tremer
2017-08-16 15:48 ` Matthias Fischer [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=2c19a35a-60a8-f57c-9407-ff7dffcfdc41@ipfire.org \
--to=matthias.fischer@ipfire.org \
--cc=development@lists.ipfire.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox