Were does it sets the _libdir to /usr/lib ? In the spec file (%ifarch) or in 
rpmbuild? 

if it's in rpmbuild, this is a behaviour change between fc17 and fc18..... 
I'll need to change the package then.... It may be a problem in some package in 
the future. 

If it's in the spec file, it should be easy to fix. forcing the variable using 
--define '%_libdir %{_prefix}/lib64' is IMHO unsure as some system variables 
are overridden. 

The problem is that in the past, rpmbuild was basic and was unable to build a 
multiarch rpm. If the main package was a arch package, then a subpackage (even 
if BuildArch:noarch was specified) was build as a %arch.rpm. 
Thus, the trick was to protect subpackage with %ifarch noarch and build using 
rpmbuild --target x86_64,noarch xxx.spec for example. (2 build triggered). 

torque (if I'm correct) is such a package for example. If you build it using 
rpmbuild -bb torque.rpm, 2 noarch packages are not build (doc, ...). 

Now, if a rpm wants sub packages of different types it's possible. just add the 
correct BuildArch: tag in the sub package and if it's a noarch it'll wuild as 
such. 

The problem of this change of behaviour may have been introduced to resolve the 
BuildArch: ix86 where the %_libdir must be correctly set. It also assumes that 
noarch libdir is in /usr/lib which is somehow correct. 

unfortunately, in some situation (mainly old packages), this produces 
inconcistency betwen arch and noarch subpackages. and we've just hit one of 
them. 

I'll search for a clean solution tomorrow. 

Regards, 

Olivier. 

----- Mail original -----

> De: "DongInn Kim" <di...@cs.indiana.edu>
> À: oscar-devel@lists.sourceforge.net
> Envoyé: Jeudi 11 Avril 2013 17:51:02
> Objet: Re: [Oscar-devel] RE : [PROVENANCE INTERNET] RE : RE : RE :
> systemimager should build.

> Olivier,

> I think I found something.

> The option "--target noarch" sets up the _libdir to "/usr/lib" even
> though my actual _libdir is supposed to be "/usr/lib64".

> So, if we don't specify "--taget noarch", it will build properly. The
> noarch is specified in the spec file.

> Is there a way to specify libdir on rpmbuld?

> Regards,

> --
> - DongInn

> On Apr 11, 2013, at 10:49 AM, olivier.laha...@free.fr wrote:

> > DongInn,
> 

> > Last test:
> 

> > rpmbuild --rebuild
> > /var/lib/oscar-packager/downloads/systemimager-4.3.0-0.10.src.rpm
> > --target noarch
> 

> > If it works, then I have no idea of why it faisl in oscar-packager
> > a:
> 
> > socar-packager --force --verbose --debug --all systemimager
> > unstable
> 
> > May help me...
> 

> > If it fails, then this means that --target noarch affects the
> > %_libdir on fc-18 but not on fc-17.....
> 
> > Which could be a problem....(if the behaviour of rpmbuild --target
> > noarch and rpmbuild with a spec file that have the BuildArch: set
> > to
> > noarch are different).....
> 

> > Regards,
> 

> > Olivier.
> 

> ------------------------------------------------------------------------------
> Precog is a next-generation analytics platform capable of advanced
> analytics on semi-structured data. The platform includes APIs for
> building
> apps and a phenomenal toolset for data science. Developers can use
> our toolset for easy data analysis & visualization. Get a free
> account!
> http://www2.precog.com/precogplatform/slashdotnewsletter
> _______________________________________________
> Oscar-devel mailing list
> Oscar-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/oscar-devel
------------------------------------------------------------------------------
Precog is a next-generation analytics platform capable of advanced
analytics on semi-structured data. The platform includes APIs for building
apps and a phenomenal toolset for data science. Developers can use
our toolset for easy data analysis & visualization. Get a free account!
http://www2.precog.com/precogplatform/slashdotnewsletter
_______________________________________________
Oscar-devel mailing list
Oscar-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/oscar-devel

Reply via email to