[pylucene-dev] Question about the MakeFile and static linking...

[Krys Wilken]

Hi Andi,

Thanks for replying.

That's what I figured.  I guess I could leave them out for an 
openSUSE-specific RPM, but if I want it to be a genera RPM I should keep them 
in.  Can't hurt, right? :)

One last question, then, and then I should soon have a 32-bit linux tarball 
and RPM available on my site:

Are the any i586 or i686 optimizations in the compiling?  Or is the resulting 
binary just i386?

I did not see explicit flags set in the Makefile, and I suspect that this is 
dependant on the system on which it is compiled, but I know very little of 
gcc or linux compiling, so I thought I'd ask.

Thanks again for all your help,
Krys

On Friday 15 June 2007 21:01, Andi Vajda wrote:
> On Fri, 15 Jun 2007, Krys Wilken wrote:
> > Hi list,
> >
> > I am wondering why, when staticly linking gcj (in the linux 32-bit, gcj
> > 3.4.x section), that the libstdc++.so.6 libgcc_s.so.1 are included in the
> > LIB_INSTALL variable.
>
> Because these can't be statically linked, no matter what.
> The static link only applies to libgcj.a.
> That's where the biggest space saving comes from.
>
> > I know this makes them get installed, but why are they needed?  I have
> > run the unit test with out those libraries being installed and they all
> > pass (except the timing one, which did not pass anyway).  Am I just lucky
> > that my distro's libs work, or are these files actually superfluous?
>
> Probably because your distro has those libs too in the system places.
>
> Andi..
> _______________________________________________
> pylucene-dev mailing list
> pylucene-dev at osafoundation.org
> http://lists.osafoundation.org/mailman/listinfo/pylucene-dev