From: "Boyce, Nick" <[EMAIL PROTECTED]>

nick.boyce> Richard> If you check the manual for ld, you'll probably
nick.boyce> Richard> find a few lines about '-f fil', where the
nick.boyce> Richard> filling is expected to be a 4-byte hex constant.
nick.boyce> 
nick.boyce> Well you're quite right; the ld man page says :
nick.boyce>   -f fill
nick.boyce>       Set the fill pattern for "holes" within an output section.  The argu-
nick.boyce>       ment fill is a four-byte hexadecimal constant.
nick.boyce> 
nick.boyce> But what I don't understand is why you're talking about a
nick.boyce> problem with "-fPIC" when my compilation objected to
nick.boyce> "-std1" ...

Ah.  Well, I'll do some qualified guesses: suppose that the command
line parser in ld is the stupid kind that checks if argv[i][0] is '-'
and then just does a switch(argv[i][1]) to process each possible switch,
and that for any switch value it will take argv[i+1].  So, it finds
your -fPIC, thinks it found -f and tries to use the next argument as
fill.  That happens to be "-std1" which is very far from a hex value,
so it complains...

And yes, I've seen that kind of parsing before, especially in pretty
old programs.

-- 
Richard Levitte   \ Spannvägen 38, II \ [EMAIL PROTECTED]
Chairman@Stacken   \ S-168 35  BROMMA  \ T: +46-8-26 52 47
Redakteur@Stacken   \      SWEDEN       \ or +46-709-50 36 10
Procurator Odiosus Ex Infernis                -- [EMAIL PROTECTED]
Member of the OpenSSL development team: http://www.openssl.org/
Software Engineer, Celo Communications: http://www.celocom.com/

Unsolicited commercial email is subject to an archival fee of $400.
See <http://www.stacken.kth.se/~levitte/mail/> for more info.
______________________________________________________________________
OpenSSL Project                                 http://www.openssl.org
User Support Mailing List                    [EMAIL PROTECTED]
Automated List Manager                           [EMAIL PROTECTED]

Reply via email to