BB Unix Network Monitor - Message

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: {bb} Solaris 10 Compile Problem



I had this same problem with Solaris10 on Sparc. I resolved it by using the version of gcc from sunfreeware.com instead of the version that comes with Solaris10.

On Wed, 20 Jul 2005, Matt Manfredonia wrote:

Date: Wed, 20 Jul 2005 09:53:13 -0400
From: Matt Manfredonia <mmanfred@amaranthllc.com>
Reply-To: bb@bb4.com
To: bb@bb4.com
Subject: {bb} Solaris 10 Compile Problem



Hello,

I have a solaris10x86 server and after running bbconfig (trying
different ones as well), when I run make in bbc1.9h-btf/src I get the
following

bash-3.00$ make
Making solaris makefile
make[1]: Entering directory `/usr/local/bb/bbc1.9h-btf/src'
BBOS="solaris" CC="gcc" CFLAGS=" -Dsolaris -O -DBZERO -DGETTIMEOFDAY
-DREGEXEC" LIBS="-ll -lnsl -lsocket -lkstat" make -e bball
make[2]: Entering directory `/usr/local/bb/bbc1.9h-btf/src'
gcc  -Dsolaris -O -DBZERO -DGETTIMEOFDAY -DREGEXEC
`./minimake/genbbdefs` -g -o bb.o -c bb.c
In file included from /usr/include/sys/signal.h:34,
                from bb.h:28,
                from bb.c:22:
/usr/include/sys/siginfo.h:259: error: parse error before "ctid_t"
/usr/include/sys/siginfo.h:292: error: parse error before '}' token
/usr/include/sys/siginfo.h:294: error: parse error before '}' token
/usr/include/sys/siginfo.h:390: error: parse error before "ctid_t"
/usr/include/sys/siginfo.h:392: error: conflicting types for `__proc'
/usr/include/sys/siginfo.h:261: error: previous declaration of `__proc'
/usr/include/sys/siginfo.h:398: error: conflicting types for `__fault'
/usr/include/sys/siginfo.h:267: error: previous declaration of `__fault'
/usr/include/sys/siginfo.h:404: error: conflicting types for `__file'
/usr/include/sys/siginfo.h:273: error: previous declaration of `__file'
/usr/include/sys/siginfo.h:420: error: conflicting types for `__prof'
/usr/include/sys/siginfo.h:287: error: previous declaration of `__prof'
/usr/include/sys/siginfo.h:424: error: conflicting types for `__rctl'
/usr/include/sys/siginfo.h:291: error: previous declaration of `__rctl'
/usr/include/sys/siginfo.h:426: error: parse error before '}' token
/usr/include/sys/siginfo.h:428: error: parse error before '}' token
/usr/include/sys/siginfo.h:432: error: parse error before "k_siginfo_t"
/usr/include/sys/siginfo.h:437: error: parse error before '}' token
In file included from bb.h:28,
                from bb.c:22:
/usr/include/sys/signal.h:85: error: parse error before "siginfo_t"
In file included from bb.h:29,
                from bb.c:22:
/usr/include/sys/wait.h:86: error: parse error before "siginfo_t"
make[2]: *** [bb.o] Error 1
make[2]: Leaving directory `/usr/local/bb/bbc1.9h-btf/src'
make[1]: *** [all] Error 2
make[1]: Leaving directory `/usr/local/bb/bbc1.9h-btf/src'
make: *** [all] Error 2

Will this version for with solaris10x86?

Thanks
--matt


CONFIDENTIALITY AND SECURITY NOTICE: This e-mail, including any attachments, may contain confidential and proprietary information and may be legally privileged or otherwise protected by law. It may be read and used solely by the intended recipient(s), and any review, use or distribution by others is strictly prohibited. If you are not an intended recipient, please notify us immediately by replying to the sender and delete this e-mail, including any attachments, from your system immediately without reading, copying or distributing them. Thank you for your cooperation. Amaranth and its affiliates retain all proprietary rights they may have in the information. We cannot give any assurances that this e-mail or any attachments are free of viruses or other harmful code. We reserve the right to monitor, intercept and block all communications involving our computer systems.


Chris Naude
cnaude@36bit.com
SDF Public Access UNIX System - http://sdf.lonestar.org
--
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-==-=-=-=-=-=-=-=-=-=-=-=
To unsubscribe from this list, or to subscribe to the bb-digest list
send e-mail to mailto:majordomo@bb4.com with unsubscribe bb -and/or-
subscribe bb-digest in the BODY of the message.


Home | Main Index | Thread Index