[
https://issues.apache.org/jira/browse/XERCESC-939?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alberto Massari closed XERCESC-939.
-----------------------------------
Resolution: Won't Fix
Assignee: (was: Xerces-C Developers Mailing List)
Xerces 3 uses autoconf-generated makefiles, so this is no more an issue
> ifeq test too restrictive in util/Compilers/Makefile
> ----------------------------------------------------
>
> Key: XERCESC-939
> URL: https://issues.apache.org/jira/browse/XERCESC-939
> Project: Xerces-C++
> Issue Type: Bug
> Components: Build
> Affects Versions: 2.3.0
> Environment: Operating System: Solaris
> Platform: Sun
> Reporter: Andy Sturrock
>
> 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.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
