[Slackbuilds-users] libs in /usr/local/lib

[Nick Warne]

On 09/03/14 14:03, Willy Sudiarto Raharjo wrote:
> On Sun 09 Mar 2014 08:51:59 PM WIT, Nick Warne wrote:
>> On 09/03/14 13:39, Nick Warne wrote:
>>> On 09/03/14 13:35, Didier Spaier wrote:
>>>> On 09/03/2014 14:30, Nick Warne wrote:
>>>>>
>>>>>
>>>>> On 09/03/14 13:19, Didier Spaier wrote:
>>>>>> On 09/03/2014 13:36, Nick Warne wrote:
>>>>>>> Using slackbuild dsniff (as an example), I find that slackbuild
>>>>>>> fails on ./configure as it thinks libnet is not installed.
>>>>>>>
>>>>>>> Now, not to confuse things, this is on my AMD64 running Slack
>>>>>>> 12.1 (no multilib) and I often build/install 'lesser used libs'
>>>>>>> into /usr/local/lib and run/update ldconfig on installation.
>>>>>>>
>>>>>>> I can configure dsniff by hand fine, all libs are found - but
>>>>>>> using the slack script, it doesn't find them...
>>>>>>
>>>>>> Alla SlackBuilds for libnet (there is none fo Salcakre 12.1)
>>>>>> include this:
>>>>>>
>>>>>> elif [ "$ARCH" = "x86_64" ]; then
>>>>>>     SLKCFLAGS="-O2 -fPIC"
>>>>>>     LIBDIRSUFFIX="64"
>>>>>>
>>>>>> So this configure option:
>>>>>> --libdir=/usr/lib${LIBDIRSUFFIX} \
>>>>>> expands to:
>>>>>> --libdir=/usr/lib64
>>>>>>
>>>>>> But there is no /usr/lib64 directory in Slackware 12.1.
>>>>>>
>>>>>> Could that be the issue?
>>>>>
>>>>> I looked at that - forgot to say too that this was a Slamd64 distro
>>>>> before Pat made the official 64bit build, so I do have a /usr/lib64
>>>>> (for years).
>>>>>
>>>>> All those $VARS do in the build is where to install the package
>>>>> libs (if you use it).
>>>>>
>>>>> And it doesn't matter where the libs are installed to - the
>>>>> 'system' knows they are there ref. ldconfig and a manual
>>>>> ./configure works...
>>>>
>>>> Then, would you mind posting your full (with all options) manual
>>>> configure command that works?
>>>
>>> Yes, sure:
>>>
>>> ./configure
>>>
>>> :)
>>>
>>> This is nothing to do with the slackbuild of dsniff!  I just used that
>>> as an example (as this is when I found this issue).
>>>
>>> I just do not know why the slackbuild ./configure doesn't see libnet
>>> libs in /usr/local/lib yet the system does!
>>>
>>> Nick
>>>
>>
>> OK, I was thinking, I use 'sudo' and wondered if it was an ENV thing
>> going on:
>>
>> sudo ./dsniff.Slackbuild
>> ...
>> checking for Berkeley DB with 1.85 compatibility... yes
>> checking for libpcap... yes
>> checking for libnet... no
>> configure: error: libnet not found
>>
>> Now log in as 'real' root:
>>
>> ./dsniff.Slackbuild
>> ...
>> checking for Berkeley DB with 1.85 compatibility... yes
>> checking for libpcap... yes
>> checking for libnet... no
>> configure: error: libnet not found
>>
>> Now as normal user (me) in dsniff directory:
>>
>> ./configure
>> ...
>> checking for Berkeley DB with 1.85 compatibility... yes
>> checking for libpcap... yes
>> checking for libnet... yes
>> checking for libnids... yes
>> checking whether libnids version is good... yes
>> checking for OpenSSL... yes
>> creating ./config.status
>> creating Makefile
>> creating config.h
>> config.h is unchanged
>>
>> Huh!  See what I mean?
>
> Have you checked the $PATH?

No...
Yes, now I have - there is no such $VAR in the script.  But 'tis only a 
bash script that calls ./configure so I honestly don't know why it fails.

As I say, I am beat on this.

Nick
-- 
"A bug in the code is worth two in the documentation."
FSF Associate Member 5508
http://linicks.net/
http://pi.linicks.net/