Send inn-workers mailing list submissions to
        [email protected]

To subscribe or unsubscribe via the World Wide Web, visit
        https://lists.isc.org/mailman/listinfo/inn-workers
or, via email, send a message with subject or body 'help' to
        [email protected]

You can reach the person managing the list at
        [email protected]

When replying, please edit your Subject line so it is more specific
than "Re: Contents of inn-workers digest..."


Today's Topics:

   1. Build with Berkeley DB and CURRENT (Julien ?LIE)


----------------------------------------------------------------------

Message: 1
Date: Fri, 20 Sep 2013 21:39:38 +0200
From: Julien ?LIE <[email protected]>
To: "[email protected]" <[email protected]>
Subject: Build with Berkeley DB and CURRENT
Message-ID: <[email protected]>
Content-Type: text/plain; charset=windows-1252; format=flowed

Hi all,

If you are using CURRENT with Berkeley DB support, please note that the 
behaviour of --with-berkeleydb has slightly changed:
     http://inn.eyrie.org/trac/changeset/9536

During the build, default search paths are no longer added to the 
compiler and linker include flags.  It will prevent for instance 
-L/usr/lib to be added; it could otherwise break the build, especially 
when /usr/lib32 or /usr/lib64 are also present on the system.

INN was also searching in /usr/local and in PREFIX (set at configure time).
Paths are now added only if explicitly given to one or more of the 
--with-berkeleydb, --with-berkeleydb-include, or --with-berkeleydb-lib 
configure flags.  These last two flags are new.


If you notice anything suspicious during your builds of CURRENT with 
Berkeley DB, please report the issue you are facing.

-- 
Julien ?LIE

? ? Nous parlerons quand l'interpr?te dormira. [Bong !]
   ? Il dort. On peut parler. ? (Ast?rix)


------------------------------

_______________________________________________
inn-workers mailing list
[email protected]
https://lists.isc.org/mailman/listinfo/inn-workers

End of inn-workers Digest, Vol 55, Issue 3
******************************************

Reply via email to