[opensuse] 32bit packages for x86_64
Hello, how does Novell/SUSE create packages like libpng-32bit? `rpm -qi` says "Source RPM: libpng-1.2.8-19.5.src.rpm", but its specfile does not mention "32bit" anywhere. Where is the magic located? -`J' -- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Thu, Dec 21, 2006 at 09:27:31PM +0100, Jan Engelhardt wrote:
Hello,
how does Novell/SUSE create packages like libpng-32bit? `rpm -qi` says "Source RPM: libpng-1.2.8-19.5.src.rpm", but its specfile does not mention "32bit" anywhere. Where is the magic located?
In our buildsystem, and is called baselibs. Originally we used a baselibs RPM built in the 32bit environment which creates the -32bit sub RPMs. Now (since 10.1/SLES10) our RPM build process does this during the build of the regular 32bit RPM. It is controlled by a baselibs configuration file on what RPMs are handled this way and what is packed. Ciao, Marcus -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Dec 21 2006 21:36, Marcus Meissner wrote:
On Thu, Dec 21, 2006 at 09:27:31PM +0100, Jan Engelhardt wrote:
how does Novell/SUSE create packages like libpng-32bit? `rpm -qi` says "Source RPM: libpng-1.2.8-19.5.src.rpm", but its specfile does not mention "32bit" anywhere. Where is the magic located?
In our buildsystem, and is called baselibs. Originally we used a baselibs RPM built in the 32bit environment which creates the -32bit sub RPMs.
Now (since 10.1/SLES10) our RPM build process does this during the build of the regular 32bit RPM. It is controlled by a baselibs configuration file on what RPMs are handled this way and what is packed.
So long story short: what is required to rebuild an arbitrary package so that it is marked with '32bit' in its name and only includes <files I want>? My build system account has not been activated yet so I can't have a look if there was something hint-ful there. -`J' -- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Thu, Dec 21, 2006 at 09:41:16PM +0100, Jan Engelhardt wrote:
On Dec 21 2006 21:36, Marcus Meissner wrote:
On Thu, Dec 21, 2006 at 09:27:31PM +0100, Jan Engelhardt wrote:
how does Novell/SUSE create packages like libpng-32bit? `rpm -qi` says "Source RPM: libpng-1.2.8-19.5.src.rpm", but its specfile does not mention "32bit" anywhere. Where is the magic located?
In our buildsystem, and is called baselibs. Originally we used a baselibs RPM built in the 32bit environment which creates the -32bit sub RPMs.
Now (since 10.1/SLES10) our RPM build process does this during the build of the regular 32bit RPM. It is controlled by a baselibs configuration file on what RPMs are handled this way and what is packed.
So long story short: what is required to rebuild an arbitrary package so that it is marked with '32bit' in its name and only includes <files I want>? My build system account has not been activated yet so I can't have a look if there was something hint-ful there.
Install the build RPM. export BUILD_DIST=i386 linux32 build --baselibs foo.spec Ciao, Marcus -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Am Donnerstag, 21. Dezember 2006 21:27 schrieb Jan Engelhardt:
Hello,
how does Novell/SUSE create packages like libpng-32bit? `rpm -qi` says "Source RPM: libpng-1.2.8-19.5.src.rpm", but its specfile does not mention "32bit" anywhere. Where is the magic located?
detlef@detlef-pc:~> build --help | grep 32bit Create -32bit/-64bit/-x86 rpms for other architectures detlef -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
participants (3)
-
Detlef Reichelt
-
Jan Engelhardt
-
Marcus Meissner