[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: <foo> link with -L/usr/lib

Let's discuss this on debian-devel. Here is what I answered to bug
723358 about hwloc.

Samuel Thibault, le Tue 17 Sep 2013 13:01:32 +0200, a écrit :
> YunQiang Su, le Tue 17 Sep 2013 18:38:26 +0800, a écrit :
> > This package has one or more -L/usr/lib in its build system,
> Err, no, it doesn't.  Please recheck your build log carefully.  And
> don't do Mass Bug Filling without extra care, which includes discussing
> about it on debian-devel first!
> > which will make it ftbfs if there is libraries under /usr/lib,
> > while is not the default architecture, mips* for example.
> > 
> > On mips* systems, /usr/lib is defined as place to hold O32
> > libraries, and /usr/lib32 for N32, and /usr/lib64 is for N64.
> That's not necessarily a problem: a spurious -L/usr/lib does not hurt,
> the linker will simply not take the binaries.  It's only if -L/usr/lib
> is required for proper linking that it would be a problem.  But the
> compiler already has that in its search path, so there is really no
> problem.
> > Beside the way, on the multiarch system like Debian, user may install
> > libraries under /usr/lib by hand.
> No, they are not supposed to be doing that.
> > The attachement is the buildlog of this package on mips64el platform.
> The build didn't even start...


Reply to: