[ http://nagoya.apache.org/jira/browse/XERCESC-939?page=history ]

Alberto Massari updated XERCESC-939:
------------------------------------

    Priority: Major

> ifeq test too restrictive in util/Compilers/Makefile
> ----------------------------------------------------
>
>          Key: XERCESC-939
>          URL: http://nagoya.apache.org/jira/browse/XERCESC-939
>      Project: Xerces-C++
>         Type: Bug
>   Components: Build
>     Versions: 2.3.0
>  Environment: Operating System: Solaris
> Platform: Sun
>     Reporter: Andy Sturrock
>     Assignee: Xerces-C Developers Mailing List

>
> The test for what your compiler is in order to assign the CPP_OBJECTS variable 
> is too tight I think.  It reads (line 103 in my case):
> ifeq (${CXX},CC))
> I ran:
> runConfigure -psolaris -c<full path>cc -x<full path>CC -rpthread
> which meant that CXX did not equal CC in this test.  I think the test should be 
> something like:
> CXXNAME:=$(shell basename ${CXX})
> ifeq (${CXXNAME},CC))
> The workaround is obviously to set your path so the compiler's bin dir is the 
> first element and use:
> runConfigure -psolaris -ccc -xCC -rpthread
> This took me a while to work out why I had problems with stricmp being missing 
> though as the problem is silent.  Maybe another solution is to test whether 
> CPP_OBJECTS is set and fail if not.  The reason I wanted to use the full path 
> is that I have several versions of CC and I wanted to make absolutely sure I 
> was using the correct one.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://nagoya.apache.org/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira


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

Reply via email to