On Jul 25, 2007, at 3:29 PM, Robert Scheck wrote:

> On Wed, 25 Jul 2007, Jeff Johnson wrote:
>> What does "... 386-linux is favoured over the i386-redhat-linux- 
>> gnu ..."
>> mean precisely? Some macro being loaded from i386-linux/macros
>> rather than i386-redhat-linux-gnu/macros?
>
> yes, but when having a look to --showrc output, I saw, that I were  
> simply
> wrong. Only i386-linux/macros is in macros per default.
>

Yes. A long time ago, when redhat-rpm-config was born, a private
gentleman's agreement was established with the Red Hat build master.

rpm looks only at CPU-OS/macros, while redhat-rpm-config uses only
CPU-VENDOR-OS/macros.

So the existing rpm-4.4.7 (and later) behavior without rpmrc by default
never looks at CPU-VENDOR-OS/macros.

>> Macro file loading epends on the macrofiles path, a colon  
>> separated list of
>> files to --macros
>> will take the mystery out of what rpm reads (so will strace spew
>> examination).
>>
>> Any desired behavior can be achieved by defaulting the compiled in  
>> value
>> of macrofiles to read to Something Else Instead.
>
> Where are the macro files defined? Is this a build time thing? Yes  
> I know,
> there is --macros, but how to overwrite the defaults?
>

The compiled in default paths are arranged by configure during rpm  
build, yes.

Compiling in different and/or additional paths is rather easy to  
arrange.

Adding ...:%{_usrlibrpm}/%{_target_platform}/macros:... to the  
compiled in macrofiles
paths is likely all that is needed.

73 de Jeff