Hello,
Thank you so much for your reply. I downloaded the new source rpm and
building it went a lot more smoothly, well, up to the final part where it
actually creates the rpm. At this point, I got this error:
RPM build errors:
File not found: /tmp/swarm-root/usr/lib/swarm/libswarm.la
File not found by glob: /tmp/swarm-root/usr/lib/swarm/libswarm.so*
File not found: /tmp/swarm-root/usr/lib/swarm/libswarm.a
File not found by glob: /tmp/swarm-root/usr/lib/swarm/libjavaswarm*.la
File not found by glob: /tmp/swarm-root/usr/lib/swarm/libjavaswarm*.so*
File not found: /tmp/swarm-root/usr/lib/swarm/libjavaswarm.a
After much hunting arround, creating logfiles and such, I see that these
missing files are all caused by a failed invocation of libtool. Libtool
attempts to relink (?) them, and fails. Not knowing too much about
libtool, I eventually decided to just link the missing files myself, and
build the rpm with --short-circuit.
regards,
Izak Burger
On Fri, 16 May 2003, Paul E. Johnson wrote:
Yes, with gcc 3.2-2002-09-09, I can compile swarm with the -Werror flag.
Before or after gcc, not so. gcc 3.2 produces an internal compiler
error. With some other gcc-3.2, you can compile swarm, but not with the
-Werror flag. Marcus Daniels told me that there would be some kind of
capstone release of gcc soon that might address it.
In swarm-hackers, we have discussed this lately. We want not to patch
gcc anymore. We want Swarm to compile without special make flags. The
newest Swarm has been hacked so it no longer needs the specially patched
gcc to enable METHOD_FUNCTIONS.
I have just this minute moved RPMS/SRPM up to the RH 9 directory. Look
for swarm-2.1.143
The srpm is
swarm-2.1.143.20030512-1RH9.0.src.rpm
This was based on a current cvs snapshot. i notice that it has the
-Werror removed, probably by one of the Mac users.
Izak Burger wrote:
Hello,
Sorry to bother again, but it looks like I found what I'm looking for.
You posted this message:
http://www.swarm.org/pipermail/support/2002-October/012608.html
At the end of last year. It looks like the problem is with the gcc 3.2 on
the system. So the moral of the story is that I'll have to install a
better gcc first.
Luckily I managed to compile gcc 3.3 for my Debian woody system, so life
should be easier on the mdk side.
regards,
Izak Burger