On Wed, Mar 5, 2008 at 1:35 AM, Alexander E. Patrakov <[EMAIL PROTECTED]> wrote:
> - It has a lot of legacy features that were oriented to the old > versions of autoconf (see, for example, how the %makeinstall macro > expands--BTW RedHat doesn't use this macro) Nobody uses this anymore, but it can be useful in the case of a Makefile with hardcoded directories. http://gitweb.dwcab.com/?p=pound.git;a=blob;f=jpeg/jpeg.spec;hb=HEAD > - The %configure macro interferes (ore, more correctly, duplicates or > overlaps in functionality) with config.site files, but the > autogenerated spec files are not expected to use this macro, so this > is likely to be a non-issue. However, in this case, setting the > default CFLAGS from RPM macros, as documented, will stop working. I don't consider this a bad thing since your rpm macros essentially deprecate config.site. echo '%_prefix /usr/local' >> ~/.rpmmacros. Also, you can easily write your own %configure replacement if you prefer config.site: cat > /etc/rpm/macros.lfs << "EOF" %configure \ export CFLAGS="${CFLAGS:-%optflags}"; \ export CXXFLAGS="${CXXFLAGS:-%optflags}; \ export CONFIG_SITE=/path/to/config.site; \ ./configure EOF I'm pretty sure that Mandriva and SUSE override the default %configure. I'm personally considering overriding it so that I can specify the shell to call configure with since a lot of them have bashisms. I don't want to hijack this thread into a merits of RPM thread, but just wanted to comment on those two points. -- Dan -- http://linuxfromscratch.org/mailman/listinfo/lfs-dev FAQ: http://www.linuxfromscratch.org/faq/ Unsubscribe: See the above information page
