Eric Blake wrote:
According to Ivan Levashew on 2/12/2009 11:59 AM:
Generally, I'd like build system and compiler to be as humble as
possible. Don't run tests on my platform, don't look for libraries and
headers in my /usr directory. If something is not specified by means of
command line or environment variables, it doesn't exist. The only
exception is libraries/headers provided by compiler (which is specified
on command line anyway). OS headers should be taken from SDKs and never
from my system.
This sounds like the perfect use case for a chroot jail. As a maintainer,
you should be capable of creating a bare-bones environment for testing
your builds against an older or less complete installation than what you
run on a day-to-day environment. In fact, many of the distros have tools
to make doing this task easier. I think that you may be better served by
learning how those distro package-preparation tools work to simulate the
oldest supported environment.
I'm doing something like this (by means of -isysroot). I'm creating
symlinks to SDK directories and put my libraries in the same root. The
problem is that I have to gather everything together. It's a lengthy
operation. Maybe unionfs will do here.
Anyway, I'm gonna try using -dylib_file install_name:file_name linker
option. This option must be provided for every indirectly reachable
library, and that's why I rejected it on my first build system. Now I
will try to automate the work.
--
If you want to get to the top, you have to start at the bottom
_______________________________________________
Autoconf mailing list
Autoconf@xxxxxxx
http://lists.gnu.org/mailman/listinfo/autoconf
