From: Michael Olbrich <m.olbrich@pengutronix.de>
To: ptxdist@pengutronix.de
Subject: Re: [ptxdist] Linker problem: libpng-1.2.50, ptxdist-2012.12.0, and new atom toolchain i686-atom-linux
Date: Fri, 14 Dec 2012 10:43:12 +0100 [thread overview]
Message-ID: <20121214094312.GD32091@pengutronix.de> (raw)
In-Reply-To: <D415CD2EC4182C4EAB90A76B7D9F16DCAAA62199@EX-DAG02.eckelmann.group>
On Thu, Dec 13, 2012 at 12:40:53PM +0000, Schenk, Gavin wrote:
> yesterday I read about the new toolchain, that has Atom optimization by default.
>
> I decided to give it a try and:
> Compiled the new toolchain: gcc-4.6.2-glibc-2.14.1-binutils-2.21.1a-kernel-2.6.39-sanitized
> Migrated my project: 2012.10.0 to 2012.12.0
> Update Kernel and rt-patchstack: 3.4.2 to 3.6.10
>
> Now the compilation fails on libpng 1.2.50 that is the same version as in ptxdist-2012.10.0.
>
> <snip>
> libtool: link: i686-atom-linux-gnu-gcc -shared .libs/libpng12_la-png.o .libs/libpng12_la-pngset.o .libs/libpng12_la-pngget.o .libs/libpng12_la-pngrutil.o .libs/libpng12_la-pngtrans.o .libs/libpng12_la-pngwutil.o .libs/libpng12_la-pngread.o .libs/libpng12_la-pngrio.o .libs/libpng12_la-pngwio.o .libs/libpng12_la-pngwrite.o .libs/libpng12_la-pngrtran.o .libs/libpng12_la-pngwtran.o .libs/libpng12_la-pngmem.o .libs/libpng12_la-pngerror.o .libs/libpng12_la-pngpread.o -lz -lm -Wl,--version-script=libpng.vers -Wl,-soname -Wl,libpng12.so.0 -o .libs/libpng12.so.0.50.0
> /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/lib/gcc/i686-atom-linux-gnu/4.7.2/../../../../i686-atom-linux-gnu/bin/ld:libpng.vers:2: syntax error in VERSION script
> collect2: error: ld returned 1 exit status
> make[2]: *** [libpng12.la] Error 1
> make[2]: Leaving directory `/var/projects/prodos3_experimental/ptxdist/platform-BB11QA6/build-target/libpng-1.2.50'
> make[1]: *** [all] Error 2
> make[1]: Leaving directory `/var/projects/prodos3_experimental/ptxdist/platform-BB11QA6/build-target/libpng-1.2.50'
> make: *** [/var/projects/prodos3_experimental/ptxdist/platform-BB11QA6/state/libpng.compile] Error 2
> </snip>
I cannot reproduce this here so far. Please sent the output of the whole
compile stage. There should be some output about creating libpng.vers.
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
next prev parent reply other threads:[~2012-12-14 9:43 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 [this message]
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
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=20121214094312.GD32091@pengutronix.de \
--to=m.olbrich@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