[comp.sys.alliant] programs with syslog

gjalt@ele.tue.nl (Gjalt de Jong) (01/02/91)

We have just installed Concentrix 5.6.0 on our Alliant FX8.
Now we encountered the following problem (stripped to its essence)

#include <syslog.h>

main ()
{
  openlog ("thisprogram", LOG_PID, LOG_USER);

}

When we compile, we get some undefined symbols:

Undefined:
_LOG_MASK
_vsprintf
_LOG_FAC
_LOG_PRI

We found out that is due to some error (?) in /lib/libc.a:

nm /lib/libc.a:
...
syslog.o:
         U _LOG_FAC
         U _LOG_MASK
         U _LOG_PRI
         U __exit
         U _alarm
         U _close
...
00000000 T _syslog
         U _time
         U _vfork
         U _vsprintf



So my question is: did we something wrong when installing the new operating
system or can this strange behaviour also be found on other systems.
It isn't caused because of an old version of the syslog.h include file, since
when we compile the syslog.c from the C library out of the BSD sources and
link it with the program, there's no problem.

So  is this just another example of having to compiling Unix yourself on an
Alliant?
--
__
Gjalt G. de Jong,                 | Phone: +(31)40-473345
Eindhoven University of Technology, Dept. of Electr. Eng. (ES/EH 7.26)
P.O. Box 513, 5600 MB Eindhoven, The Netherlands
Email: gjalt@es.ele.tue.nl

eschle@forty2.physik.unizh.ch (Patrik Eschle) (01/03/91)

gjalt@es.ele.tue.nl complains about a problem with libc(syslog.o) and
asks:

>So  is this just another example of having to compiling Unix yourself on an
>Alliant?

Yes, and an old one - we've reported this back in March 1990. Remove
their syslog.o from libc and replace it by the BSD syslog.o.

It took them almost a year from 5.5 to 5.6 - why don't they have 10
minutes to fix this trivial bug?

Patrik
-- 
Patrik Eschle, Physics Institute University of  Zuerich (Switzerland)
inet: eschle@physik.unizh.ch (bang: uunet!chx400!forty2!eschle)
          -> Send CHUUG mail to chuug@chuug.uu.ch <-