From: "Schenk, Gavin" <G.Schenk@eckelmann.de>
To: "ptxdist@pengutronix.de" <ptxdist@pengutronix.de>
Cc: Marc Kleine-Budde <mkl@pengutronix.de>
Subject: Re: [ptxdist] Linker problem: libpng-1.2.50, ptxdist-2012.12.0, and new atom toolchain i686-atom-linux
Date: Tue, 18 Dec 2012 10:00:47 +0000 [thread overview]
Message-ID: <D415CD2EC4182C4EAB90A76B7D9F16DCAAA625E1@EX-DAG02.eckelmann.group> (raw)
In-Reply-To: <20121217163739.GO32091@pengutronix.de>
[-- Attachment #1: Type: text/plain, Size: 4162 bytes --]
Hi,
enjoy your holidays, I have no time pressure switching to the new toolchain!
After learning about logfiles and ptxdist :D, the command-wrapper produces reasonable output on console in the libpng folder. There is no output when I prefix ccache, but calling the compiler directly the output is like this:
<snip>
/opt/OSELAS.Toolchain-2012.12.0/i686-atom-linux-gnu/gcc-4.7.2-glibc-2.16.0-binutils-2.22-kernel-3.6-sanitized/bin/i686-atom-linux-gnu-cpp -frecord-gcc-switches -isystem /home/gschenk/projects/prodos3_experimental/ptxdist/platform-BB11QA6/sysroot-target/include -isystem /home/gschenk/projects/prodos3_experimental/ptxdist/platform-BB11QA6/sysroot-target/usr/include -DPNG_CONFIGURE_LIBPNG -DPNG_BUILDSYMS ./png.h
# 1 "./png.h"
# 1 "<command-line>"
# 1 "./png.h"
# 536 "./png.h"
# 1 "/home/gschenk/projects/prodos3_experimental/ptxdist/platform-BB11QA6/sysroot-target/usr/include/zlib.h" 1 3 4
# 34 "/home/gschenk/projects/prodos3_experimental/ptxdist/platform-BB11QA6/sysroot-target/usr/include/zlib.h" 3 4
# 1 "/home/gschenk/projects/prodos3_experimental/ptxdist/platform-BB11QA6/sysroot-target/usr/include/zconf.h" 1 3 4
# 365 "/home/gschenk/projects/prodos3_experimental/ptxdist/platform-BB11QA6/sysroot-target/usr/include/zconf.h" 3 4
typedef unsigned char Byte;
typedef unsigned int uInt;
typedef unsigned long uLong;
...
extern PNG_FUNCTION_EXPORT png_save_uint_16 END
(png_bytep buf, unsigned int i);
</snip>
Attached you find two logfiles, one with ccache enabled, one without. I tried to figure out what is going on, but I need a Guru ... THATS YOU :D. I hope to become more familiar with ptxdist in future.
Maybe it is the order, or parallelization of build process? I have a Multi-CPU system with 8 cores.
Even when I disable ccache the buildprocess does not finish. Next I am bailing out at building gdbserver.
make[1]: Entering directory `/var/projects/prodos3_experimental/ptxdist/platform-BB11QA6/build-target/gdbserver-7.2-build
...
/var/projects/prodos3_experimental/ptxdist/platform-BB11QA6/build-target/gdbserver-7.2/gdb/gdbserver/linux-low.c:4691:40: error: invalid application of 'sizeof' to incomplete type 'struct siginfo'
...
Thanks for your help,
Gavin
> -----Original Message-----
> From: ptxdist-bounces@pengutronix.de [mailto:ptxdist-
> bounces@pengutronix.de] On Behalf Of Michael Olbrich
> Sent: Monday, December 17, 2012 5:38 PM
> To: ptxdist@pengutronix.de
> Cc: Marc Kleine-Budde
> Subject: Re: [ptxdist] Linker problem: libpng-1.2.50, ptxdist-2012.12.0,
> and new atom toolchain i686-atom-linux
>
> On Fri, Dec 14, 2012 at 07:19:35PM +0100, Michael Olbrich wrote:
> > On Fri, Dec 14, 2012 at 01:46:01PM +0000, Schenk, Gavin wrote:
> > > I am a bit short in time today.... I do not find a line like:
> > > wrapper: i686-atom-linux-gnu-cpp [...] -DPNG_CONFIGURE_LIBPNG -
> DPNG_BUILDSYMS ./png.h
> > > Attached the complete log from ptxdist -v compile libpng.
> >
> > Not the output in the shell but platform-BB11QA6/logfile.
>
> And it's probably:
> wrapper: /usr/bin/ccache i686-atom-linux-gnu-cpp [...] -
> DPNG_CONFIGURE_LIBPNG -DPNG_BUILDSYMS ./png.h
>
> > > The compilestage succeeds, if I disable ccache. Please try if you can
> > > reproduce the error when ccache is activated.
> >
> > I'll see, when I find some time. Christmas holidays start for me just
> about
> > now. :-)
>
> I've enabled ccache. Still no error.
>
> Michael
>
> --
> Pengutronix e.K. | |
> Industrial Linux Solutions | http://www.pengutronix.de/ |
> Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0 |
> Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
>
> --
> ptxdist mailing list
> ptxdist@pengutronix.de
Eckelmann Aktiengesellschaft
Vorstand: Dr.-Ing. Gerd Eckelmann (Vorsitzender)
Dr.-Ing. Peter Cordes, Dr.-Ing. Frank-Thomas Mellert
Vorsitzender des Aufsichtsrats: Hubertus G. Krossa
Sitz der Gesellschaft: Berliner Str. 161, 65205 Wiesbaden, Amtsgericht Wiesbaden HRB 12636
http://www.eckelmann.de
[-- Attachment #2: logfiles.tgz --]
[-- Type: application/x-compressed, Size: 9709 bytes --]
[-- Attachment #3: Type: text/plain, Size: 48 bytes --]
--
ptxdist mailing list
ptxdist@pengutronix.de
next prev parent reply other threads:[~2012-12-18 10:00 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-13 12:40 Schenk, Gavin
2012-12-13 17:06 ` George McCollister
2012-12-13 18:46 ` Robert Schwebel
2012-12-14 9:43 ` Michael Olbrich
2012-12-14 9:48 ` Schenk, Gavin
2012-12-14 10:07 ` Michael Olbrich
2012-12-14 10:26 ` Schenk, Gavin
2012-12-14 10:32 ` Michael Olbrich
2012-12-14 13:46 ` Schenk, Gavin
2012-12-14 18:19 ` Michael Olbrich
2012-12-17 16:37 ` Michael Olbrich
2012-12-18 10:00 ` Schenk, Gavin [this message]
2012-12-18 18:46 ` Michael Olbrich
2012-12-19 11:22 ` Schenk, Gavin
2012-12-19 11:42 ` Michael Olbrich
2012-12-20 11:10 ` Schenk, Gavin
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=D415CD2EC4182C4EAB90A76B7D9F16DCAAA625E1@EX-DAG02.eckelmann.group \
--to=g.schenk@eckelmann.de \
--cc=mkl@pengutronix.de \
--cc=ptxdist@pengutronix.de \
/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