Menu
▾
▴
#4 *BSD builds not always successful
Reported by esn@ematic.com:
Hi all can some 1 plz help me i whant to build
LCDproc0.4.1 in a FreeBSD
box.
i du the ./configure and all gos well, then the make
and this comes out
make all-recursive
Making all in shared
Making all in clients
Making all in examples
Making all in headlines
Making all in lcdproc
Making all in server
Making all in drivers
gcc -DHAVE_CONFIG_H -I. -I. -I../.. -I./.. -I../..
-Wall -Wno-unused -O6
-c glkproto.c
glkproto.c: In function `glkopen':
glkproto.c:48: `CBAUD' undeclared (first use in this
function)
glkproto.c:48: (Each undeclared identifier is reported
only once
glkproto.c:48: for each function it appears in.)
glkproto.c:54: `O_SYNC' undeclared (first use in this
function)
*** Error code 1
Stop in /tmp/lcdproc-0.4.1/server/drivers.
*** Error code 1
Stop in /tmp/lcdproc-0.4.1/server.
*** Error code 1
Stop in /tmp/lcdproc-0.4.1.
*** Error code 1
Stop in /tmp/lcdproc-0.4.1.
--- [end of report] ---
Other users have reported similar problems, and this
can be duplicated on the compile farm at Sourceforge.
The above user eventually reported getting it to
compile, waiting for update from him to detail how he
accomplished this.
*BSD are desired compile targets, so all our releases
should compile on the BSDs.
Logged In: YES
user_id=53970
Here's the answer I posted to the mailing list:
As for a correction to the problem,
for the CBAUD check out:
http://docs.FreeBSD.org/cgi/getmsg.cgi?fetch=313627+
0+/usr/local/www/db/text/1997/freebsd-current/1997111
6.freebsd-current
and I just realised I posted a message similar on
30-05-2001
(http://lists.omnipotent.net/lcdproc/200105/msg00119.h
tml)
and for the O_SYNC, check out:
http://www.chiark.greenend.org.uk/pipermail/userv-disc
uss/2001/000043.html
In short, adding:
-----
#ifndef CBAUD
#define CBAUD 0010017
#endif
#ifndef O_SYNC
#define O_SYNC O_FSYNC
#endif
-----
on top of server/drivers/glkproto.c removes the
compilation errors. But I'm not sure if it's the best way of
doing it...
Logged In: YES
user_id=839
Here's an instance where even autogen.sh doesn't work right
on FreeBSD:
From: David Douthitt <ssrat@mailbag.com>
Subject: [lcdproc] Compiling on the SF Compile Farm...
I tried the Compile Farm for the first time - pretty nice!
lcdproc compiled fine under Solaris 8, but had problems
under FreeBSD
4.3. Can someone clear this up?
bash-2.05$ sh ./autogen.sh
Running aclocal ...
aclocal: /usr/local/share/aclocal/sdl11.m4: 11: duplicated macro
`AM_PATH_SDL'
Running autoheader...
Running automake ...
automake: configure.in: installing `./install-sh'
automake: configure.in: installing `./mkinstalldirs'
automake: configure.in: installing `./missing'
automake: configure.in: installing `./config.guess'
automake: configure.in: installing `./config.sub'
Running autoconf ...
autoconf: Undefined macros:
configure.in:93:AC_GET_FS_INFO
bash-2.05$ uname -a
FreeBSD usf-cf-x86-freebsd-1.sourceforge.net 4.3-RELEASE FreeBSD
4.3-RELEASE #0: Sat Apr 21 10:54:49 GMT 2001
jkh@narf.osd.bsdi.com:/usr/src/sys/compile/GENERIC i386
bash-2.05$ autoconf --version
Autoconf version 2.13
bash-2.05$ aclocal --version
aclocal (GNU automake) 1.4
Copyright (C) 1999 Free Software Foundation, Inc.
This is free software; see the source for copying
conditions. There is
NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A
PARTICULAR
PURPOSE.
Written by Tom Tromey <tromey@cygnus.com>
bash-2.05$
Logged In: YES
user_id=53970
Here's a status report:
LCDd (server) now compiles on OpenBSD, NetBSD
and FreeBSD. It doesn't use FreeBSD's native port io
funtions. This should be solved.
A couple of lcdproc's (client) screens have been ported
to *BSD, but some haven't. This should also be solved.
Logged In: YES
user_id=53970
Here's (another status report):
LCDd (server) now compiles on OpenBSD, NetBSD
and FreeBSD. It does use FreeBSD's i386_set_ioperm
but it stills uses i386 ASM inb and outb since I couldn't
find their FreeBSD equivalent.
A couple of lcdproc's (client) screens have been ported
to *BSD, but some haven't. This should also be solved.
Logged In: YES
user_id=839
Closing this bug -- it's very, very old, and is believed to have
been fixed. If this is NOT the case, please re-open the bug and
provide additional details.