On 12/08/2009 08:03 AM, doiggl@velocitynet.com.au wrote:
How can this error be fixed(see following message) ?, do I alter makefile ? so I can compile gimp-lch-selector. If I need a new makefile what should it look like ?
Thanks Glenn
Error message as follows: + make g++ \ -ansi -pedantic -Wall -Wextra \ -shared -fPIC -O3 \ -o libcolor-selector-lch.so main.cpp \ $(gimptool-2.0 --cflags --libs) + exit 0 Executing(%install): /bin/sh -e /var/tmp/rpm-tmp.ru3Am0 + umask 022 + cd /usr/src/packages/BUILD + cd gimp-lch-selector-0.3 + make DESTDIR=/usr/src/packages/BUILDROOT/gimp-lch-selector-0.3-17.1.x86_64 install install libcolor-selector-lch.so $(gimptool-2.0 --gimpplugindir)/modules/ install: cannot create regular file `/usr/lib64/gimp/2.0/modules/libcolor-selector-lch.so': Permission denied make: *** [install] Error 1 error: Bad exit status from /var/tmp/rpm-tmp.ru3Am0 (%install)
RPM build errors: Bad exit status from /var/tmp/rpm-tmp.ru3Am0 (%install) mount: / is busy
spec file -
project -
https://build.opensuse.org/package/show?package=gimp-lch-selector&project=home%3Adoiggl
Last log -
The way that I fix similar errors is to transfer the sources, patches, etc. to my systems /usr/src/packages/SOURCES directory and the spec file to /usr/src/packages/SPECS and use "rpmbuild -bc <mypackage>.spec", which builds to the end of the compile stage and use midnight commander to search for the files in the BUILD/mypackage-%version directory where the sources are built, then use "rpmbuild -bi --short-circuit <mypackage>.spec" which completes the %install and %files stage and all of the files to be packaged are present in BUILD-ROOT/mypackage-%version so I can search to see if the file exists and where the packages make install has written it.then use cp, install, rm and move etc., in the %install section to place the files in the correct places in the package. Of course, if you can't find the file in the BUILD directory then you have a make problem with the package which you have to trouble shoot in the %configure section. Look at other spec files to see how other people install files into the correct place. "rpmbuild -bi --short-circuit <mypackage>.spec" completes quickly so you can hack the spec file and rerun it to see if you got it right. An easier method of putting the bits of the package in the right place is to install a source rpm from upstream, if available and then apply suse package conventions to it. Installing the src.rpm also satisfies the BuildRequires: of the package automatically. I see you haven't got the build requirements of the package right yet, from your previous email it needs cairo-devel and one more devel package at least, that's most probably something to do with the problem. Regards Dave P -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-packaging+help@opensuse.org