Hi Andreas,

But in general: Why do you want this? I consider it a bad idea...

yes, you are right, it is not ideal; I have some legacy code that has a hardcoded /usr/lib in it, that I do not want to change.

is this an rpmlint check (you might want to cite some more lines)?

+ /usr/lib/rpm/brp-lib64-linux sf@suse.de: if you find problems with this script, drop me a note /var/tmp/mypackage-1.0.9-build/usr/lib/libPOWERBOOK_MODEM.so: file format elf64-x86-64 /var/tmp/mypackage-1.0.9-build/usr/lib/libPOWERBOOK_MODEM.so: should be in */lib64 error: Bad exit status from /var/tmp/rpm-tmp.47721 (%install) RPM build errors: Bad exit status from /var/tmp/rpm-tmp.47721 (%install)

Those can be worked around - I hope it's documented somewhere.

Do you know how the rpmlint can be worked around or disabled during a build server build? many thanks Chris Am Dienstag, 23. September 2008 22:15 schrieb Andreas Jaeger:

Christopher Lang <christopher.lang@acurana.de> writes:

...

Hi,

in one of my packages that I am building for openSuse 10.2/x86_64 I have some custom .so files that I want to put explicitely in /usr/lib. I am installing them there, but the build server is complaining (and the build fails):

/var/tmp/some-file-build/usr/lib/libSome.so: file format elf64-x86-64 /var/tmp/some-file-build/usr/lib/libSome.so: should be in */lib64

Is there a way in the spec file %files section to handle that particular situation - or is there a way to make the build server accept certain .so files in /usr/lib even for x86_64 builds?

is this an rpmlint check (you might want to cite some more lines)? Those can be worked around - I hope it's documented somewhere.

But in general: Why do you want this? I consider it a bad idea...

Andreas -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org

ok, after thinking about it again it is probably really the best to fix it in the code. thanks for your responses! cheers Chris Am Freitag, 26. September 2008 17:44 schrieb Michal Marek:

Christopher Lang wrote:

...

Hi Andreas,

...

But in general: Why do you want this? I consider it a bad idea...

yes, you are right, it is not ideal; I have some legacy code that has a hardcoded /usr/lib in it, that I do not want to change.

There are (used to be?) plenty of packages out there with hardcoded .../lib paths, but usually it's not hard to fix these.

...

Do you know how the rpmlint can be worked around or disabled during a build server build?

Disable builds for Factory.

Michal

-- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org

yes, I figured that, after looking into the old code. Some other app loaded libs already go into /usr/lib/%{name}. And the build server & rpmlint do not complain. thanks again Chris Am Freitag, 26. September 2008 18:23 schrieb Cristian Rodríguez:

Christopher Lang escribió:

...

ok, after thinking about it again it is probably really the best to fix it in the code.

if this are modules loaded by your application , you must place them in /usr/lib/%{name} -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org