In regard to: Re: linking a C program with a C++ library on Solaris, Ralf...:
Hello Bob, Tim,
* Bob Friesenhahn wrote on Tue, Feb 26, 2008 at 03:11:44AM CET:
On Mon, 25 Feb 2008, Tim Mooney wrote:
I don't see anything in 2.1b's info files or README or NEWS for updating
a project
Hi Eric,
* Eric Blake wrote on Tue, Feb 26, 2008 at 02:04:05PM CET:
> According to Ralf Wildenhues on 2/25/2008 11:58 PM:
> |> I believe that backward compatability has been mostly respected.
> |
> | Yes, but just running libtoolize has never been enough. Running aclocal
> | (with Libtool 2.2's m
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
According to Ralf Wildenhues on 2/25/2008 11:58 PM:
|> I believe that backward compatability has been mostly respected.
|
| Yes, but just running libtoolize has never been enough. Running aclocal
| (with Libtool 2.2's macro files visible to aclocal)
Hello Bob, Tim,
* Bob Friesenhahn wrote on Tue, Feb 26, 2008 at 03:11:44AM CET:
> On Mon, 25 Feb 2008, Tim Mooney wrote:
>>
>> I don't see anything in 2.1b's info files or README or NEWS for updating
>> a project from 1.5.x to 2.2. I assume that means that there's nothing
>> a project maintainer
On Mon, 25 Feb 2008, Tim Mooney wrote:
Thanks Bob, that's great news!
I don't see anything in 2.1b's info files or README or NEWS for updating
a project from 1.5.x to 2.2. I assume that means that there's nothing
a project maintainer needs to do other than to re-libtoolize his or her
project?
In regard to: Re: linking a C program with a C++ library on Solaris, Bob...:
On Mon, 25 Feb 2008, Tim Mooney wrote:
On Solaris, if you are linking against any C++ objects, you must use the
C++ compiler to link. I don't know if that's common to other platforms
or not, as I don
On Mon, 25 Feb 2008, Tim Mooney wrote:
On Solaris, if you are linking against any C++ objects, you must use the
C++ compiler to link. I don't know if that's common to other platforms
or not, as I don't have access to the plethora of UNIX platforms I used
to. In any case, the packages I've enco
