ISO: assistance for sparc solaris building of tclkit

[lvi...@gmail.com]

I started over at the starkit mailing list. But to date, no one who
has been able to figure out how to get this to work has had time to
contact me. So I thought I would ask here.

I've been trying for 6 months or more to build a tclkit on a
sparc solaris 8 machine. The build process fails, and I am
left stuck.

The problem is this. On my machine, gcc is not installed in a
standard location. So its library directory MUST be specified in
the link steps.

However, for at least one step of the process - the kitsh step -
that is not being done. Here's the error I see:

RUN: g++ -o kitsh pwb.o kitInit.o zlib.o rechan.o tclAppInit.o ../tcl/libtcl8.4.a ../vfs/libvfs1.3.a ../zlib/libz.a ../mk/Mk4tcl.a -L/ldatae/tclkit/install/lwv28awu/lib -ltcl8.4 -ldl -lsocket -lm -Wl,-Bstatic -lstdc++

/vol/gnu/gcc-3.3.4/bin/ld: cannot find -lgcc_s
collect2: ld returned 1 exit status

Now, my problem is that I've been unsuccessful in figuring out the
genkit process so that I can get the right -L and -R flags
passed along to this step.

Can someone provide me any tips on doing this?

Thank you.
--
<URL: http://wiki.tcl.tk/> MP3 ID tag repair < http://www.fixtunes.com/?C=17038 >
Even if explicitly stated to the contrary, nothing in this posting
should be construed as representing my employer's opinions.
<URL: mailto:lvi...@gmail.com > <URL: http://www.purl.org/NET/lvirden/ >

[Shaun Deacon]

Larry,

I have exactly the same problem and error message.... gcc
and g++ are under /usr/local/lib on my Solaris box.

I got round the problem by removing the '"-Wl,-Bstatic" flags
in the library switches - first on the command line (compiling
with g++ directly) and then in the genkit script.

In the genkit script, this is set in the Z array after the
platform check :

SunOS { array set Z { tclsuff "-Wl,-Bstatic -lstdc++" tksuff
"-Wl,-Bstatic -lstdc++" }

I changed this to :

SunOS { array set Z { tclsuff "-lstdc++" tksuff "-lstdc++" }

and kitsh compiles OK for me.

This is not a suitable permanent solution, but at least you
should be able to finish the tclkit build.

I hope this helps a little ?

cheers
Shaun

--
Shaun Deacon
SOCDEC, Fujitsu Microelectronics America
phone: ++1 408 737 5627 [coins: 7933 75627]
email: sde...@fma.fujitsu.com
--

[Larry W. Virden]

The problem with removing the attempt to make stdc++ static is that the
tclkit then gets built with that library dynamic. And the problem with
that, when
the compiler and libraries are installed in a non-standard location, is
that no one
can run the tclkit without modifying their environment - not a good
thing.