Very strange. I forcefully reinstalled the "rpm" package and all is well. I
will
have to track down what happened and what is missing from the install.
-- John
Nathan Scott wrote:
> On Thu, Mar 21, 2002 at 05:41:48PM -0500, John Wingenbach wrote:
> > Hi Nathan,
> >
> > The problem I am seeing is the same thing I saw when building another rpm
> > myself. When I try to run:
> >
> > rpm -bANYTHING specfile
> >
> > I always get:
> > No such file or directory
>
> That sounds like your rpm installation is borken - I'm not sure
> exactly how it got in that state though. Just as a second
> workaround, you could set RPM=/bin/rpmbuild in the environment
> before the build and it will use that in preference (with no
> Makefile changes, etc).
>
> What does "strace rpm -bANYTHING specfile" list as the file that
> is not found?
>
> > >From searching the net, all I could find was a recommendation to use
> > >rpmbuild
> > instead of rpm. When I did that, it worked perfectly. The Makepkgs run
> > also
> > is trying to perform a "rpm" build. Simply fooling Makepkgs into using
> > rpmbuild instead of rpm built the rpms.
> >
> > The rpm versions I have installed are:
> > rpm-4.0.3-1.03
> > rpmbuild-4.0.3-1.03
> > rpm-python-4.0.3-1.03
> >
>
> The only difference between your Redhat machine and mine is that
> # rpm -q rpm rpmbuild rpm-python
> rpm-4.0.3-1.03
> package rpmbuild is not installed
> rpm-python-4.0.3-1.03
>
> Oh, wait I have:
> # rpm -q -f `which rpmbuild`
> rpm-build-4.0.3-1.03
>
> Was that a typo above in your list?
>
> Anyway, maybe you should try a fresh install of rpm - sounds like
> something is fishy on your machine (maybe try compare your machine
> to another with similar config to see whats different?)
>
> cheers.
>
> --
> Nathan
|