[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: libtool, Solaris, Sun Studio compiler

From: Ralf Wildenhues
Subject: Re: libtool, Solaris, Sun Studio compiler
Date: Thu, 17 Mar 2005 13:53:41 +0100
User-agent: Mutt/1.4.1i

Hi there,

* Пухальский Юрий Андреевич wrote on Thu, Mar 17, 2005 at 01:49:44PM CET:
> Good day!

Please keep the mailing list in Cc: so others can
read/learn/comment/help as well.  Thank you.

> I don't know how does the quoting work in this Outlook express:( So
> will try not to quote at all.

There are instructions on the web how to achieve this.
I don't know myself, have never used it.  But if you
accept a word of advice -- use a different mailer, one
with less bugs and security problems.

> I've checked the 5.3 compiler from Forte 6.2, it shows the same
> behaviour.


> As of patch, what do I do with it? I have sources of libtool here,
> does it suffice? Or should I get the cvs version?

1.5.14 should suffice.  You will, however, need recent versions of
Autoconf and Automake installed.

Save the patch in a file, say patch-sun.  Execute
$ cd $top_srcdir
$ patch -p0 < $path_to/patch-sun
$ ./bootstrap
$ ./configure  --prefix=/usr/local      # or some other prefix
$ make
[ possibly also: make install ]
$ make check 
# Now, for failed test groups:

$ make check VERBOSE=x TESTS='foo1.test ...'

Replace $top_srcdir with the toplevel Libtool source directory and
$path_to and /usr/local with values that are sensible at your place.

This is documented in README.

> Do I understand it right, that we use linker options only to pass -z
> flags? Else we probably couldn't set wl=-z...

I have no idea whether setting wl=-z generally is a good idea or not.
The available online docs suggest so, but there may be problems with
older versions of the compiler, and I don't want to break that without a
good reason to do so (or someone convincing me it is ok to do so).


reply via email to

[Prev in Thread] Current Thread [Next in Thread]