]] Daniel Pocock | > The only variation to gcc is the -64 flag - this should be transparent, | > you should have to do nothing special until you overload your box with | > multiple flavors. | > | The real issue is not the -64 flag - that is usually added by the | configure script that is calling apr-X-config anyway. The real issues | that arise: | | - the output of `apr-X-config --ld-flags' will always be .../lib or | .../lib64, depending on which version of apr-X-config was installed | most recently
You should not add the -L path if it's part of the system search path as that'll confuse gcc in some cases. | I'm not suggesting apr needs to implement something special for every | weird setup. Rather, it just needs a generalisation that can be | applied in the most popular cases (probably RHEL and Debian). Some | possible solutions that I haven't completely thought through: In Debian, if you want to build for another environment, use a chroot (or a VM). -- Tollef Fog Heen UNIX is user friendly, it's just picky about who its friends are
