From: Arne Fitzenreiter <Arne.Fitzenreiter@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: Problem with building 2.13/75 (gutenprint) on Debian
Date: Mon, 03 Mar 2014 14:15:21 +0100 [thread overview]
Message-ID: <64413d34f10281641c3ac163a7dfeaca@mail01.ipfire.org> (raw)
In-Reply-To: <531452DB.2000208@t-online.de>
[-- Attachment #1: Type: text/plain, Size: 2029 bytes --]
On 2014-03-03 11:00, Matthias Fischer wrote:
> Hi,
>
> I just began working with IPFire 2.13, trying to get my Devel-PC
> working.
>
> My environment:
>
> - P4/2800, 1GB RAM (ok, I know, machine is old, but sufficient for my
> needs - until now)
> - Debian 7.4 (3.2.0-4-686-pae #1 SMP Debian 3.2.54-2 i686 GNU/Linux)
> - /bin/sh points to 'bash'.
>
> I tried to setup everything as described in Wiki and had absolutely no
> problems until tonight:
>
> Despite everything I tried, "./make.sh build" keeps telling me this
> (taken from '_build.ipfire.log'):
>
> ***SNIP***
> Can't locate Foomatic/Defaults.pm in @INC (@INC contains:
> /usr/lib/perl5/site_perl/5.12.3/i586-linux-thread-multi
> /usr/lib/perl5/site_perl/5.12.3
> /usr/lib/perl5/5.12.3/i586-linux-thread-multi /usr/lib/perl5/5.12.3 .)
> at /usr/sbin/foomatic-kitload line 3.
> BEGIN failed--compilation aborted at /usr/sbin/foomatic-kitload line 3.
> make[5]: *** [install-kit] Error 2
> make[5]: Leaving directory `/usr/src/gutenprint-5.2.5/src/foomatic'
> ***SNAP***
This is a strange timing problem on systems with more cpu cores.
Sometimes the ccache was corrupted and gutenprint or fomatic will not
build correctly. I hope this is fixed with the new foomatic version in
IPFire 2.15.
erase your ccache and checkout the next branch. (get checkout next)
After this make clean and download toolchain again.
It makes not much sense to develop with the master tree at the moment
because 2.15 should released in some weeks.
Arne
>
> Every 'make.sh'-line says '[ DONE ]', but only 'gutenprint' won't
> work, no matter what I tried.
>
> Being curious, I commented line 695 ('ipfiremake gutenprint') in
> 'make.sh' and started 'make.sh' again.
>
> Building continued with 'apsupsd' and is still working fine.
>
> Any hints for getting 'gutenprint' compiling ok?
>
> Regards
> Matthias
> _______________________________________________
> Development mailing list
> Development(a)lists.ipfire.org
> http://lists.ipfire.org/mailman/listinfo/development
next prev parent reply other threads:[~2014-03-03 13:15 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-03 10:00 Matthias Fischer
2014-03-03 13:15 ` Arne Fitzenreiter [this message]
2014-03-03 19:42 ` 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=64413d34f10281641c3ac163a7dfeaca@mail01.ipfire.org \
--to=arne.fitzenreiter@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