From: Joachim Nilsson <jocke@vmlinux.org>
To: "Yann E. MORIN" <yann.morin.1998@anciens.enib.fr>
Cc: crossgcc@sourceware.org
Subject: Re: crosstool-ng: No CT_TOOLS_WRAPPER set when building a standard CROSS...
Date: Sun, 06 Sep 2009 09:21:00 -0000 [thread overview]
Message-ID: <4AA37EF2.7040203@vmlinux.org> (raw)
In-Reply-To: <200909061107.44797.yann.morin.1998@anciens.enib.fr>
On 09/06/2009 11:07 AM, Yann E. MORIN wrote:
> But in fact there's a litle bit to it that I'd like to fix, especially
> the menuconfig order: it would be better if the user does not have to
> go back and forth in the menuconfig to set options. In this case, setting
> the comp libs would uncover anoption at the begining, and the user may
> miss it. Moving the choice down into the comp lib menu will be better.
That's a good idea, I was actually quite confused by this initially.
But I can see the logic in having it with the toolchain options as well,
but that same logic could also be applied to saying that it should be
with the C Compiler options. I.e., when selecting a gcc >= 4.3.x ...
... maybe the companion libraries section should appear as a subsection
of the C Compiler menu when selecting a gcc >= 4.3.x?
Sorry if I muddling the water here.
Regards
/Jocke
--
For unsubscribe information see http://sourceware.org/lists.html#faq
next prev parent reply other threads:[~2009-09-06 9:21 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-06 8:18 Joachim Nilsson
2009-09-06 8:52 ` Yann E. MORIN
2009-09-06 9:00 ` Joachim Nilsson
2009-09-06 8:53 ` Joachim Nilsson
2009-09-06 9:07 ` Yann E. MORIN
2009-09-06 9:21 ` Joachim Nilsson [this message]
2009-09-06 9:41 ` Yann E. MORIN
2009-09-06 9:49 ` Joachim Nilsson
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=4AA37EF2.7040203@vmlinux.org \
--to=jocke@vmlinux.org \
--cc=crossgcc@sourceware.org \
--cc=yann.morin.1998@anciens.enib.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).