From: George McCollister <george.mccollister@gmail.com>
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: Thu, 13 Dec 2012 11:06:22 -0600 [thread overview]
Message-ID: <50CA0B0E.4010100@gmail.com> (raw)
In-Reply-To: <D415CD2EC4182C4EAB90A76B7D9F16DCAAA62199@EX-DAG02.eckelmann.group>
On 12/13/2012 06:40 AM, Schenk, Gavin wrote:
> Hi,
>
> 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>
I'm using libpng on Atom as well. I had a few unrelated (I think)
problems with the new wrappers and a problem with CROSS python changes
in ptxdist so I had to revert back to ptxdist as of November 12, 2012
with
OSELAS.Toolchain-2011.11.3/i686-unknown-linux-gnu/gcc-4.6.2-glibc-2.14.1-binutils-2.21.1a-kernel-2.6.39-sanitized.
I'll make it a point to try to get my build going with the newest
ptxdist and toolchain and see if I run into the same problem.
Regards,
George McCollister
--
ptxdist mailing list
ptxdist@pengutronix.de
next prev parent reply other threads:[~2012-12-13 17:06 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 [this message]
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
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=50CA0B0E.4010100@gmail.com \
--to=george.mccollister@gmail.com \
--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