From: Ludger Keilig <buildroot@invalid-domain.net>
To: buildroot@busybox.net
Subject: [Buildroot] buildroot-2010.05-rc2, problem with binutils-2.20.1
Date: Fri, 21 May 2010 11:09:15 +0200 [thread overview]
Message-ID: <4BF64DBB.9030805@invalid-domain.net> (raw)
In-Reply-To: <1274422785.5719.8.camel@bernd-desktop>
Hello,
> I tried buildroot-2010.05-rc2:
> make at91rm9200df_defconfig
> make menuconfig
> make
>
> buildroot terminates with:
>
> checking for zlib.h... yes
> /media/disk/br1005rc2/buildroot-2010.05-rc2/output/toolchain/binutils-2.20.1/libiberty/fibheap.c: In function ?fibheap_union?:checking linker --as-needed support...
> /media/disk/br1005rc2/buildroot-2010.05-rc2/output/toolchain/binutils-2.20.1/libiberty/fibheap.c:151: warning: implicit declaration of function ?free?
> /media/disk/br1005rc2/buildroot-2010.05-rc2/output/toolchain/binutils-2.20.1/libiberty/fibheap.c: In function ?fibheap_replace_key_data?:
> /media/disk/br1005rc2/buildroot-2010.05-rc2/output/toolchain/binutils-2.20.1/libiberty/fibheap.c:220: error: ?LONG_MIN? undeclared (first use in this function)
> /media/disk/br1005rc2/buildroot-2010.05-rc2/output/toolchain/binutils-2.20.1/libiberty/fibheap.c:220: error: (Each undeclared identifier is reported only once
> /media/disk/br1005rc2/buildroot-2010.05-rc2/output/toolchain/binutils-2.20.1/libiberty/fibheap.c:220: error: for each function it appears in.)
> /media/disk/br1005rc2/buildroot-2010.05-rc2/output/toolchain/binutils-2.20.1/libiberty/fibheap.c: In function ?fibheap_delete_node?:
> /media/disk/br1005rc2/buildroot-2010.05-rc2/output/toolchain/binutils-2.20.1/libiberty/fibheap.c:261: error: ?LONG_MIN? undeclared (first use in this function)
> /media/disk/br1005rc2/buildroot-2010.05-rc2/output/toolchain/binutils-2.20.1/libiberty/fibheap.c:265: warning: implicit declaration of function ?abort?
> /media/disk/br1005rc2/buildroot-2010.05-rc2/output/toolchain/binutils-2.20.1/libiberty/fibheap.c:265: warning: incompatible implicit declaration of built-in function ?abort?
> /media/disk/br1005rc2/buildroot-2010.05-rc2/output/toolchain/binutils-2.20.1/libiberty/fibheap.c: In function ?fibheap_consolidate?:
> /media/disk/br1005rc2/buildroot-2010.05-rc2/output/toolchain/binutils-2.20.1/libiberty/fibheap.c:368: warning: implicit declaration of function ?memset?
> /media/disk/br1005rc2/buildroot-2010.05-rc2/output/toolchain/binutils-2.20.1/libiberty/fibheap.c:368: warning: incompatible implicit declaration of built-in function ?memset?
Seems to be the same as in bug #1789.
For me, it helped to revert the patch introduced in commit
6b939d40f6a29a43277566adc9d4312d49cb3abf.
No, I don't like this, but at least it seems to work.
Ciao, Ludger
next prev parent reply other threads:[~2010-05-21 9:09 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-21 6:19 [Buildroot] buildroot-2010.05-rc2, problem with binutils-2.20.1 Thomas
2010-05-21 9:09 ` Ludger Keilig [this message]
2010-05-21 9:53 ` Thomas Petazzoni
2010-05-21 10:25 ` Thomas Petazzoni
[not found] ` <1274479497.25288.3.camel@bernd-desktop>
2010-05-21 22:30 ` Thomas Petazzoni
2010-05-22 8:33 ` Thomas
2010-05-22 12:55 ` Thomas Petazzoni
2010-05-24 18:10 ` Thomas
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=4BF64DBB.9030805@invalid-domain.net \
--to=buildroot@invalid-domain.net \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.