From: Michael Tremer <michael.tremer@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 14:45:26 +0100 [thread overview]
Message-ID: <1502891126.2543.29.camel@ipfire.org> (raw)
In-Reply-To: <c70899e8-4401-4446-fb6b-8c388bd1cbed@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 3495 bytes --]
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 ]
>
> Processing Jamo.txt
> Processing UnicodeData.txt
> Processing ArabicShaping.txt
> Processing Blocks.txt
> Processing PropList.txt
> Processing SpecialCasing.txt
> Processing LineBreak.txt
> Processing EastAsianWidth.txt
> Processing CompositionExclusions.txt
> Processing BidiMirroring.txt
> Processing CaseFolding.txt
> Processing DCoreProperties.txt
> Processing Scripts.txt
> Processing DNormalizationProps.txt
> Processing HangulSyllableType.txt
> Processing auxiliary/WordBreakProperty.txt
> Processing auxiliary/GraphemeBreakProperty.txt
> Processing auxiliary/GCBTest.txt
> Processing auxiliary/SentenceBreakProperty.txt
> Processing NamedSequences.txt
> Processing NameAliases.txt
> Finishing processing Unicode properties
> Compiling Perl properties
> Creating Perl synonyms
> Writing tables
> Making pod file
> Making test script
> Updating 'mktables.lst'
> make[1]: Leaving directorroot(a)S20:/usr/ipfire-2.x#
>
> tail /usr/ipfire-2.x/log/_build.base.log
>
> Processing NameAliases.txt
> Finishing processing Unicode properties
> Compiling Perl properties
> Creating Perl synonyms
> Writing tables
> Making pod file
> Making test script
> Updating 'mktables.lst'
> make[1]: Leaving directory '/usr/src/perl-5.12.3'
> make: *** [perl:85: /usr/src/log/perl-5.12.3] Error 2
> root(a)S20:/usr/ipfire-2.x#
> root(a)S20:/usr/ipfire-2.x# tail /usr/ipfire-2.x/log/_build.base.log
> Processing NameAliases.txt
> Finishing processing Unicode properties
> Compiling Perl properties
> Creating Perl synonyms
> Writing tables
> Making pod file
> Making test script
> Updating 'mktables.lst'
> make[1]: Leaving directory '/usr/src/perl-5.12.3'
> make: *** [perl:85: /usr/src/log/perl-5.12.3] Error 2
>
> I found the last referenced mktables.lst in lib/unicore and it exists
> and seems ok.
>
> -rw-r--r-- 1 root root 14334 Aug 9 14:43 mktables.lst
>
> How do figure where in the perl makefile is the failing part?
>
> In ipfire-2.x/build/usr/src/perl-5.12.3 is a perl binary which
> executes.
>
> How do figure where in the perl makefile is the failing part?
>
> root(a)S20:/usr/ipfire-2.x/build/usr/src/perl-5.12.3# ./perl -v
>
> This is perl 5, version 12, subversion 3 (v5.12.3) built for
> x86_64-linux-thread-multi
>
> Copyright 1987-2010, Larry Wall
>
> Perl may be copied only under the terms of either the Artistic
> License
> or the
> GNU General Public License, which may be found in the Perl 5 source
> kit.
>
> Complete documentation for Perl, including FAQ lists, should be found
> on
> this system using "man perl" or "perldoc perl". If you have access
> to the
> Internet, point your browser at http://www.perl.org/, the Perl Home
> Page
>
> -- Digital had it then. Don't you wish you could buy it now!
> pechter-at-gmail.com http://xkcd.com/705/
>
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2017-08-16 13:45 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 [this message]
2017-08-16 13:47 ` William Pechter
2017-08-16 14:59 ` Michael Tremer
2017-08-16 15:48 ` Matthias Fischer
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=1502891126.2543.29.camel@ipfire.org \
--to=michael.tremer@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