[Swarm-Support] Re: Swarm again

[Izak Burger]

Hello,

Thanks for the advice.  What I actually did was to edit the .la files for
the two libraries, and change the relink commands, adding /.libs to the
end of all the relevant -L's, which is what should have happened anyway if
I'm not mistaken.  Then I had to manually recreate the .so file that was
destroyed during the failed invocation of libtool, after which I ran the
libtool --mode=install command again.  After installing the rpm, ldd shows
that everything resolves properly.

At least we have rpm --short-circuit, or I would have had to sit through
the whole compile again :-)

I will keep this in mind for next time.  I still have to transform your
.spec file to a debian/rules file at some point, and since Debian woody
has a less recent version of libtool than Mandrake 9.1, I foresee similar
problems.

My users only really want the jdk part, so as long as that works I'm a
happy camper.

regards,
Izak

On Wed, 21 May 2003, Paul Johnson wrote:

> Hello, Izak
>
> You have happened upon the libtool scourge.  I see the same in RedHat
> when certain versions of libtool exist.
>
> Here's the problem. libtool is looking in /usr/lib/swarm but instead the
> files are in /tmp/swarm-root/usr/lib/swarm.  At one time, I had changed
> the ltmain.sh in Swarm to avoid this, but that changed did not work with
> one version of libtool or another, so it got ditched.
>
> So here is the fix.
>
> After the RPM build runs one time, note in your build directory BUILD
> you have swarm, cd in there, and cd into the directory called
> "=with-hdf".  su to the root user, then run "make install".  This
> actually installs the stuff to /usr.
>
> Then run the RPM build again, and it will find the libraries it needs.
>
> You can then manually delete the swarm install, from /usr/include/swarm,
> usr/lib/swarm, etc.
>
> Then when you install the Swarm RPM,
>
> Izak Burger wrote:
> > 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
> >>>
> >>>
> >>
> >>
> >>
> >
>
>
>

-- 
Never look up when dragons fly overhead.

------------------------------------------------------------------------
Izak Burger                                  Email: address@hidden
Homepage: http://www.cs.sun.ac.za/~iburger/  Tel: +27 21 808 4863

Please avoid sending me Word attachments.
See http://www.cs.sun.ac.za/~iburger/noword.html