RE: {bb} Solaris 10 Compile errors:

["Greg Paik" <gpaik@smithandhawken.com>]

My bad actually, I forgot to install the C/C++ header files for general
software development, SUNWhea.


Greg


-----Original Message-----
From: owner-bb@bb4.com [mailto:owner-bb@bb4.com] On Behalf Of Andy
France
Sent: Tuesday, March 08, 2005 5:07 PM
To: bb@bb4.com
Subject: Re: {bb} Solaris 10 Compile errors:







owner-bb@bb4.com wrote on 09/03/2005 11:49:15:

> Anyone compile BBc1.9e for Solaris 10 (Core installation with gmake 
> 3.80 and gcc 3.4.3) and run into the following compilation errors:

> bash-3.00# gcc -v
> Reading specs from /usr/sfw/lib/gcc/sparc-sun-solaris2.10/3.4.3/specs
> Configured with:
> /gates/sfw10/builds/sfw10-gate/usr/src/cmd/gcc/gcc-3.4.3/configure
> --prefix=/usr/sfw --with-as=/usr/sfw/bin/gas --with-gnu-as 
> --with-ld=/usr/ccs/bin/ld --without-gnu-ld --enable-languages=c,c++ 
> --enable-shared Thread model: posix gcc version 3.4.3 
> (csl-sol210-3_4-branch+sol_rpath)

>
> bash-3.00# make

I haven't run Sol10 yet... any chance the gnu make is installed as gmake
rather than make?

> Making solaris makefile
> make[1]: Entering directory `/export/home/orwell/bbc1.9e/src'
> BBOS="solaris" CC="gcc" CFLAGS="-Dsolaris -O -DBZERO -DGETTIMEOFDAY 
> -DREGEXEC" LIBS="-ll -lnsl -lsocket" make -e bball
> make[2]: Entering directory `/export/home/orwell/bbc1.9e/src'
> gcc -Dsolaris -O -DBZERO -DGETTIMEOFDAY -DREGEXEC 
> `./minimake/genbbdefs` -g -o bb.o -c bb.c In file included from 
> bb.c:22:
> bb.h:9:19: stdio.h: No such file or directory
> bb.h:10:23: sys/types.h: No such file or directory
> bb.h:22:24: sys/socket.h: No such file or directory
> bb.h:23:24: netinet/in.h: No such file or directory
> bb.h:24:23: arpa/inet.h: No such file or directory
> bb.h:25:57: sys/signal.h: No such file or directory
> bb.h:26:64: sys/wait.h: No such file or directory
> bb.h:27:58: syslog.h: No such file or directory
> bb.h:28:65: setjmp.h: No such file or directory
> bb.c:23:19: ctype.h: No such file or directory
> bb.c:24:43: netdb.h: No such file or directory
> bb.c: In function `bbnotify':
> bb.c:32: error: `NULL' undeclared (first use in this function)
> bb.c:32: error: (Each undeclared identifier is reported only once
> bb.c:32: error: for each function it appears in.)
> bb.c: In function `main':
> bb.c:92: error: `stderr' undeclared (first use in this function)
> bb.c:102: error: `stdin' undeclared (first use in this function)
> bb.c:102: error: `NULL' undeclared (first use in this function)
> make[2]: *** [bb.o] Error 1
> make[2]: Leaving directory `/export/home/orwell/bbc1.9e/src'
> make[1]: *** [all] Error 2
> make[1]: Leaving directory `/export/home/orwell/bbc1.9e/src'
> make: *** [all] Error 2

> Thanks in advance,

> Greg

HTH,
Andy.


########################################################################
#############

This email is intended for the person to whom it is addressed only. If
you are not the intended recipient, do not read, copy or use the
contents in any way. The opinions expressed may not necessarily reflect
those of ZESPRI Group of Companies ('ZESPRI').

While every effort has been made to verify the information contained
herein, ZESPRI does not make any representations as to the accuracy of
the information or to the performance of any data, information or the
products mentioned herein.
ZESPRI will not accept liability for any losses, damage or consequence,
however, resulting directly or indirectly from the use of this
e-mail/attachments.
########################################################################
#############
--
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-==-=-=-=-=-=-=-=-=-=-=-=
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.

--
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-==-=-=-=-=-=-=-=-=-=-=-=
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.