Re: Problems with AIX4 Compiler

[Tim Mooney]

In regard to: Re: Problems with AIX4 Compiler, address@hidden said...:

>I'm not positive, but that is how most of the other flags work.
>The man page isn't too clear in this case though.
>
>I guess the only way to find out is to test it.

Our signals were crossed.  In the first paragraph I was indeed wondering
about the later -Wl,-blibpath,$libdir:/usr/lib:/lib completely overriding
the earlier -nolibpath, but I was hypothesizing that there must be (or must
have been) some need for it.

After the sentence that starts with "In addition", I'm wondering about
the *other* "override" -- there are two instances of an _LT_AC_TAGVAR for
hardcode_libdir_flag_spec.  My guess is the first one of those is getting
overriden.  That's what I was asking about in the last question.

>> From address@hidden Wed Jul 18 17:30:53 2001
>> From: Tim Mooney <address@hidden>
>>
>> I was looking at that too, and wondering why it made it into libtool.
>> It must have solved some problem for someone, but it makes me wonder.
>> In addition, in that section in libtool-1.4b's libtool.m4, I see:
>>
>>         _LT_AC_TAGVAR(hardcode_libdir_flag_spec, $1)='${wl}-bnolibpath 
>> ${wl}-blibpath:$libdir:/usr/lib:/lib'
>>
>> [bunch of stuff deleted]
>>
>>         _LT_AC_TAGVAR(hardcode_libdir_flag_spec, 
>> $1)='${wl}-blibpath:$libdir:/usr/lib:/lib'
>>
>>
>> Does that mean what I think it does -- the first one is getting overridden
>> by the second one?

Tim
-- 
Tim Mooney                              address@hidden
Information Technology Services         (701) 231-1076 (Voice)
Room 242-J6, IACC Building              (701) 231-8541 (Fax)
North Dakota State University, Fargo, ND 58105-5164