Skip site navigation (1)Skip section navigation (2)
Date:      Fri, 2 Nov 2012 10:49:08 +0100
From:      Polytropon <>
To:        James Colannino <>
Subject:   Re: Autotools, libraries and man pages: oh my!
Message-ID:  <>
In-Reply-To: <>
References:  <> <>

Next in thread | Previous in thread | Raw E-Mail | Index | Archive | Help
On Thu, 01 Nov 2012 22:01:16 -0700, James Colannino wrote:
> On 11/01/12 21:44, James Colannino wrote:
> > [...]I'm able to use autotools on FreeBSD to
> > generate configure and, and can use gmake to compile and
> > install it.
> >
> > Unfortunately, the man pages are installed to /usr/local/share/man
> > instead of to /usr/local/man, which I thought the tools would've taken
> > care of.  Also, even though I see my library was successfully compiled
> > and installed to /usr/local/lib, when I try to compile a program with
> > gcc source.c -ldstring, I get:
> >
> > /usr/bin/ld: cannot find -ldstring
> Update: I can compile against my dstring library by using the following
> line:
> gcc source.c -L/usr/local/lib -ldstring.  I guess it didn't know to
> search /usr/local/lib.  Still having trouble figuring out how to install
> the man pages properly, though :(

The easiest way to do it is to have a look at the porter's
handbook (part of the FreeBSD documentation) and use the
predefined target locations for the generated components.

However, I always thought /usr/local/lib would be one of
the default search paths for ld, so -l<library> for any
library residing there should be fine - except of course
you override default options of cc...

For your project, you could create a Makefile containing
the required CFLAGS and LDFLAGS, define a rule for building
the target and then just use "make".

Magdeburg, Germany
Happy FreeBSD user since 4.0
Andra moi ennepe, Mousa, ...

Want to link to this message? Use this URL: <>