Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe:	<mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive:	<http://sources.redhat.com/ml/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-help AT cygwin DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender:	cygwin-owner AT cygwin DOT com
Delivered-To:	mailing list cygwin AT cygwin DOT com
Date:	Tue, 29 Jan 2002 23:06:29 +0000
Message-ID:	<5052-Tue29Jan2002230629+0000-starksb@ebi.ac.uk>
X-Mailer:	21.5 (beta2) "artichoke" XEmacs Lucid (via feedmail 9-beta-7 I);
	VM 7.00 under 21.5 (beta2) "artichoke" XEmacs Lucid
From:	David Starks-Browning <starksb AT ebi DOT ac DOT uk>
MIME-Version:	1.0
To:	posting-list AT MailAndNews DOT com (Jari Aalto+list.cygwin)
Cc:	cygwin AT cygwin DOT com
Subject:	Packaging questions?
In-Reply-To:	<it9kx2ae.fsf@blue.sea.net>
References:	<it9kx2ae DOT fsf AT blue DOT sea DOT net>

On Tuesday 29 Jan 02, Jari Aalto+list.cygwin writes:
> 
> I have a quostion about the packaging page that says:
> 
>     The package is configured using (at a minimum) the following paths: 
>       --prefix=/usr
>       --sysconfdir=/etc
>       --libexecdir='$(sbindir)'
>       --localstatedir=/var
>       --datadir='$(prefix)/share'
> 
> What are the values of $(sbindir) and $(prefix)? At least Berkeley
> DB does not accept these parameters straight:
> 
>     configure: error: expected an absolute path for --libexecdir: 

I recall from building BerkeleyDB on UNIX (not Cygwin) that it did not
have complete autoconf support.  My advice for BerkeleyDB is to simply
build it with --prefix=/usr and see where everything goes.  I bet you
get lucky.  (I had required distinct --prefix and --exec-prefix, and
BerkeleyDB could not accomodate that.)

You might check another package, but I suspect that $(sbindir) is
/usr/sbin.  (Hmm, there is also stuff in my Cygwin /usr/libexec, were
those packages built incorrectly?)

Hope this helps.

David


--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

- Raw text -