From: Peter Korsgaard <jacmet@uclibc.org>
To: buildroot@busybox.net
Subject: [Buildroot] "make menuconfig" possibly broken in git master
Date: Sat, 25 Sep 2010 16:59:29 +0200 [thread overview]
Message-ID: <87iq1t7tta.fsf@macbook.be.48ers.dk> (raw)
In-Reply-To: <AANLkTi=OWG3Q2z2_G4QNU45fFf78391GB2kx5SjUkBLv@mail.gmail.com> ("Bjørn Forsman"'s message of "Sat, 25 Sep 2010 16:29:31 +0200")
>>>>> "Bj?rn" == Bj?rn Forsman <bjorn.forsman@gmail.com> writes:
Bj?rn> 2010/9/25 Peter Korsgaard <jacmet@uclibc.org>:
>>>>>>> "Bj?rn" == Bj?rn Forsman <bjorn.forsman@gmail.com> writes:
>>
>> ?Bj?rn> Hi all,
>> ?Bj?rn> My buildroot git master tree fails to "make menuconfig" because of
>> ?Bj?rn> "zconf.tab.c:181: error: conflicting types for ?symbol_hash?":
>>
>> Strange - Could you try the the same with a recent linux kernel
>> (E.G. 2.6.36-rc5)?
Bj?rn> As the commands "make distclean && make defconfig/menuconfig" fail
Bj?rn> I don't know how to specify another kernel version. So I assume you mean
Bj?rn> the kernel on build host. I'm on Ubuntu 10.04 and the last time I tried my
Bj?rn> own kernel on a Ubuntu system it barely booted. So no, I dare not try a
Bj?rn> recent kernel just yet :-)
No, I actually meant go and download a Linux kernel tarball (E.G. from
kernel.org), extract it and run make menuconfig. The menuconfig stuff in
buildroot comes from the Linux kernel.
But looking at Lionel's mail it seems to be an issue about certain files
not getting rebuilt. Could you do a fresh git clone and try in that dir
or alternatively run make O=output2 menuconfig?
--
Bye, Peter Korsgaard
next prev parent reply other threads:[~2010-09-25 14:59 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-25 11:21 [Buildroot] "make menuconfig" possibly broken in git master Bjørn Forsman
2010-09-25 12:14 ` Peter Korsgaard
2010-09-25 14:29 ` Bjørn Forsman
2010-09-25 14:59 ` Peter Korsgaard [this message]
2010-09-25 15:31 ` Bjørn Forsman
2010-09-25 20:56 ` Peter Korsgaard
2010-09-27 7:12 ` Bjørn Forsman
2010-09-25 13:49 ` Lionel Landwerlin
2010-09-25 15:02 ` Bjørn Forsman
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=87iq1t7tta.fsf@macbook.be.48ers.dk \
--to=jacmet@uclibc.org \
--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.