Hi Lars,
Thanks for pointing out the fact that boost
sources are C code. I’m still not able to build Boost.Jam, even I’ve
set the CC and CXX correctly. It complained syntax errors in ./tools/build/v2/engine/src/fileunix.c:
# CC=/opt/SUNWspro11/SUNWspro/bin/cc; export CC
# CXX=/opt/SUNWspro11/SUNWspro/bin/CC; export CXX
#
PATH=/usr/local/ssl/bin:/opt/SUNWspro11/SUNWspro/bin:/usr/local/bin:/usr/sfw/bin/:/usr/sbin:/usr/bin:/apps/gnu/bin;
export PATH
# which cc
/opt/SUNWspro11/SUNWspro/bin/cc
# which CC
/opt/SUNWspro11/SUNWspro/bin/CC
# ./bootstrap.sh --with-toolset=sun-11.0
--prefix=/usr/local/boost1.46.1-sun --with-python=python3
--with-python-root=/usr/local/bin
-n Building Boost.Jam with toolset sun-11.0...
Failed to build Boost.Jam
Consult 'bootstrap.log' for more details
# tail -50 bootstrap.log
"fileunix.c", line 82: syntax error before
or at: ||
"fileunix.c", line 82: invalid source
character: '\'
"fileunix.c", line 84: warning: invalid
white space character in directive
"fileunix.c", line 85: warning: invalid
white space character in directive
"fileunix.c", line 86: warning: invalid
white space character in directive
"fileunix.c", line 88: warning: invalid
white space character in directive
"fileunix.c", line 90: warning: invalid
white space character in directive
"fileunix.c", line 95: warning: invalid white
space character in directive
"fileunix.c", line 98: warning: invalid
white space character in directive
"fileunix.c", line 127: warning: old-style
declaration or incorrect type for: defined
"fileunix.c", line 127: identifier
redefined: defined
current :
function() returning int
previous:
function() returning int : "fileunix.c", line 82
"fileunix.c", line 127: syntax error before
or at: scanback
"fileunix.c", line 127: warning: undefined
or missing type for: scanback
"fileunix.c", line 127: warning: undefined
or missing type for: void
"fileunix.c", line 128: parameter not in
identifier list: file_dirscan
"fileunix.c", line 141: parameter not in
identifier list: files
"fileunix.c", line 166: syntax error before
or at: .
"fileunix.c", line 166: parameter not in
identifier list: debug
"fileunix.c", line 166: syntax error before
or at: )
"fileunix.c", line 167: warning: function
prototype parameters must have types
"fileunix.c", line 167: parameter not in
identifier list: printf
"fileunix.c", line 169: warning: function
prototype parameters must have types
"fileunix.c", line 169: parameter not in
identifier list: string_new
"fileunix.c", line 170: syntax error before
or at: while
"fileunix.c", line 170: syntax error before
or at: =
"fileunix.c", line 170: warning: function
prototype parameters must have types
"fileunix.c", line 170: parameter not in
identifier list: readdir
"fileunix.c", line 170: syntax error before
or at: )
"fileunix.c", line 172: warning: invalid
white space character in directive
"fileunix.c", line 175: warning: invalid
white space character in directive
"fileunix.c", line 177: warning: invalid
white space character in directive
"fileunix.c", line 186: warning: function
prototype parameters must have types
"fileunix.c", line 186: parameter not in
identifier list: string_free
"fileunix.c", line 188: warning: function
prototype parameters must have types
"fileunix.c", line 188: parameter not in
identifier list: closedir
"fileunix.c", line 190: parameter not in
identifier list: d
"fileunix.c", line 190: syntax error before
or at: ->
"fileunix.c", line 190: parameter not in
identifier list: files
"fileunix.c", line 190: cannot initialize
parameter: files
"fileunix.c", line 191: syntax error before
or at: }
"fileunix.c", line 201: parameter not in
identifier list: files
"fileunix.c", line 212: warning: function
prototype parameters must have types
"fileunix.c", line 212: parameter not in
identifier list: profile_exit
"fileunix.c", line 213: syntax error before
or at: }
"fileunix.c", line 216: parameter not in
identifier list: file_info_t
"fileunix.c", line 217: parameter not in
identifier list: file_query
"fileunix.c", line 217: cannot recover from
previous errors
cc: acomp failed for fileunix.c
Any ideas?
Alex
-----Original Message-----
From: boost-build-bounces@lists.boost.org
[mailto:boost-build-bounces@lists.boost.org] On Behalf Of Lars Viklund
Sent: May 14, 2011 2:00 AM
To: boost-build@lists.boost.org
Subject: Re: [Boost-build] bootstrap failed using sun studio 11 - Please help
On Fri, May 13, 2011 at 03:34:18PM -0400, Alex Lai (Scotia Capital)
wrote:
>
I'm trying to build boost 1.46.1 with Sun Studio 11 on a sparc machine. Below
is what I did:
> # CC=/opt/SUNWspro11/SUNWspro/bin/CC; export CC
>
>
It looks like the cc is used instead of CC.
>
Could someone please help?
The last time I used the Sun tools:
* 'cc' was the C compiler and belonged in $CC;
* 'CC' was the C++ compiler and belonged in $CXX.
As those sources you're trying to build there are C, it seems wrong to
be trying to force them through the C++ compiler.
--
Lars Viklund | zao@acc.umu.se
_______________________________________________
Unsubscribe & other changes:
http://lists.boost.org/mailman/listinfo.cgi/boost-build
---
The information transmitted is intended only for the person or entity to which it is addressed and may contain confidential and/or privileged material. Any review, re-transmission, dissemination or other use of, or taking of any action in reliance upon this information by persons or entities other than the intended recipient is prohibited. If you received this email in error, please contact the sender immediately by return electronic transmission and then immediately delete this transmission, including all attachments, without copying, distributing or disclosing same. No member of the Scotiabank Group is liable for any errors or omissions in the content or transmission of this email or accepts any responsibility or liability for loss or damage arising from the receipt or use of this transmission. Scotiabank Group may monitor, retain and/or review email. Trading instructions received by e-mail or voicemail will not be accepted or acted upon. Unless indicated in writing, opinions contained in this email are those of the author and are not endorsed by any member of the Scotiabank Group. For information on some members of the Scotiabank Group, click here. For authorized users of the Scotia Capital trademark, click here.
Pour obtenir la traduction en français: http://www.scotiacapital.com/EmailDisclaimer/French.htm
Traducción en español: http://www.scotiacapital.com/EmailDisclaimer/Spanish.htm