DwD,
Thank you for your help.
GNU flex seemed to have solved my compile problems.
> -----Original Message-----
> From: Daryl W. Dunbar [SMTP:[EMAIL PROTECTED]]
> Sent: Thursday, February 25, 1999 4:24 PM
> To: Syed Ali; [EMAIL PROTECTED]
> Subject: RE: [ADMIN] errors compiling and errors in binary version
>
> As for the compile problems, on Solaris you need flex, the built-in
> lex does not work. I fetched a flex pkg from sunsite.unc.edu, but
> you can get it other places and/or compile it yourself.
>
> Since you are running on Solaris, you will need to configure your
> kernel to allow more semaphores than the default (60) and probably
> more shared memory. Here are my entries from /etc/system, these
> allow very large allocations of semaphores and the shared memory can
> accommodate at least 128 backend processes.
>
> set shmsys:shminfo_shmmax=16777216
> set shmsys:shminfo_shmmin=1
> set shmsys:shminfo_shmmni=128
> set shmsys:shminfo_shmseg=51
> *
> set semsys:seminfo_semmap=128
> set semsys:seminfo_semmni=128
> set semsys:seminfo_semmns=8192
> set semsys:seminfo_semmnu=8192
> set semsys:seminfo_semmsl=64
> set semsys:seminfo_semopm=32
> set semsys:seminfo_semume=32
>
> Don't forget to reboot after editing /etc/system.
>
> As for the binary problems, it looks like a shared library link is
> missing. I remember some entries in the INSTALL file that refer to
> telling your system where to look for the shared libraries, you
> might want to try that. When I compiled 6.4.2 on Solaris with all
> the default location settings, I did not have to do anything special
> for the libraries. I simply did:
> ./configure --without-CXX
> make
> make install
> ...
>
> DwD
>
> > -----Original Message-----
> > From: [EMAIL PROTECTED]
> > [mailto:[EMAIL PROTECTED]]On Behalf Of Syed Ali
> > Sent: Thursday, February 25, 1999 1:59 PM
> > To: [EMAIL PROTECTED]
> > Subject: [ADMIN] errors compiling and errors in binary version
> >
> >
> > hi
> > i downloaded the source code and binaries for postfresql
> > but am unable
> > to use either one
> > the following is the error message i get when i try and
> > use the binary
> > version:
> >
> > $ uname -a
> > SunOS myhost 5.6 Generic_105181-03 sun4u sparc SUNW,Ultra-2
> > $ cat .profile
> > export LD_LIBRARY_PATH=/usr/local/pgsql/lib
> > export PATH=$PATH:/usr/local/pgsql/bin
> > export MANPATH=$MANPATH:/usr/local/pgsql/man
> > export PGLIB=/usr/local/pgsql/lib
> > export PGDATA=/usr/local/pgsql/data
> > export USER=pgsql
> >
> > $ initdb
> >
> > ld.so.1: pg_id: fatal: libgen.so.1: open failed: No such file or
> > directory
> > Unable to determine a valid username. If you are running
> > initdb without an explicit username specified, then there
> > may be a problem with finding the Postgres shared library
> > and/or the pg_id utility.
> > $
> >
> > This is using postgesql v6.4.2
> >
> > As far as the source code goes, I get the following error:
> > make[3]: Entering directory
> > `/local/src/pgsql/src/interfaces/ecpg/preproc'
> > /usr/ccs/bin/yacc -d preproc.y
> > "preproc.y", line 576: warning: redeclaration of
> > precedence of UNLISTEN.
> >
> > gcc -I../../../include -I../../../backend -Wall
> > -Wmissing-prototypes
> > -I../include -DMAJOR_VERSION=2 -DMINOR_VERSION=4 -DPATCHLEVEL=4
> > -DINCLUDE_PATH=\"/usr/local/pgsql/include\" -c y.tab.c
> > -o y.tab.o
> > /usr/ccs/bin/yaccpar: In function `yyparse':
> > /usr/ccs/bin/yaccpar:274: warning: implicit declaration
> > of function
> > `yylex'
> > /usr/ccs/bin/yaccpar:374: warning: label `yyerrlab'
> > defined but not used
> >
> > /usr/ccs/bin/yaccpar:164: warning: label `yynewstate'
> > defined but not
> > used
> > lex pgc.l
> > "pgc.l":line 53: Error: missing translation value
> > make[3]: *** [pgc.c] Error 1
> > make[3]: Leaving directory
> > `/local/src/pgsql/src/interfaces/ecpg/preproc'
> > make[2]: *** [all] Error 2
> > make[2]: Leaving directory `/local/src/pgsql/src/interfaces/ecpg'
> > make[1]: *** [all] Error 2
> > make[1]: Leaving directory `/local/src/pgsql/src/interfaces'
> > make: *** [all] Error 2
> > $
> >
> > Any leads on how I can solve these problems?
> >
> > Thank you.
> >
> >
> >
> >
> >
>
