This is the mail archive of the crossgcc@sourceware.org mailing list for the crossgcc project.
See the CrossGCC FAQ for lots more information.
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |
Other format: | [Raw text] |
Hi, On Fri, Apr 9, 2010 at 3:04 PM, Remy Bohmer <linux@bohmer.net> wrote: > On certain hosts (ie. mingw) the default wrapper scripts and binary do not work > due to incompatible paths, path syntax, executable extensions > Why not making the script/exec MinGW-friendly ? I find dangerous to offer that option to everyone. If mingw specifically has to disable the wrapper (ie. if it can't be fixed), this can certainly be done in pure kconfig logic (!FOO_MINGW at the right place), without touching the build script. Having both ${CT_WRAPPER_NEEDED} and ${CT_TOOLS_WRAPPER_NONE} set seems quite illogical to me. Note that this wrapper stuff can be worked around by using the patch I send in a previous thread[0]. Yann, do you want a clean version of that patch ? Thanks, - Arnaud [0]: http://sourceware.org/ml/crossgcc/2010-04/msg00008.html > Signed-off-by: Bart vdr. Meulen <bartvdrmeulen@gmail.com> > --- > ?config/companion_libs.in ? | ? 14 +++++++- > ?scripts/build/internals.sh | ? 78 +++++++++++++++++++++++---------------------- > ?2 files changed, 53 insertions(+), 39 deletions(-) > -- For unsubscribe information see http://sourceware.org/lists.html#faq
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |