http://nagoya.apache.org/bugzilla/show_bug.cgi?id=2681

*** shadow/2681 Wed Jul 18 13:42:21 2001
--- shadow/2681.tmp.12912       Wed Jul 18 13:42:21 2001
***************
*** 0 ****
--- 1,31 ----
+ +============================================================================+
+ | Can't build with gcc with a non-standard name                              |
+ +----------------------------------------------------------------------------+
+ |        Bug #: 2681                        Product: Xerces-C++              |
+ |       Status: NEW                         Version: 1.5.1                   |
+ |   Resolution:                            Platform: Sun                     |
+ |     Severity: Major                    OS/Version: Solaris                 |
+ |     Priority: Other                     Component: Build                   |
+ +----------------------------------------------------------------------------+
+ |  Assigned To: [EMAIL PROTECTED]                                  |
+ |  Reported By: [EMAIL PROTECTED]                                       |
+ |      CC list: Cc:                                                          |
+ +----------------------------------------------------------------------------+
+ |          URL:                                                              |
+ +============================================================================+
+ |                              DESCRIPTION                                   |
+ It's not possible (on Solaris 8) to build Xerces-C++ if your g++ is named
+ anything other than "g++".
+ 
+ This is because Makefile.incl explicitly compares $(CXX) with "g++" to determine
+ whether to use gcc-style or Sun CC-style arguments.
+ 
+ Because g++ 2.95.2 and g++ 3.0 are not binary-compatible, if you want to be able
+ to test Xerces-using code with both compilers, you need to be able to build with
+ both compilers.  On my system, "g++" is g++ 3.0, and g++ 2.95.2 is installed as
+ "g++-2.95.2".  However, if I set CXX=g++-2.95.2 at configure time, the code
+ won't build.
+ 
+ Because configure has a check to see if your compiler is gcc, Makefile.incl
+ ought to be able to base its behavior on that information, rather than the
+ string comparison.

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to