libtool-patches
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Patch for installations that use an install prefix


From: Brad
Subject: Re: Patch for installations that use an install prefix
Date: Thu, 25 Jul 2002 20:18:00 -0400 (EDT)

In OpenBSD's case we have what is known as the FAKE system, a program that
is in our ports tree will be configured with a prefix of /usr/local but
when it comes time to creating the package for installation then it will
be installed into a sort of temporary work area, in this work area we
create a directory hierarchy that mimics the final installation path. When
the "fake install" step happens it will set DESTDIR (or some other
variable name that provides equivalent functionality, depending on the
Makefile(s)) to /usr/ports/devel/glib/w-glib-1.2.10/fake-macppc for
example.

phatty:local {136} pwd
/usr/ports/devel/glib/w-glib-1.2.10/fake-macppc/usr/local
phatty:local {137} ls -la
total 22
drwxr-xr-x  11 root  wheel  512 Jul 25 20:03 .
drwxr-xr-x   3 root  wheel  512 Jul 25 20:03 ..
drwxr-xr-x   2 root  wheel  512 Jul 25 20:03 bin
drwxr-xr-x   4 root  wheel  512 Jul 25 20:03 include
drwxr-xr-x   2 root  wheel  512 Jul 25 20:03 info
drwxr-xr-x   4 root  wheel  512 Jul 25 20:03 lib
drwxr-xr-x   3 root  wheel  512 Jul 25 20:03 libdata
drwxr-xr-x   2 root  wheel  512 Jul 25 20:03 libexec
drwxr-xr-x  25 root  wheel  512 Jul 25 20:03 man
drwxr-xr-x   2 root  wheel  512 Jul 25 20:03 sbin
drwxr-xr-x   9 root  wheel  512 Jul 25 20:03 share

Then the package is created with this temp area path as the root.

I don't know exactly how Debian and RPMs work but it is my understanding
that they both have a similar system for creating their packages.

// Brad

address@hidden
address@hidden

>Date: Thu, 25 Jul 2002 18:25:29 -0500
>From: Albert Chin <address@hidden>
>Reply-To: address@hidden
>To: address@hidden
>Subject: Re: Patch for installations that use an install prefix
>
>On Tue, Jul 09, 2002 at 06:24:03PM -0700, Ossama Othman wrote:
>> The following patch was submitted to Debian's bug tracking system to
>> correct problems with the fact that libtool cannot handle situations
>> where the final install destination and the current install
>> destination are not the same.  I believe that it was originally
>> obtained from the Debian ORBit package.  This situation occurs, for
>> example, when installing binaries into the installation directory of a
>> Debian package.  Upon installing the Debian package, those binaries
>> will ultimately be installed into the appropriate system location
>> (e.g. `/usr/lib').
>
>Huh? Is this a patch for?
>  $ ./configure --prefix=/tmp/a
>  $ make
>  $ maek prefix=/tmp/b
>
>Do you have a link to the BTS entry?
>
>--
>albert chin (address@hidden)




reply via email to

[Prev in Thread] Current Thread [Next in Thread]