| delorie.com/archives/browse.cgi | search |
--_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 =
<whatever> 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
<html>
<head>
<style>
.hmmessage P
{
margin:0px=3B
padding:0px
}
body.hmmessage
{
FONT-SIZE: 10pt=3B
FONT-FAMILY:Tahoma
}
</style>
</head>
<body class=3D'hmmessage'>
I'm being loose with words. It isn't cheating=2C it is exactly what you hav=
e to do.<BR>
 =3B<BR>
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.<BR>
 =3B<BR>
I understand=2C but my wording is poor.<BR>
 =3B<BR>
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.<BR>
 =3B<BR>
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:)<BR>
 =3B<BR>
 =3B- Jay<BR><BR><BR>>=3B Date: Mon=2C 7 Jul 2008 21:31:25 -0400<BR>&=
gt=3B From: dj AT delorie DOT com<BR>>=3B To: jayk123 AT hotmail DOT com<BR>>=3B CC: =
djgpp AT delorie DOT com<BR>>=3B Subject: Re: libstdc++ writev/2.04/patches upst=
ream?<BR>>=3B <BR>>=3B <BR>>=3B >=3B Having a native compiler and l=
inker I label "cheating".<BR>>=3B <BR>>=3B Having a native *linux* comp=
iler and trying to build a djgpp *cross*<BR>>=3B with it is certainly not=
cheating.<BR>>=3B <BR>>=3B >=3B You have to start somewhere -- from =
some binaries=2C that are runnable<BR>>=3B >=3B somewhere=2C not just s=
ource.<BR>>=3B <BR>>=3B Those are the natives on the system on which yo=
u're building the<BR>>=3B cross.<BR><BR></body>
</html>=
--_6d8c8a59-d812-4750-bdee-dc3a474a9724_--
| webmaster | delorie software privacy |
| Copyright © 2019 by DJ Delorie | Updated Jul 2019 |