Hi Charles,
Typo on my part (copy pasting diff scripts).
I tried building libGD in the following directory (sPREFIX is an env name I
use in scripts):
sPREFIX=${PWD}/../build/usr
This works, all files in the correct directory.
Next I try building NUT with the following params:
sPREFIX=${PWD}/../build/usr
configure \
--with-gd-includes="-I${sPREFIX}/include/libgd" \
--with-gd-libs="-L${sPREFIX}/lib64" \
......
This fails to locate LibGD and aborts.
If I build libGD using "sPREFIX=${PWD}/../build" and include this in the NUT
build
--with-gd-includes="-I${sPREFIX}/include/libgd" \
--with-gd-libs="-L${sPREFIX}/lib64" \
......
This works. It did this consistently across several openSUSE platforms.
This is a minor annoyance as normally all of the working libs are in
/usr/lib|lib64, not /lib.
Thanks,
Simon
-----Original Message-----
From: Charles Lepple [mailto:[email protected]]
Sent: Thursday, December 04, 2014 01:47
To: [email protected]
Cc: nut-upsdev
Subject: [Nut-upsdev] GD libraries and $PREFIX (was Re: building NUT on Mac
OS X Yosemite(website/documentation))
On Dec 3, 2014, at 7:05 PM, [email protected] wrote:
> One other issue I noticed is with the placement of the GD libraries,
> if they are not installed under the root it will not find them
>
> If I build GD into /build/usr and add the following lines to my make
> script for nut:
>
> PREFIX=/build/usr
>
> configure \
> --with-gd-includes="-I${sPREFIX}/include/libgd" \
> --with-gd-libs="-L${sPREFIX}/lib64" \
> ......
>
> Configure will abort with a GD libary not found. If I set
> PREFIX=/build and rebuild GD and NUT then configure will identify the
> GD libs. Not sure where the problem is exactly.
>
> (this is with the latest public code release from the git repository).
Can you elaborate on how you are using PREFIX versus sPREFIX?
--
Charles Lepple
clepple@gmail
_______________________________________________
Nut-upsdev mailing list
[email protected]
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/nut-upsdev
