From: Bryan Hundven <bryanhundven@gmail.com>
To: "Yann E. MORIN" <yann.morin.1998@free.fr>
Cc: "crossgcc maillist" <crossgcc@sourceware.org>,
"Benoît THÉBAUDEAU" <benoit.thebaudeau@advansee.com>
Subject: kconfig
Date: Sat, 22 Feb 2014 07:12:00 -0000 [thread overview]
Message-ID: <CAJ+oik0SBCzqY57ccq+j1N+i_Pwn4h6-7jGE+35qmphwxqQQRA@mail.gmail.com> (raw)
Yann, Benoît, all,
I use xubuntu on one computer and mac os x 10.9 on my mac book pro.
I like the idea of being able to build on my mac with the least number
of packages installed by homebrew.
I started down this path, and installed:
* xcode
* xcode command line tools
* autoconf
* automake
* binutils
* cvs
* gawk
* gnu-sed
* libtool
* wget
Which gets me to the point of being able to bootstrap the
configure.in, configure, and run make.
The part that really kills the build and perplexes me is kconfig.
http://code.bulix.org/qereby-85701
While trying to figure out the right fix to the problem, I noticed
that there are a *LOT* of differences between the kconfig in
crosstool-ng, buildroot and upstream linux, and Yann's
kconfig-frontends git tree
(http://ymorin.is-a-geek.org/git/kconfig-frontends/).
It seems to me that we should follow buildroot's example of using a
'Makefile.ctng' in the kconfig directory to wrap the kconfig Makefile,
so that we can copy updates from upstream linux into the kconfig
directory without stomping on our own Makefile.
While trying to attempt, I started pulling on the thread of the
kconfig sweater in crosstool-ng, and it's a mess.
Just looking for opinions for the path forward with this.
Cheers,
-Bryan
--
For unsubscribe information see http://sourceware.org/lists.html#faq
next reply other threads:[~2014-02-22 7:12 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-22 7:12 Bryan Hundven [this message]
2014-02-22 12:12 ` kconfig Bryan Hundven
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=CAJ+oik0SBCzqY57ccq+j1N+i_Pwn4h6-7jGE+35qmphwxqQQRA@mail.gmail.com \
--to=bryanhundven@gmail.com \
--cc=benoit.thebaudeau@advansee.com \
--cc=crossgcc@sourceware.org \
--cc=yann.morin.1998@free.fr \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).