[Cooker] Does /usr/lib/rpm/platform/i686-linux/macros get used?

[vatbier]

How do you compile for i686 on Mandriva?
In /usr/lib/rpm/manbo/rpmrc I see:
 macrofiles:
 /usr/lib/rpm/macros:/usr/lib/rpm/%{_target}/macros:/etc/rpm/macros.*:/etc/rpm/macros:/etc/rpm/%{_target}/macros:/etc/rpm/macros.d/*.macros:~/.rpmmacros
   
"/usr/lib/rpm/%{_target}/macros" is not the same as
"/usr/lib/rpm/platform/i686-linux/macros".
And what are all the *.macros files for in /etc/rpm/macros.d and how do
you choose to compile for one of those *.macros files?

To compile for i686 do I have to put this line:
 buildarchtranslate: i686: i686
in my .rpmrc file?
 
And does this line of /usr/lib/rpm/manbo/rpmrc:
 optflags: i686 %{__common_cflags_with_ssp} -fomit-frame-pointer -march=i686 -fasynchronous-unwind-tables
get used when compiling for i686 or is there some other optflags line of
some other macro that gets used?

vatbier


     

[Colin Guthrie-8]

'Twas brillig, and vatbier at 02/07/09 23:21 did gyre and gimble:

> And what are all the *.macros files for in /etc/rpm/macros.d and how do
> you choose to compile for one of those *.macros files?

I'm not an expert in the other fields, but whenever you see a folder
ending in .d, it generally means *all* the files in that folder are
parsed as part of the overall config. e.g. compare it to /etc/php.d and
/etc/modprobe.d and /etc/httpd/conf/vhost.d.

This is basically a configuration extension to make packaging easier. If
each of the apps in question only parsed one config file, any package
that extends that app (e.g. a php module) would have to edit the main
config file. This is unworkable in a modular system.

So just htink of .d folders as extensions to the a single config file.

Col


--

Colin Guthrie
cguthrie(at)mandriva.org
http://colin.guthr.ie/

Day Job:
   Tribalogic Limited [http://www.tribalogic.net/]
Open Source:
   Mandriva Linux Contributor [http://www.mandriva.com/]
   PulseAudio Hacker [http://www.pulseaudio.org/]
   Trac Hacker [http://trac.edgewall.org/]