From: Wim Vinckier <wimpunk@gmail.com>
To: ptxdist@pengutronix.de
Subject: Re: [ptxdist] Issue while compiling libSDL
Date: Thu, 24 May 2018 13:31:08 +0200 [thread overview]
Message-ID: <CAMyOCn8QovvEwvKGLvAyWQk0=41ECYvOEnP80xWXyOc58_W-Xw@mail.gmail.com> (raw)
In-Reply-To: <CAMyOCn8hqRC6ohiPONDmrnKapUtkTns7TEFoMzu2MFi=2gY09g@mail.gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 1442 bytes --]
Hi,
On Thu, 24 May 2018 at 09:16, Wim Vinckier <wimpunk@gmail.com> wrote:
> Hi,
>
> On Wed, 23 May 2018 at 22:39, Ladislav Michl <ladis@linux-mips.org> wrote:
>
>> On Wed, May 23, 2018 at 11:49:16AM +0200, Wim Vinckier wrote:
>> > Hi List,
>> >
>> > I'm trying to compile libSDL for arm with toolchain
>> >
>> oselas.toolchain-2018.02.0-arm-v5te-linux-gnueabi-gcc-7.3.1-glibc-2.27-binutils-2.30-kernel-4.15-sanitize
>> > with ptxdist-2018.05.0 but it fails and I don't understand what's going
>> > wrong. This is the linker error I get:
>> >
>> > ./.libs/libSDL_image.so: undefined reference to `png_set_longjmp_fn'
>>
>> Just did quick test with both arm-v5te-linux-gnueabi and
>> arm-v7a-linux-gnueabi
>> and I do not see above error. Also, care to tell what ptxdist version are
>> you
>> using?
>>
>>
> I'm using ptxdist-2018.05.0.
>
> Google results for 'png_set_longjmp_fn' query gives a bit of clue, care to
>> check them?
>>
>
> Most of the items tells refer to an old version of the library hanging
> around. I see there's a libpng12 and a libpng16 in my tree. I'll try to
> clean it complete and come back after the rebuild.
>
> Thanks for the suggestion, I should have checked that one earlier.
>
It looks like this suggestion was the correct suggestion. There was a
libpng12 hanging around from the old build. I did a complete `ptxdist
distclean` and after a rebuild I got a working SDL library.
Thanks again,
wim vinckier.
[-- Attachment #1.2: Type: text/html, Size: 2310 bytes --]
[-- Attachment #2: Type: text/plain, Size: 91 bytes --]
_______________________________________________
ptxdist mailing list
ptxdist@pengutronix.de
prev parent reply other threads:[~2018-05-24 11:31 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-23 9:49 Wim Vinckier
2018-05-23 20:38 ` Ladislav Michl
2018-05-24 7:16 ` Wim Vinckier
2018-05-24 11:31 ` Wim Vinckier [this message]
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='CAMyOCn8QovvEwvKGLvAyWQk0=41ECYvOEnP80xWXyOc58_W-Xw@mail.gmail.com' \
--to=wimpunk@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