public inbox for crossgcc@sourceware.org
 help / color / mirror / Atom feed
From: Ralf Corsepius <ralf.corsepius@rtems.org>
To: Mike Frysinger <vapier@gentoo.org>
Cc: crossgcc@sourceware.org,
	Zhenqiang Chen <zhenqiang.chen@linaro.org>,
	 "Yann E. MORIN" <yann.morin.1998@anciens.enib.fr>
Subject: Re: [PATCH] libc/newlib: fix configure error
Date: Wed, 07 Dec 2011 04:46:00 -0000	[thread overview]
Message-ID: <4EDEEF00.3020708@rtems.org> (raw)
In-Reply-To: <201112062217.23143.vapier@gentoo.org>

On 12/07/2011 04:17 AM, Mike Frysinger wrote:
> On Tuesday 06 December 2011 21:18:16 Zhenqiang Chen wrote:
>> --- a/scripts/build/libc/newlib.sh      Wed Nov 30 12:07:59 2011 +0100
>> +++ b/scripts/build/libc/newlib.sh      Wed Dec 07 10:13:17 2011 +0800
>>
>>       AR=${CT_TARGET}-ar                                  \
>>       RANLIB=${CT_TARGET}-ranlib                          \
>>       "${CT_SRC_DIR}/newlib-$(libc_newlib_version)/configure" \
>> -        --host=${CT_BUILD}                              \
>> +        --build=${CT_BUILD}                             \
>> +        --host=${CT_HOST}                               \
>>           --target=${CT_TARGET}                           \
>
> i'd expect newlib to be like glibc and would use:
> 	--build=${CT_BUILD} --host=${CT_TARGET}
>
> does newlib even use --target= ?

The toplevel configure script does (It is GCC's/binutil's/gdb's unified 
configure script).

The newlib subdir's configure script doesn't.

So .. the answer would depend upon which configure script the patch 
above refers to.


Ralf



--
For unsubscribe information see http://sourceware.org/lists.html#faq

  reply	other threads:[~2011-12-07  4:46 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-12-07  2:18 Zhenqiang Chen
2011-12-07  3:17 ` Mike Frysinger
2011-12-07  4:46   ` Ralf Corsepius [this message]
2011-12-07  7:57     ` Zhenqiang Chen
2011-12-07  6:01   ` Zhenqiang Chen
2011-12-11 21:25 ` Yann E. MORIN
2011-12-12  3:55   ` Zhenqiang Chen

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=4EDEEF00.3020708@rtems.org \
    --to=ralf.corsepius@rtems.org \
    --cc=crossgcc@sourceware.org \
    --cc=vapier@gentoo.org \
    --cc=yann.morin.1998@anciens.enib.fr \
    --cc=zhenqiang.chen@linaro.org \
    /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).