This is the mail archive of the gcc-patches@gcc.gnu.org mailing list for the GCC project.
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |
Other format: | [Raw text] |
Geoffrey Keating wrote:
Mark Mitchell <mark@codesourcery.com> writes:
Geoffrey Keating wrote:
Mark Mitchell <mark@codesourcery.com> writes:
+ The GNU linker (beginning with version 2.16) has the necessary support
+ for this option. If your linker does not support this option, the
+ header file aspect of @option{--sysroot} will still work, but the
+ library aspect will not.
This is a regression on Darwin; there, -isysroot already passes -syslibroot to the linker.
I didn't change anything about what -isysroot does; if on Darwin it has extra semantics, then it still should. Is that not true?
The regression is that now the documentation doesn't match the implementation...
I think the documentation is accurate.
As far as I can tell from looking at the mainline sources, the Darwin linker does not support --sysroot (it uses some other name), and the configure script does not set HAVE_LD_SYSROOT on Darwin, so the driver --sysroot option does not work on Darwin when linking. If someone changes the driver so that on Darwin --sysroot translates into the right linker option, then the documentation will need updating too.
Are you saying that the --sysroot driver option works on Darwin?
@item -isysroot @var{dir} @opindex isysroot This option is like the @option{--sysroot} option, but applies only to header files. See the @option{--sysroot} option for more information.
Attachment:
smime.p7s
Description: S/MIME cryptographic signature
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |