From: James J. Dines <jdines@jdines.net>
To: buildroot@busybox.net
Subject: [Buildroot] Make 3.82 does behave differently than make 3.81 for sure, but ...
Date: Mon, 30 Aug 2010 19:28:14 -0400 [thread overview]
Message-ID: <4C7C3E8E.70309@jdines.net> (raw)
In-Reply-To: <87pqwzwzp6.fsf@macbook.be.48ers.dk>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 08/30/2010 05:36 PM, Peter Korsgaard wrote:
>>>>>> "James" == James J Dines <jdines@jdines.net> writes:
>
> Hi,
>
> James> I went for a third option (applying Yann's patch) and it indeed
> James> allows the 'make clean' to work. I remain confused why we did
> James> not need this patch to do a complete build with make 3.81
> James> however. I just tried it again, and I do not get the error
> James> message on my other machine with 3.81 even without the patch.
>
> No, it seems like make 3.81 ignores those invalid lines.
>
> besides this issue, is everything working for you with ake 3.82?
>
I think things are working OK. I am currently getting this error while
building oprofile 0.9.4 during the configure stage:
checking for bfd_openr in -lbfd... no
configure: error: bfd library not found
make: ***
[/home/jdines/Build/buildroot/output/build/oprofile-0.9.4/.stamp_configured]
Error 1
... but it seems like this is might be the issue:
http://old.nabble.com/configure-error:-bfd-library-not-found-td23863431.html
Excerpt:
So, do you have libbfd(.a or .so) installed in the usual place where
config would look for it? If you do, then perhaps the problem is you
have a newer binutils where libbfd has a dependency on libz that
oprofile 0.9.4 did not handle, which resulted in this rather unhelpful
error message. Pull the latest oprofile cvs code for a fix.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (GNU/Linux)
iQEcBAEBAgAGBQJMfD6AAAoJECSpOhdQESq6ESEH/j8zRLV8g3oejph8MFgci0Wi
82wE9f9MDw0mtoyiWWYD5z2n8VhkqgsnhCqbOjKHMwjGi9G7AuyTzuwqZxC50A6E
kuVajig90Hxz0Ae0kH97ntte7mtwS19I/yXw8cFVorvUV6n6iOlmtni+vi/4T6tt
72xRLm3MmG46EGrn0W8297e3a6O4eUAM3f+GXV/pG2RVb5YnE9WnYC4axAZpMiT3
dyARY+w6XkXdy2+JX6IbzlXxj9v7mAtSd/9puvkhxkGrVLd60lnw2CQ/U0h8kMZq
NuPJYF/umHTO7hnS5Vf9Sp2hHTCjjL+rzRCDBE0M7AbMwdfVnIAe1nweC4ji4K8=
=QQ8F
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2010-08-30 23:28 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-30 11:45 [Buildroot] package/atk/atk.mk:43: *** recipe commences before first target. Stop James J. Dines
2010-08-30 13:05 ` Yann E. MORIN
2010-08-30 13:37 ` Peter Korsgaard
2010-08-30 14:46 ` James J. Dines
2010-08-30 15:01 ` Yann E. MORIN
2010-08-30 15:44 ` [Buildroot] Make 3.82 does behave differently than make 3.81 for sure, but James J. Dines
2010-08-30 16:31 ` Sam Ravnborg
[not found] ` <4C7BE3C4.1060706@jdines.net>
[not found] ` <20100830185017.GA12921@merkur.ravnborg.org>
2010-08-30 19:01 ` [Buildroot] Make 3.82 does behave differently than make 3.81 James J. Dines
2010-08-30 20:00 ` [Buildroot] Make 3.82 does behave differently than make 3.81 for sure, but Peter Korsgaard
2010-08-30 20:21 ` James J. Dines
2010-08-30 20:57 ` Peter Korsgaard
2010-08-30 21:10 ` James J. Dines
2010-08-30 21:36 ` Peter Korsgaard
2010-08-30 23:28 ` James J. Dines [this message]
2010-08-31 22:17 ` [Buildroot] Make 3.82 testing progress update James J. Dines
2010-08-30 22:15 ` [Buildroot] Make 3.82 does behave differently than make 3.81 for sure, but Malte Starostik
2010-08-31 12:38 ` James J. Dines
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=4C7C3E8E.70309@jdines.net \
--to=jdines@jdines.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox