Solaris carriage return build problem
-------------------------------------

         Key: XERCESC-1551
         URL: http://issues.apache.org/jira/browse/XERCESC-1551
     Project: Xerces-C++
        Type: Bug
  Components: Build  
    Versions: 2.7.0    
 Environment: Solaris sparcv9
    Reporter: David G. Pickett
    Priority: Minor


Hi,

I'm building Xerces-C 2.7.0 with an old SunWSPro 4.2 CC/cc on Solaris 8 and a 
spacv9.  Problem is, I am either pulling carriage returns out of the conf* 
files or turning them into linefeeds to make the runConfigure/configure work.  
Is there a good reason for all this ^M ?  Maybe one of my tools handles inputs 
differently than yours.  I have previously built a lot of GNU and open stuff 
without hitting this.  Maybe I did not need to run autoconf, as there was 
already a configure script there -- that's a new step for me.  I found the 
files lacked execute permission, too, so I put a sh command before them.  I 
think I have configure'd ok, but the message no longer matches the docs it 
references, and is not reassuring  - a 'configure done, ready to make' message 
would be nice!  --  Yes, it seems to be making something, finally:

 .
 .
 .
config.status: creating internal/Makefile
config.status: creating sax/Makefile
config.status: creating sax2/Makefile
config.status: creating ../../obj/Makefile
config.status: executing default commands

Having build problems?
Read instructions at http://xml.apache.org/xerces-c/build.html
Still cannot resolve it?
Find out if someone else had the same problem before.
Go to http://marc.theaimsgroup.com/?l=xerces-c-dev
$

Best regards,

David


-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira


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

Reply via email to