Timo Sirainen wrote:
On Tue, 2010-08-31 at 19:57 +0200, Stephan Schulz wrote:
What is speaking agains adding the -lgcc_s if configure finds itself on Solaris?
Because it seems like unnecessary workaround. I haven't heard anyone else complain about this than you in the recent years (other than I guess the one other person whose mail you linked to). I'd at least want to understand why this isn't a problem for all Solaris users. Can you compile *anything* without -lgcc_s?
I have compiled many many things on Solaris (9 and 10 on SPARC), including Dovecot. I've never had this particular issue. Part of the deal is that I have an environment file that I always source before doing any build work. It sets up all the paths that I need and makes sure the tools and libraries are going to be found. It defines CC, CFLAGS, CPPFLAGS, LDFLAGS and so on. It removes any inconsistencies from the system behavior when I am building software. When I forget to do that, configure will give me odd ball results. Then I just start over and do it right.
Make sure the path to the lib that contains libgcc_s.so, etc., is in your LD_LIBRARY_PATH, CFLAGS and LDFLAGS before running configure. Alternatively, you can use crle (man crle) to set up your load environment. But, I prefer to just build the software correctly in the first place.
On one of my older Solaris 9 systems, using a Sunfreeware version of gcc (and all the gnu tools), I have:
PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/usr/ucb:/usr/ccs/bin export PATH LD_LIBRARY_PATH=/usr/local/lib:/usr/lib:/usr/sfw/lib export LD_LIBRARY_PATH CPPFLAGS="-I/usr/local/include" export CPPFLAGS CFLAGS="-L/usr/local/lib -R/usr/local/lib" export CFLAGS LDFLAGS="-L/usr/local/lib -R/usr/local/lib" export LDFLAGS CC=gcc export CC
On my newer Solaris 10 systems it is more complicated, because I'm using gccfss.
--
Chris Hoogendyk
- O__ ---- Systems Administrator c/ /'_ --- Biology & Geology Departments (*) \(*) -- 140 Morrill Science Center
<hoogendyk@bio.umass.edu>
---------------
Erdös 4