On Jan 7, 2008, at 8:11 PM, Michael Jennings wrote:
>
> On Friday, 04 January 2008, at 19:07:10 (-0500),
> Jeff Johnson wrote:
>
>> The default for @libdir@ is /usr/lib in autoconf, and so is the
>> default in rpm macros.
>>
>> The per-platform config override is in the top level
>> cpu-os-macros.tar.gz.
>>
>> I hear I screwed %_arch on ppc by generating on x86, so examine.
>
> The cpu-os-macros tarball isn't included with the packages available
> on rpm5.org; it appears to only be in CVS.  Does this need to change?
>

Definitely should change if per-platform macros from static content
in a tarball is the delivery mechanism. Well duh ;-)

>> The right way (imho) is still with per-platform macro configuration.
>>
>> The script that used to generate /usr/lib/rpm/CPU-OS/macros used
>> rpmrc arch/os compatibility to generate.
>>
>> All that is needed is some other means to generate the per-platform
>> macros.
>>
>> FWIW, none of those values have changed for years and years, so the
>> tarball with all the per-platform macros should be gud enuf as a
>> distribution mechanism.
>
> Seems reasonable to me.  The other thought I had was doing a
> substitution of `basedir ${libdir}` in configure.ac for macros.in
> instead of hard-coding "lib" as it is now.  (e.g., %_lib  
> lib@LIBSUFFIX@)
>
> ...
>
> I went back to examine the commit messages involving MARK64 and its
> eventual demise.  Ralf's reasoning was that --libdir is the right way
> to do that.  Unfortunately, I was using --libdir=/usr/lib64, and it
> still didn't work.  "lib" is hard-coded into macros.in, so it will
> never be controllable via autoconf parameters until that changes.
>

Ah yes.

Not just Ralf. Mark wanted path relative macro configuration, Olivier  
wanted
additional Mandriva per-platform macro conventions, and I was trying  
to get rid of rpmrc
all at the same time, in early summer. Wotta mess. ;-)

Meanwhile the real flaw (in autoconf imho) is that there isn't a  
really strong design paradigm
for multilib, with obvious candidate macro names to use, when  
@libdir@ becomes multivalued.

Sure additional m4 macros are as easy to create as variables are; but  
there's not much that
is already conventionally defined.

But perhaps the easiest solution is to just make the cpu- 
os.macros.tar.gz tarball available
through http/ftp as well as cvs.

73 de Jeff