|Subject:||RE: Problems with cvs-libtool and Solaris CC|
|Date:||Wed, 8 Jan 2003 18:35:41 -0500|
I've looked at this in depth, and the problem does not appear for me.
The main difference I see in my "libtool" script generated using Solaris CC
is that AR="ar" for every tag. As it should be, old_archive_cmds uses 'CC -xar'
in the CXX tag, but it doesn't change AR. I don't think this problem
is still in CVS libtool, but mine isn't 100% current.
From: Bob Friesenhahn [mailto:address@hidden]
Sent: Wednesday, January 08, 2003 10:28 AM
Subject: Re: Problems with cvs-libtool and Solaris CC
On Wed, 8 Jan 2003, Albert Chin wrote:
> > CC: Outfile required when -xar flag is used
> > As you see, CC is called with -xar, which I believe is correct, but I
> > don't know what the `x' is supposed to do. As you saw in the previous
> > mail, I found the following bit of code in the generated libtool:
> > | > # The archiver.
> > | > AR="/opt/SUNWspro/bin/CC -xar"
> > | > AR_FLAGS="-o"
> > Which seems to be correct, but further down.
> Sun C++ requires /opt/SUNWspro/bin/CC -xar to *create* archives.
> However, it appears we cannot use this to *extract* archives. Bummer.
> So, do we need a separate AR_x variable to control the path to an AR
> used to extract archives?
> If you look at a Sun C++ .a archive file, you'll find the .o files
> archived and other .o files (objects of template functions I guess).
> Any idea how to properly extract a Sun C++ archive? /usr/bin/ar
> wouldn't pull out the extra .o files.
Yikes! I assume that this problem results from using C++-based
The purpose of 'CC -xar' is to support a template repository. Given
this, it is likely that the archive file doesn't contain everything
since the template instantiations will be stored in the template
repository subdirectory. It may be impossible to accomplish the
equivalent of 'ar -x'.
Libtool mailing list
|[Prev in Thread]||Current Thread||[Next in Thread]|