this is what it was, and xchat still doesn't work with the new libxpg4
just so you all know.
[EMAIL PROTECTED] writes:
>Isn't this the true error message? This one is the well-known
>DYLD_FORCE_FLAT_NAMESPACE/libxpg4 bug.
¸.·´^`·.,][JFH][`·.,¸¸.·´][JFH][¸.·´^`·.,
Justin F. Hallett - Systems An
Maybe cc should be added to the list of commands that conflict with
libxpg4?
On Monday, April 15, 2002, at 03:46 PM, Justin Hallett wrote:
> good point thanks i just reinstalled libxpg4 not used to having it
> installed yet...thanks, I'll try that.
>
> [EMAIL PROTECTED] writes:
>> Isn't this th
good point thanks i just reinstalled libxpg4 not used to having it
installed yet...thanks, I'll try that.
[EMAIL PROTECTED] writes:
>Isn't this the true error message? This one is the well-known
>DYLD_FORCE_FLAT_NAMESPACE/libxpg4 bug.
¸.·´^`·.,][JFH][`·.,¸¸.·´][JFH][¸.·´^`·.,
Justin F. Hallett
Justin Hallett wrote:
> dyld: /sw/bin/bash multiple definitions of symbol _BC
Isn't this the true error message? This one is the well-known
DYLD_FORCE_FLAT_NAMESPACE/libxpg4 bug.
--
Martin
___
Fink-devel mailing list
[EMAIL PROTECTED]
https://lists.
did both of these and still the same errors.
[EMAIL PROTECTED] writes:
>HFS+ is case insensitive, so /usr/bin/CC is actually cc, whereas on some
>systems I think it's the C++ compiler frontend type thing. Perhaps you
>should modify the Makefiles or whatever to use /usr/bin/c++ instead.
¸.·´^`·
On Monday, April 15, 2002, at 05:43 PM, Justin Hallett wrote:
>
>
> Missing C++ runtime support for CC (/usr/bin/CC).
HFS+ is case insensitive, so /usr/bin/CC is actually cc, whereas on some
systems I think it's the C++ compiler frontend type thing. Perhaps you
should modify the Makefiles or
why am i getting lib errors when it's not linking??
Missing C++ runtime support for CC (/usr/bin/CC).
Compilation of the following test program failed:
--
#include "iostream.h"
int main(){ cout << "Hello World!" << endl; return 0;}
-
