Ludo Brands wrote:
One thing I don't understand is whether there's any scope for the
computer type that's optionally fed to binutils's ./configure
to appear
in the final programs (ld for Solaris etc.). I definitely see
references
to sol2 as the final part of this parameter in config.sub which I
believe is used to check and parse the type, where it's used
to specify
that the OS is -solaris2 rather than -sysv etc.
That is how cross binutils are made. On system x you do a configure
--prefix=dir-to-put-tools
--host=the-host --target=the-target
The config.guess script is used by configure when you don't specify a
target.
More usefull info here:
http://wiki.osdev.org/OS_Specific_Toolchain
Yes, but you can also do e.g.
$ ./configure --prefix=/usr/local/mipsel-linux mipsel-linux-gnu
and what I was wondering was whether the final portion of the parameter
could, in some cases, "leak" into the binaries e.g. into ld's embedded
script, resulting in the sort of problem that Joost reported:
>>>>> At first it did not work. I've edited the file, changed the
>>>>> output-format in the script from 'elf32-i386-sol2' to 'elf32-i386'
>>>>> and now it works.
--
Mark Morgan Lloyd
markMLl .AT. telemetry.co .DOT. uk
[Opinions above are the author's, not those of his employers or colleagues]
_______________________________________________
fpc-devel maillist - [email protected]
http://lists.freepascal.org/mailman/listinfo/fpc-devel
