This is the mail archive of the
binutils@sources.redhat.com
mailing list for the binutils project.
Re: [RFA] [pei-386] prevent ld (auto-import) from generating broken code
DJ Delorie wrote:
>> Second, we're merely arguing about which of two alternatives to
*recommend*,
>> while still presenting BOTH alternatives -- in the documentation.
>> (Unless you're arguing for eliminating all references to my
>> preferred alternative?)
>>
>
> Would it be reasonable to refer to the manual in the error message?
> I think we can document all the known workarounds (and dwarbacks of
each), but we can't do it clearly if we're limited to doing it in the
> error message.
>
>
stringtest.o: In function `main':
/usr/src/binutils/tmp/stringtest.c:9: aggregate 'hwstr1' is referenced
in direct addressing mode with constant offset - auto-import failed.
Workarounds: a) use a 'volatile' auxilliary variable; b) mark the symbol
with __declspec(dllimport)
collect2: ld returned 1 exit status
> > each), but we can't do it clearly if we're limited to doing it in
> the error message.
>
>
Currently, the message reads:
stringtest.o: In function `main':
/usr/src/binutils/tmp/stringtest.c:9: aggregate 'hwstr1' is referenced
in direct addressing mode with constant offset - auto-import failed.
Workarounds: a) use a 'volatile' auxilliary variable; b) mark the symbol
with __declspec(dllimport)
collect2: ld returned 1 exit status
Perhaps this:
stringtest.o: In function `main':
/usr/src/binutils/tmp/stringtest.c:9: aggregate 'hwstr1' is referenced
in direct addressing mode with constant offset - auto-import failed.
Workarounds: a) use a 'volatile' auxilliary variable; b) mark the symbol
with __declspec(dllimport). For more information, see
ld.info::Invocation::Options::--enable-auto-import
collect2: ld returned 1 exit status
?
--Chuck