On Mar 23, 2012, at 8:12 PM, Jeffrey Johnson wrote:

> 
> On Mar 23, 2012, at 7:41 PM, Henri Gomez wrote:
> 
>> Hi to all,
>> 
>> I'm a long time rpm user and packager and I'd like to experiment it on
>> OSX (10.7.3) and Xcode 4.3.2.
>> 
> 
> Good.
> 
> <snip>
> 
>> 
>> Did someone succeed to build rpm 5.x on OSX Lion ?
>> Advices more than welcomed.
>> 
> 
> I build the latest rpm-5_4 from CVS on Lion Server using a buildbot here:
>       http://harwich.jbj.org:8010/waterfall
> 
> Both Lion Server (and Leopard) are there in the waterfalls.
> 
> (aside)
> Both are broken atm just because I haven't bothered fixing "bleeding edge" 
> functionality
> on Mac OS X quite yet.
> 

Snipping out embedded perl on Lion mostly resurrected the Lion build
of rpm-5_4. The rpm-5_3 branch builds are dramatically different …


… your build failures are:

   1) not having Berkeley DB installed correctly: RPM releases target
    a single version of Berkeley DB, currently db-5.3.15. On Mac OS X
    there's one extra hack I do:
        cd /opt/local/lib
        ln -s db53/* .
    because of too little RPM interest on Mac OS X to justify a proper fix
    chasing down what is ultimately just a path problem divergence.
    If you examine config.h, you will find that Berkeley DB wasn't detected.

    2) RPM and POPT are quite intimately connected (I maintain both)
    and RPM now (again) is distributed with a version of POPT that
    "works" with RPM. Install popt-1.16 like this
        cd popt
        ./configure --prefix=/opt/local
        make
        make install
    and RPM will find. There were also a couple of Mac peculiarities
    repaired in POPT in the last 2 months.

    3) BeeCrypt is MANDATORY: many of the common digest algorithms
    are from BeeCrypt. BeeCrypt is also distributed with RPM because
    its mostly an orphan project these days: which is sad because BeeCrypt
    is pretty code and is still faster than other choices like 
openssl/nss/gcrypt.

At least mostly: something else needs to be fixed with RPM+PERL on
Lion. *yawn* todo++.

But you should be able to read the logs and figure how to build from
CVS (which is likely easier to fix than builds from tar balls: the rpm-5_4
branch is being released more often than monthly while development is active.

And active development will likely continue through (at least) July.

Resurrecting the Leopard rpm-5_4 build is equally easy if there is interest.

I use the G5 build as a "sanity check" on endianness issues on ppc64 …
there's some issues setting WORDS_BIG_ENDIAN that need to be fixed
for the NIST SHA3 hashes which I will get to as the winner is announced.

hth

73 de Jeff

______________________________________________________________________
RPM Package Manager                                    http://rpm5.org
User Communication List                             rpm-users@rpm5.org

Reply via email to