Mailinglist Archive: opensuse-buildservice (351 mails)

< Previous Next >
Re: [opensuse-buildservice] Building xxx-32bit and xxx-devel-32bit
  • From: Uwe Bonnes <bon@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx>
  • Date: Wed, 16 Jul 2008 10:26:28 +0200
  • Message-id: <18557.45236.544914.479424@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx>
"Ludwig" == Ludwig Nussel <ludwig.nussel@xxxxxxx> writes:

Ludwig> Uwe Bonnes wrote:
>> >>>>> "Michal" == Michal Marek <mmarek@xxxxxxx> writes:
>>
Michal> Uwe Bonnes wrote:
>> >> However cleaner would be a possibility to build xxx-32bit and >>
>> xxx-devel-32bit from the source rpms. A receipe how to do that would
>> >> be very welcome.
>>
Michal> See
Michal>
http://en.opensuse.org/Build_Service/Tips_and_Tricks#Building_xxbit_packages_for_other_architectures
>>
Michal> Michal
>> Thanks,
>>
>> there are already libusb and libftdi packages in the buildservice
>> repositories. Should I get a new package builder and trigger building
>> new packages or should I try to get in contact with the people who
>> build libusb and libftdi to expand them?

Ludwig> There should be a libusb-32bit already. If you have a special
Ludwig> one you may try $ echo libusb > baselibs.conf $
Ludwig> /usr/lib/build/mkbaselibs -c /usr/lib/build/baselibs_global.conf
Ludwig> -c baselibs.conf libusb-2342.i586.rpm libusb(ia64:x86): writing
Ludwig> specfile... libusb(ia64:x86): running build...
Ludwig> libusb(x86_64:32bit): writing specfile... libusb(x86_64:32bit):
Ludwig> running build... $ l /usr/src/packages/RPMS/* ...

You are right in the existance of libusb-32bit. But libusb-devel-32bit is
missing, so compiling a 32 bit programm using libusb doesn't work.

--
Uwe Bonnes bon@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx

Institut fuer Kernphysik Schlossgartenstrasse 9 64289 Darmstadt
--------- Tel. 06151 162516 -------- Fax. 06151 164321 ----------
---------------------------------------------------------------------
To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@xxxxxxxxxxxx
For additional commands, e-mail: opensuse-buildservice+help@xxxxxxxxxxxx

< Previous Next >
Follow Ups