From: "Thiago A. Corrêa" <thiago.correa@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] undefined _dl_app_init_array and _dl_app_fini_array
Date: Tue, 23 Oct 2007 17:07:39 -0300 [thread overview]
Message-ID: <d6cda7730710231307g675615f7p1474b668aa88f748@mail.gmail.com> (raw)
In-Reply-To: <00d501c815ad$7f540f40$7b00000a@atmel.com>
Nope, it wasn't that I had another toochain installed... I'm still
getting that link error after removing the toolchain. Even using the
atngw100-defconfig :(
./libtool --mode=link
/root/novacomm/buildroot/buildroot-original/build_avr32/staging_dir/usr/bin/avr32-linux-uclibc-gcc
-Os -pipe -I/root/novacomm/buildroot/buildroot-original/build_avr32/staging_dir/usr/include
-I/root/novacomm/buildroot/buildroot-original/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
/root/novacomm/buildroot/buildroot-original/build_avr32/staging_dir/usr/bin/avr32-linux-uclibc-gcc
-Os -pipe -I/root/novacomm/buildroot/buildroot-original/build_avr32/staging_dir/usr/include
-I/root/novacomm/buildroot/buildroot-original/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
/root/novacomm/buildroot/buildroot-original/build_avr32/staging_dir/lib/libc.so.0:
undefined reference to `_dl_app_init_array'
/root/novacomm/buildroot/buildroot-original/build_avr32/staging_dir/lib/libc.so.0:
undefined reference to `_dl_app_fini_array'
collect2: ld returned 1 exit status
make[1]: *** [cjpeg] Error 1
make[1]: Leaving directory
`/root/novacomm/buildroot/buildroot-original/build_avr32/jpeg-6b'
make: *** [/root/novacomm/buildroot/buildroot-original/build_avr32/jpeg-6b/.libs/libjpeg.a]
Error 2
On 10/23/07, Ulf Samuelsson <ulf@atmel.com> 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.
>
> It is not unlikely that they have the same problem then.
> If you indeed verify this, then pls inform them at the AVRfreaks forum.
>
> Best Regards
> Ulf Samuelsson
>
>
next prev parent reply other threads:[~2007-10-23 20:07 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 [this message]
2007-10-23 20:17 ` Ivan Kuten
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=d6cda7730710231307g675615f7p1474b668aa88f748@mail.gmail.com \
--to=thiago.correa@gmail.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