hardcode files in %files stanza

pbdlists at pinboard.com pbdlists at pinboard.com
Thu Nov 12 19:45:46 UTC 2009


Of course, the build stage must actually install the file to %buildroot.
Never install things directly to /usr/bin or so during RPM builds,
always to %{buildroot}/usr/bin or whatever. With most software packages which
offer "./configure; make; make install" this can be done by running
"DESTDIR=%{buildroot} make install" for example. The %makeinstall should
do this automatically.

What I don't quite understand is why you would get at "fg: no job
error". What job would be backgrounded during the build stage?

By the way, you should never be worried that you hosed your rpmbuild-box
because that box should _ALWAYS_ be pristine! Try to build you rpm
packages on a freshly installed (maybe virtual) box. Or you might want
to have a lock at mock: http://fedoraproject.org/wiki/Projects/Mock

There is one law and one very strong suggestion when building RPMs:
law:            never ever build an RPM as root - NEVER!
suggestion:     try to build the RPM on a freshly installed minimal box
                (eg. only @Base + rpmbuild +requirements for this
                 package installed)



On Tue, Nov 10, 2009 at 01:21:53PM -0600, Barry R Cisna wrote:

> or something.I am wondering if I have something hosed on my dev box FC10 I
> am trying to build this on? Last things I have rpm built was on Centos5. I
> could things to rpmbuild fine on that OS? I'll keep scratching.

On Tue, Nov 10, 2009 at 01:55:00PM -0600, Barry R Cisna wrote:
> Kurt,
> I changed the syntax from %{BUILDROOT} to > $RPM_BUILD_ROOT ..this got rid
> of the 'gf: no job error',,but now I still get file could not be found at
> BUILDROOT/<packagename>/usr/bin/file  .Bad exit when building.

More information about the Rpm-list mailing list