Mailinglist Archive: opensuse-packaging (214 mails)

< Previous Next >
Re: [opensuse-packaging] Help needed to get baselibs.conf right
  • From: Michael Matz <matz@xxxxxxx>
  • Date: Tue, 12 Oct 2010 11:26:41 +0200 (CEST)
  • Message-id: <Pine.LNX.4.64.1010121115450.10994@xxxxxxxxxxxxx>
Hi,

On Tue, 12 Oct 2010, Vincent Untz wrote:

Hi,

I've struggled with two baselibs.conf issues yesterday, and I'd need
help to solve them.

First, one question: my understanding is that we can't assume that the
packages that will be created will be for 32-bit only, they could well
be 64-bit too. Is that right? (We only do 32-bit ones in openSUSE,
afaik, though)

Huh? x86-64 is 64bit and last I checked openSUSE supports that :)

My two issues can be seen with this example from gtk2 (submitted to G:F):

post "%if %_lib == lib64"
post "%{_bindir}/gtk-query-immodules-2.0-64 >
%{_sysconfdir}/gtk-2.0/gtk64.immodules"
post "%else"
post "%{_bindir}/gtk-query-immodules-2.0 >
%{_sysconfdir}/gtk-2.0/gtk.immodules"
post "%endif"

Is the '>' supposed to be '->' ? In any case I didn't even know that
'post ""' exists. You might want to look at gcc45 and glibc
baselibs.conf. In particular, for testing the target-system you can use

targettype <type> <some baselibs directive>
or
(target)?arch <arch> <some baselibs directive>

Where <arch> can be the usual archs, <type> can be 'x86' (that's the
repackaged i?86 libs for ia64 (!)), 'ia32' (that matches all i?86) and
some others. Note also the special variables like <prefix>.

Paths for x86 packages
======================

The files in x86 packages are all put in a /emul/ia32-linux prefix.
So I get /emul/ia32-linux/usr/bin/gtk-query-immodules-2.0 and
/emul/ia32-linux/etc/gtk-2.0/gtk.immodules.

However, the post scriplet above will expand to:
/usr/bin/gtk-query-immodules-2.0 > /etc/gtk-2.0/gtk.immodules

I think you want to prepend <prefix> to both.


Ciao,
Michael.
--
To unsubscribe, e-mail: opensuse-packaging+unsubscribe@xxxxxxxxxxxx
For additional commands, e-mail: opensuse-packaging+help@xxxxxxxxxxxx

< Previous Next >
Follow Ups
References