Hi Peter,
* Peter Ekberg wrote on Fri, Jul 29, 2005 at 11:41:22AM CEST:
>
> I have looked at the reason why the mdemo2-make.test fails
> on MinGW.
Very nice!
> The reason is that the mlib_func symbol is not properly
> exported from libmlib (i.e. not present in the import lib).
>
> I see two so
On Wed, 2005-08-03 at 13:46 -0500, Bob Friesenhahn wrote:
> On Wed, 3 Aug 2005, Ralf Corsepius wrote:
>
> > On Wed, 2005-08-03 at 13:57 +0200, Graham Leggett wrote:
> >> Hi all,
> >
> >> What method needs to be used to tell libtool to link to stdc++ that
> >> belongs to the compiler being run?
> >
Ralf Wildenhues wrote:
> * Peter Ekberg wrote on Thu, Jul 28, 2005 at 03:18:18PM CEST:
> >
> > I came across a surprise in the commit script though. When
> > commiting on branch-2-0, the script checked for conflicts
> > against head, which forced me to --force one commit.
> >
> > Is this caused b
Hi Peter,
* Peter Ekberg wrote on Thu, Jul 28, 2005 at 03:18:18PM CEST:
>
> I came across a surprise in the commit script though. When
> commiting on branch-2-0, the script checked for conflicts
> against head, which forced me to --force one commit.
>
> Is this caused by an error in my routine?
Christoph Bartoschek said:
> I also have big problems that libtool tries to use /usr/lib/libstdc++
> instead of the compiler one, when I compile several projects.
>
> IMO libtool should always ignore libstdc++, but this is another issue.
>
> I solve the problem by patching libtool after configu
On Wed, 3 Aug 2005, Ralf Corsepius wrote:
On Wed, 2005-08-03 at 13:57 +0200, Graham Leggett wrote:
Hi all,
What method needs to be used to tell libtool to link to stdc++ that
belongs to the compiler being run?
No method at all. libstdc++ is an internal library of g++ you are not
supposed to
On Wed, Aug 03, 2005 at 07:30:39PM +0200, Graham Leggett wrote:
>
> The link line generated by libtool is:
>
> /bin/bash ../../libtool --tag=CC --mode=link gcc -I.. -I../..
> -I/usr/local/include/libxml2 -L/usr/local/lib -R/usr/local/lib -lxml2 -lz
> -lpthread -liconv -lm -lsocket -lnsl -o libm
Christoph Bartoschek said:
> I also have big problems that libtool tries to use /usr/lib/libstdc++
> instead of the compiler one, when I compile several projects.
>
> IMO libtool should always ignore libstdc++, but this is another issue.
>
> I solve the problem by patching libtool after configur
Christoph Bartoschek said:
> I also have big problems that libtool tries to use /usr/lib/libstdc++
> instead of the compiler one, when I compile several projects.
>
> IMO libtool should always ignore libstdc++, but this is another issue.
>
> I solve the problem by patching libtool after configur
Am Mittwoch, 3. August 2005 19:11 schrieb Graham Leggett:
> Kurt Roeckx said:
> > Are you sure your libtool has been regenerated for the new g++?
>
> I rebuilt libtool v1.5.8 which was previously installed, and when this
> made no difference I downloaded and built libtool v1.5.18.
>
> I deleted con
Hi all,
While attempting to build two C++ library projects A and B, on a Solaris
v2.8 environment with gcc v4.0.1 (in a private directory) and gcc v3.4.2
(in /usr/local) both installed in the path, and with gcc v4.0.1 taking
precedance, libtool pulls in either the v3.4.2 stdc++, or the v4.0.1
stdc
Peter O'Gorman said:
> It could be coming from an already installed .la file.
I did a complete machine grep. The only references to libstdc++ within an
.la file on this machine are in libstdc++.la itself, or in the .la files
of the two projects.
libstdc++ is not found in any other .la file on th
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Graham Leggett wrote:
| I am completely baffled - can anyone reveal what method libtool uses to
| detect libraries? What steps are followed to create the dependency_libs
| variable within the .la file? I am trying to find out where the referencce
| t
Kurt Roeckx said:
> Are you sure your libtool has been regenerated for the new g++?
I rebuilt libtool v1.5.8 which was previously installed, and when this
made no difference I downloaded and built libtool v1.5.18.
I deleted config.guess, config.sub, libtool and ltmain.sh and recreated
them from
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Peter O'Gorman wrote:
| Ralf Wildenhues wrote:
| |
| | Regards, and sorry for the inconvenience,
|
| I have posted recently and had my mail queued for moderator approval.
| Not happy.
Okay, this one came through, improving my mood :)
Peter
-BE
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Ralf Wildenhues wrote:
| Just a short heads-up for people who have posted recently:
|
| In an attempt to improve upon the spam situation, I've probably messed
| up mailman filtering rules to the extent that currently, everyone is
| moderated. Please
On Wed, Aug 03, 2005 at 01:57:20PM +0200, Graham Leggett wrote:
> Hi all,
>
> I have been having a very strange problem that I have tracked down to
> libtool, and I don't know how to proceed.
>
> I have a Solaris v2.8 machine with a system installed copy of gcc v3.4.2
> in /usr/local. Recently a
Would it be possible to configure mailman so that only messages from
addresses which are not registered get moderated? Might be less work
for the moderator(s) and only senders which are not subscribers would
be inconvenienced (still not great, but a little better).
Cheers,
Ian.
-Original
Just a short heads-up for people who have posted recently:
In an attempt to improve upon the spam situation, I've probably messed
up mailman filtering rules to the extent that currently, everyone is
moderated. Please excuse this unwanted annoyance and a couple more[*]
which may turn up in the fol
On Wed, 2005-08-03 at 13:57 +0200, Graham Leggett wrote:
> Hi all,
> What method needs to be used to tell libtool to link to stdc++ that
> belongs to the compiler being run?
No method at all. libstdc++ is an internal library of g++ you are not
supposed to specify explicitly.
The issue you describ
Graham Leggett said:
> What method needs to be used to tell libtool to link to stdc++ that
> belongs to the compiler being run?
As was pointed out in a followup message (I deleted the message by
accident, sorry!), it should not be necessary to explicitly link to the
stdc++ library, however libtoo
Hi all,
I have been having a very strange problem that I have tracked down to
libtool, and I don't know how to proceed.
I have a Solaris v2.8 machine with a system installed copy of gcc v3.4.2
in /usr/local. Recently a private copy of gcc v4.0.1 was installed in a
private directory. The private d
Hi Steve,
* Steve Langasek wrote on Wed, Aug 03, 2005 at 03:37:18AM CEST:
> On Tue, Aug 02, 2005 at 05:41:32PM +0200, Ralf Wildenhues wrote:
> >
> > There were also a couple of bug reports related to Debian having
> > link_all_deplibs=no, but the user expecting otherwise.
> > For example, if you w
On Tue, Aug 02, 2005 at 05:41:32PM +0200, Ralf Wildenhues wrote:
> * Steve Langasek wrote on Wed, Jul 27, 2005 at 02:01:35PM CEST:
> > Is there no one out there who can answer this question from my mail of last
> > week,
> I've been away, sorry for the late response.
Ok, no worries. :)
> > On T
24 matches
Mail list logo
