1. I made a suggestion to you earlier that it could
be that altarch thing, are you on an i686 machine?
2. It does that when the SPEC file calls an RPM macro
that you don't have. The choices are to upgrade rpm,
or just edit some spec files to macros you do have. I
have been changing %old_makeinstall and
%makeinstall_std to %makeinstall and that works fine.
Also, I had to change %configure2_5x to:
WANT_AUTOCONF_2_5=1 %configure
in the AbiWord spec.
--- Bryan Paxton <[EMAIL PROTECTED]> wrote:
> Two things specifically am I interested in:
> 1. Why is it that I still have problems building the
> glibc package?
> 2. Why is it on building some packages I get 'fg: no
> job control'
>
> The first one... glibc package does not build do to
> the following:
> %{_mandir}/man1/*
> %{_mandir}/man3/*
> %{_mandir}/man8/ld.so*
> %{_mandir}/man8/rpcinfo*
>
>
> Now, my best guess, since obviously the devel team
> has no problem with
> these macros, is that my ver of rpm(4.0.3) (and the
> macros files that
> come with it) are obsolete in the cooker-sense?
> I've stuck with 4.0.3 for compatibility reasons,
> specifically, ximian.
>
> On the second problem, 'fg: no job control', this
> would appear to be
> bash bitching about something, but what exactly?
> I encountered this problem with a few packages, then
> when building msec
> with my patches, I found that I got this error with
> macro for patch
> fubar (%Patch0 instead of %patch0). So is this
> simply due to a problem
> with the spec file, or possibly back to the problem
> with the glibc
> example (rpm ver and macros)?
>
>
> --
> Bryan Paxton
> Public PGP key: http://www.deadhorse.net/bpaxton.gpg
>
> "What laughter, why joy, when constantly aflame?
> Enveloped in darkness,
> don't you look for a lamp?"
> Dhp. 163
>
>
__________________________________________________
Do You Yahoo!?
Great stuff seeking new owners in Yahoo! Auctions!
http://auctions.yahoo.com
