X-Authentication-Warning: delorie.com: mail set sender to djgpp-bounces using -f X-Recipient: dj AT delorie DOT com X-Recipient: djgpp AT delorie DOT com Message-ID: Content-Type: multipart/alternative; boundary="_6d8c8a59-d812-4750-bdee-dc3a474a9724_" X-Originating-IP: [131.107.0.103] From: Jay To: DJ Delorie CC: Subject: RE: libstdc++ writev/2.04/patches upstream? Date: Tue, 8 Jul 2008 01:41:31 +0000 Importance: Low In-Reply-To: <200807080131.m681VPmg009267@envy.delorie.com> References: <200807070405 DOT m67451dZ010910 AT delorie DOT com> <200807071920 DOT m67JKA4v032518 AT envy DOT delorie DOT com> <200807072141 DOT m67Lf1A6003751 AT envy DOT delorie DOT com> <200807072346 DOT m67NklaB006801 AT envy DOT delorie DOT com> <200807080131 DOT m681VPmg009267 AT envy DOT delorie DOT com> MIME-Version: 1.0 X-OriginalArrivalTime: 08 Jul 2008 01:41:31.0483 (UTC) FILETIME=[BF580AB0:01C8E09B] Errors-To: nobody AT delorie DOT com X-Mailing-List: djgpp AT delorie DOT com X-Unsubscribes-To: listserv AT delorie DOT com Precedence: bulk --_6d8c8a59-d812-4750-bdee-dc3a474a9724_ Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable I'm being loose with words. It isn't cheating=2C it is exactly what you hav= e to do. =20 Think of someone maybe a bit beginnerish who gets a bug in their head about= wanting to build "everything" from source. Where does it end? Well=2C you = can build "the whole system"=2C given the source=2C but you have to start w= ith some minimal sort of working system. =20 I understand=2C but my wording is poor. =20 And then=2C since we have a system already up and running=2C I am/was willi= ng to forgo some of the bootstrapping steps and start with a sys-root=2C in= cluding libraries=2C which=2C I understand=2C is not what you have to do=2C= is often what you CANNOT do=2C but is maybe a reasonable shortcut when pos= sible. =20 btw=2C just compiling against writev would be ok too=2C but of course not a= s I showed=2C only if there is a declaration -- don't need a code generator= =2C just a correctly configured cross C preprocessor that handles #include = for the target. :) =20 - Jay> Date: Mon=2C 7 Jul 2008 21:31:25 -0400> From: dj AT delorie DOT com> To: j= ayk123 AT hotmail DOT com> CC: djgpp AT delorie DOT com> Subject: Re: libstdc++ writev/2.= 04/patches upstream?> > > > Having a native compiler and linker I label "ch= eating".> > Having a native *linux* compiler and trying to build a djgpp *c= ross*> with it is certainly not cheating.> > > You have to start somewhere = -- from some binaries=2C that are runnable> > somewhere=2C not just source.= > > Those are the natives on the system on which you're building the> cross= .= --_6d8c8a59-d812-4750-bdee-dc3a474a9724_ Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable I'm being loose with words. It isn't cheating=2C it is exactly what you hav= e to do.
=3B
Think of someone maybe a bit beginnerish who gets a bug in their head about= wanting to build "everything" from source. Where does it end? Well=2C you = can build "the whole system"=2C given the source=2C but you have to start w= ith some minimal sort of working system.
=3B
I understand=2C but my wording is poor.
=3B
And then=2C since we have a system already up and running=2C I am/was willi= ng to forgo some of the bootstrapping steps and start with a sys-root=2C in= cluding libraries=2C which=2C I understand=2C is not what you have to do=2C= is often what you CANNOT do=2C but is maybe a reasonable shortcut when pos= sible.
=3B
btw=2C just compiling against writev would be ok too=2C but of course not a= s I showed=2C only if there is a declaration -- don't need a code generator= =2C just a correctly configured cross C preprocessor that =3Bhandles #i= nclude <=3Bwhatever>=3B for the target. =3B:)
=3B
=3B- Jay

>=3B Date: Mon=2C 7 Jul 2008 21:31:25 -0400
&= gt=3B From: dj AT delorie DOT com
>=3B To: jayk123 AT hotmail DOT com
>=3B CC: = djgpp AT delorie DOT com
>=3B Subject: Re: libstdc++ writev/2.04/patches upst= ream?
>=3B
>=3B
>=3B >=3B Having a native compiler and l= inker I label "cheating".
>=3B
>=3B Having a native *linux* comp= iler and trying to build a djgpp *cross*
>=3B with it is certainly not= cheating.
>=3B
>=3B >=3B You have to start somewhere -- from = some binaries=2C that are runnable
>=3B >=3B somewhere=2C not just s= ource.
>=3B
>=3B Those are the natives on the system on which yo= u're building the
>=3B cross.

= --_6d8c8a59-d812-4750-bdee-dc3a474a9724_--