X-Authentication-Warning:	delorie.com: mail set sender to djgpp-bounces using -f
Date:	Mon, 7 Jul 2008 19:46:47 -0400
Message-Id:	<200807072346.m67NklaB006801@envy.delorie.com>
From:	DJ Delorie <dj AT delorie DOT com>
To:	jayk123 AT hotmail DOT com
CC:	djgpp AT delorie DOT com
In-reply-to:	<BAY139-W45413141F49024B6BBB218E6940@phx.gbl> (message from Jay
	on Mon, 7 Jul 2008 23:40:10 +0000)
Subject:	Re: libstdc++ writev/2.04/patches upstream?
References:	<200807070405 DOT m67451dZ010910 AT delorie DOT com>
	<BAY139-W19808358F507B7930E7F6EE6940 AT phx DOT gbl>
	<200807071920 DOT m67JKA4v032518 AT envy DOT delorie DOT com>
	<BAY139-W3281EFF9FE7174C4D5C2FEE6940 AT phx DOT gbl>
	<200807072141 DOT m67Lf1A6003751 AT envy DOT delorie DOT com> <BAY139-W45413141F49024B6BBB218E6940 AT phx DOT gbl>
Errors-To:	nobody AT delorie DOT com
X-Mailing-List:	djgpp AT delorie DOT com
X-Unsubscribes-To:	listserv AT delorie DOT com

>  > It's not, but automated testing for *any* cross is nearly impossible  > without some manual intervention. That's why we have special cases 
>  
> I (naively?) disagree. You can do lots of compile and link tests, but not any run tests.
> Do you count setting up a sys-root ahead of time "manual intervention"? If so, ok.

I do.  For many cross targets, you start with nothing, so you can't do
link tests until after the C library is built, but you can't build the
C library until the compiler is built, etc.

And many of the tests are "run this" tests; compiling and linking
isn't always sufficient.

> You have to "cheat" in any case, like starting with a compiler and
> linker from somewhere.

Um, no.  I do cross compilers starting with only a native compiler and
the original sources.  Note that writing cross development tools is my
day job - I do this all the time.

- Raw text -