Re: My experience with rpm and lib64

Baho Utot <[email protected]>
Newsgroups gmane.linux.lfs.general
Message-ID <[email protected]>
On 04/13/2013 10:09 PM, Alice Wonder wrote:

[putolin]

> So now I'm busy writing spec files, test building them in Fedora 18
> (where I can use rpmlint to find issues - mostly documentation that
> isn't utf8, iconv usually fixes them - often it's a changelog or old man
> page)
>
> nspr and nss are first since one of them (nss I think) wasn't a clean
> install into lib64, then I'll go in the order of the book - hopefully
> figuring out how to get localedef to use /usr/lib/locale
>
> So - sorry for the length, but I don't have a blog ;) and I thought
> someone might be interested.
>

I have built LFS-7.3 and the current LFS-SVN for i686 using rpm. x86_64 
also worked for version 7.3.

To build rpm and build rpm into the tool chain you will need the 
following as dependencies:
zlib berkeley-db nspr nss popt readline elfutils rpm.

In  chapter 6 you will need: db elfutils nspr nss popt rpm as dependencies.

lua is not needed and I have droped it from my builds.

I have all the spec files for chapter 6 and it is available at 
github.com/baho-utot/LFS-RPM <https://github.com/baho-utot/LFS-RPM>.

I have a whole complete build system that builds rpm into chapter 5 
toolchain and then builds chapter 6 using the rpm installed from the 
tool chain.
To keep elfutils from trashing the toolchain you will need to configure 
it like the following:

./configure --prefix=/tools --program-prefix="eu-" --with-bzlib=no 
--disable-werror in the build in chapter5
and :
./configure  CFLAGS="%{optflags} -g" CXXFLAGS="%{optflags} -g " \
     --prefix=/usr \
     --bindir=/usr/bin \
     --libdir=/usr/lib \
     --disable-werror \
     --program-prefix="eu-" || {
     cat config.log
     exit 2
     }

In the spec file chapter 6

-- 
http://linuxfromscratch.org/mailman/listinfo/lfs-chat
FAQ: http://www.linuxfromscratch.org/faq/
Unsubscribe: See the above information page
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.