Well, this has been happening for about a year on my dev box. It's not
gcc 3.1 specific.
I've never gotten around to figuring out why it works on some machines.
On Sat, 29 Jun 2002 19:41:51 -0700, David O'Brien wrote:
> On Sat, Jun 29, 2002 at 11:30:48PM +0100, Brian Somers wrote:
> > The probl
On Sat, Jun 29, 2002 at 11:30:48PM +0100, Brian Somers wrote:
> The problem is because the glxinfo program uses CCLINK to
> link, but it's a c++ program. Changing the CCLINK to CXXLINK
> works.
We can't be the only ones seeing this -- surely anyone using Gcc 3.1 on
their i386 (any OS) box. Has
I've been seing this problem for ages on my dev box, but it
doesn't happen on other boxes.
The problem is because the glxinfo program uses CCLINK to
link, but it's a c++ program. Changing the CCLINK to CXXLINK
works.
I have no idea why there's no problem on some machines.
On Mon, 17 Jun 2002 1
On Sun, Jun 23, 2002 at 12:46:25 -0700, David O'Brien wrote:
> It is not OK. One should NEVER be explicity adding "-lstdc++". Please
> use the right compiler which takes care of all this for you.
I dont know how to make a patch against X (it's too complex :/ )
but I do know that it works (for m
On Sun, Jun 23, 2002 at 07:19:06PM +0800, Ying-Chieh Liao wrote:
> On Mon, Jun 17, 2002 at 12:09:14 +0800, Ying-Chieh Liao wrote:
> > make build all ok, but failed on install
> > should I rebuild world first ?
>
> after adding "-lstdc++" , it's all ok
It is not OK. One should NEVER be explicity
On Mon, Jun 17, 2002 at 12:09:14 +0800, Ying-Chieh Liao wrote:
> make build all ok, but failed on install
> should I rebuild world first ?
after adding "-lstdc++" , it's all ok
and I find that everything link with libGL* must link to stdc++, too
(at least ports/x11-toolkits/gtkglarea)
maybe th
