FC3 build machine broken?

[Michael A. Peters]

On Mon, 2005-11-21 at 18:22 -0500, Dan Williams wrote:

> ...
> mkdir /.libs
>  g++ -DHAVE_CONFIG_H -I. -I. -I../include -I../include -DUSE_AUTOTOOLS -DUNIX -Dunix -D__unix__ -D_FTPLIB_NO_COMPAT -ftemplate-depth-25 -DCURLAVAILABLE -O2 -g -pipe -m32 -march=i386 -mtune=pentium4 -MT swconfig.lo -MD -MP -MF .deps/swconfig.Tpo -c ../src/mgr/swconfig.cpp  -fPIC -DPIC -o /.libs/swconfig.o
> ...
> 
> obviously, it shouldn't be sticking build objects in /.libs, and that's
> probably why the link section can't find it.

I'll report that to upstream.

>   Also not that it's a
> parallel build, since we're doing 'make -j2' at the top since the box is
> a multiprocessor box.  And those opteron boxes are _FAST_.  So try
> removing the %{?_smp_mflags} from the make and see what happens.

To avoid upgrade issues, would it be kosher to put a .1 after %{?dist}
in the release tag when I make that change (to ensure the fc4/fc5 are
seen as newer)?

I suppose I could just bump them all a release - but that seems like a
waste. I suppose I also could just wait until the next change, getting
rid of the static lib from the devel package isn't that big of a deal.