[Top][All Lists]

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

Re: Compiling into chroot

From: Bob Friesenhahn
Subject: Re: Compiling into chroot
Date: Thu, 12 Jun 2008 15:07:39 -0500 (CDT)

On Thu, 12 Jun 2008, Alon Bar-Lev wrote:

Currently libtool is the only tool making the problems, I need to keep
modifying the .la files over and over, and then restore them. And I
still get the full path of the host system within the libraries and
executables, this is unexpected side result of clean chroot.

Libtool is only causing problems because you dramatically altered the build environment. Once libtool is adjusted you may find that some other build tool is to blame for the next problem. Other build tools often insert full paths into built objects and libraries (without being directed to by libtool).

The best path forward is that if you feel strongly enough about this, then prepare a patch for libtool which works for you. The patched libtool needs to be tested on various host environments to make sure that it still passes all of its tests. It needs to work for C, C++, and other languages that libtool supports. If the patched libtool only works properly for one host environment, then it is not worth accepting into libtool.

Bob Friesenhahn
GraphicsMagick Maintainer,

reply via email to

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