Dear Sam:

        Thank you for replying. I tried to keep my original message brief, and 
must have tried too hard. I also had thought that I should use a preconfigured 
installation. I originally installed the FreeBSD libtool package, then 
installed the port, and finally installed from source as a last resort. The 
courier-auth configure script never could find any of the three installed 
ltdl.h files. All ltdl.h files are still installed, and are identical. I tried 
copying the original ltdl.h file from /user/local/include to /usr/include, 
which does include other header files, but the courier-authlib configure script 
still fails with the same error: Unable to find ltdl.h.

        You mentioned that I could “pass CPPFLAGS to configure.” Unless you 
have a better suggestion about what to try next, please point me toward any 
documentation available about how to appropriately pass CPPFLAGS to the 
configure script.

        With continuing appreciation,

        Michael

> On Dec 12, 2016, at 5:22 PM, Sam Varshavchik <mr...@courier-mta.com> wrote:
> 
> Michael S. Scaramella, Esq. writes:
> 
>> Libtool 2.4.6 and Courier Unicode 1.4 are now reinstalled from source. I ran 
>> the Libtool configure script as “./configure --prefix=/usr/local 
>> --exec-prefix=/usr/local --sysconfdir=/usr/local/etc/libtool 
>> --localstatedir=/var --includedir=/usr/local/include/libtool” which 
>> completed successfully. Running gmake and gmake install installed two copies 
>> of ldtl.h, one at /usr/local/share/libtool/, and another at 
>> /usr/local/include/libtool/. The following are relevant excerpts from the 
>> terminal session:
> 
> Just because you installed some files in some directory doesn't mean that 
> your compiler will automatically find them.
> 
> Typically, a compiler searches for header files in /usr/include, and maybe 
> /usr/local/include. If you stick something somewhere else, you have to tell 
> the compiler, it won't find it for you. You can pass CPPFLAGS to configure, 
> to specify an additional compilation flags.
> 
> However, your approach is overall wrong. I'm sure that libtool is already 
> properly packaged for FreeBSD. I'm sure it's somewhere in the ports tree, and 
> all you have to do is install it, and it will be properly installed in 
> /usr/include, /usr/lib, and all the usual default system directories, where 
> all applications will find them, by default.

<+>-=-<+>-=-<+>-=-<+>-=-<+>-=-<+>-=-<+>

SCARAMELLA & HOOFNAGLE
Computer Division
 ~  *  ~
Voice: 856-424-2100
Web: http://www.ScaraHoof.com

<+>-=-<+>-=-<+>-=-<+>-=-<+>-=-<+>-=-<+>

------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most 
engaging tech sites, SlashDot.org! http://sdm.link/slashdot
_______________________________________________
courier-users mailing list
courier-users@lists.sourceforge.net
Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users

Reply via email to