❦ 16 septembre 2013 12:47 CEST, YunQiang Su <wzss...@gmail.com> :
>>>> Does the bug really happens for real? Doesn't system paths used before >>>> user-specified paths? >>> You can tag it as won't-fix if you'd like to. >>> If without multilib packages installed or install some libraries >>> installed manually, >>> this package can be built successfully. >> >> Does the problem happens if the user only install stuff with apt-get? > yes, it will. if user install libc6-dev-mips32, there will be some thing like > libc.so, libm.so etc in /usr/lib. > > x86 series (i386, amd64, x32) don't do it like this, they put i386 > stuff to lib32 > and x32 stuff to libx32, amd64 stuff to lib64. > Unfortunately, mips series don't do it like x86 series. Shouldn't the linker favor /usr/lib64 over /usr/lib in this case? I thought that it would be possible but since there is no `-lsystem` option (like `-isystem`), this may be because the default path is not special. -- /* Am I fucking pedantic or what? */ 2.2.16 /usr/src/linux/drivers/scsi/qlogicpti.h
signature.asc
Description: PGP signature