From: Ivan Kuten <ivan.kuten@promwad.com>
To: buildroot@busybox.net
Subject: [Buildroot] undefined _dl_app_init_array and _dl_app_fini_array
Date: Tue, 23 Oct 2007 23:17:08 +0300 [thread overview]
Message-ID: <471E56C4.2090308@promwad.com> (raw)
In-Reply-To: <d6cda7730710231154k48e3ef30uac75a10a0b9fa1c8@mail.gmail.com>
libjpeg is OK for avr32 too:
./libtool --mode=link /opt/buildroot/build_avr32/staging_dir/usr/bin/avr32-linux-uclibc-gcc -Os -pipe -I/opt/buildroot/build_avr32/staging_dir/usr/include
-I/opt/buildroot/build_avr32/staging_dir/include -msoft-float -o cjpeg cjpeg.lo rdppm.lo rdgif.lo rdtarga.lo rdrle.lo rdbmp.lo rdswitch.lo cdjpeg.lo libjpeg.la
/opt/buildroot/build_avr32/staging_dir/usr/bin/avr32-linux-uclibc-gcc -Os -pipe -I/opt/buildroot/build_avr32/staging_dir/usr/include -I/opt/buildroot/build_avr32/staging_dir/include -msoft-float -o
.libs/cjpeg cjpeg.o rdppm.o rdgif.o rdtarga.o rdrle.o rdbmp.o rdswitch.o cdjpeg.o -Wl,--rpath -Wl,/lib .libs/libjpeg.so
Thiago A. Corr?a wrote:
> Hmmm well, I noticed that on my custom package at the linking stage it
> was for some reason using the avr32 compiler instaled on my system
> (4.0.99), so I removed that and I'm rebuilding to see what gives....
> hopefully that's the problem :)
>
> Strangely, I know I'm not the only one who have noticed that issue...
> some others have mentioned that at the avrfreaks.com forums.
>
> *crosses fingers and waits*
>
> Regards,
> Thiago A. Correa
>
Best regards,
Ivan
--
--------------------------------
Embedded Linux engineer,
Promwad Company: http://www.promwad.com/
Homepage : http://www.ivankuten.com/
--------------------------------
prev parent reply other threads:[~2007-10-23 20:17 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-23 17:19 [Buildroot] undefined _dl_app_init_array and _dl_app_fini_array Thiago A. Corrêa
2007-10-23 19:54 ` Ivan Kuten
2007-10-23 18:54 ` Thiago A. Corrêa
2007-10-23 19:46 ` Ulf Samuelsson
2007-10-23 20:07 ` Thiago A. Corrêa
2007-10-23 20:17 ` Ivan Kuten [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=471E56C4.2090308@promwad.com \
--to=ivan.kuten@promwad.com \
--cc=buildroot@busybox.net \
/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