This is the mail archive of the crossgcc@sources.redhat.com 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] |
I'm currently doing some experiments w/ the latest crosstool.
The build seems to be fine, but now some questions about best practise for production system installation ...
a) I'm doing no real crosscompile, instead using it for cleanroom
(jail) builds via sysroot. Should I somehow fake the platform identifier to be able to
pass it via --host=xxx to applications ?
However, if you're going to the trouble of using a jail, and you're not cross-compiling, you don't need to pass --host, --build, or --target when configuring apps, I think.
b) I'd like to have short binary names (w/o platform), when passing the commands to the builders. How can I specify this ?
One other thing: you might want to edit the spec file of the resulting toolchain so it doesn't think it's a cross-compiler. See http://sources.redhat.com/ml/crossgcc/2004-06/msg00161.html Otherwise it won't search your jail's /lib and /usr/lib.
------ Want more information? See the CrossGCC FAQ, http://www.objsw.com/CrossGCC/ Want to unsubscribe? Send a note to crossgcc-unsubscribe@sources.redhat.com
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |