The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: Warner Losh <imp@bsdimp.com>
To: "Jeremy C. Reed" <reed@reedmedia.net>
Cc: KenUnix <ken.unix.guy@gmail.com>, UNIX TUHS Group <tuhs@tuhs.org>
Subject: [TUHS] Re: Trying to compile cron
Date: Thu, 28 Dec 2023 14:57:59 -0700	[thread overview]
Message-ID: <CANCZdfpxy8G-G+zZ_KjRUbtuM77GNiRTGsx0-0Zkvhk4xkMz=A@mail.gmail.com> (raw)
In-Reply-To: <a80eb46-c16b-5ef9-68d0-e9cefff6d646@reedmedia.net>

[-- Attachment #1: Type: text/plain, Size: 1632 bytes --]

On Thu, Dec 28, 2023, 2:55 PM Jeremy C. Reed <reed@reedmedia.net> wrote:

> On Thu, 28 Dec 2023, KenUnix wrote:
>
> > Hi. I am trying to compile cron for the 3b2-400 and 3b2-700
> > and am apparently missing required libraries. The reason is
> > on the 3b2-400 after boot up it complains there is corruption
> > in the crontab for every user lp, sysadm, root and so on.
> >
> > # make cron
> >         cc -O  cron.c -o cron
>

Try just cc *.c -o cron

> undefined                       first referenced
> >  symbol                             in file
> > el_add                              cron.o
> > el_delete                           cron.o
> > el_empty                            cron.o
> > el_first                            cron.o
> > el_init                             cron.o
> > xmalloc                             cron.o
> > el_remove                           cron.o
> > num                                 cron.o
> > days_in_mon                         cron.o
> > days_btwn                           cron.o
> > ld fatal: Symbol referencing errors. No output written to cron
> > *** Error code 13
> >
> > Stop.
> >
> > Does anyone have these libraries? Thanks.
>
> At first I thought the el_ code was editline code but that doesn't make
> sense in cron, but then I found the General-Purpose Event List Manager.
>
> See
> https://www.tuhs.org/cgi-bin/utree.pl?file=SysVR4/cmd/cron/elm.c
> and
> https://www.tuhs.org/cgi-bin/utree.pl?file=SysVR4/cmd/cron/funcs.c
>
> Does your cron source come with this other code?
>
> By the way, how to browse the SysVR4 code at TUHS?
>

[-- Attachment #2: Type: text/html, Size: 2722 bytes --]

  reply	other threads:[~2023-12-28 21:58 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-12-28 21:21 [TUHS] " KenUnix
2023-12-28 21:55 ` [TUHS] " Jeremy C. Reed
2023-12-28 21:57   ` Warner Losh [this message]
2023-12-28 22:13   ` KenUnix
2023-12-28 22:44 ` Rich Salz
2023-12-29  2:27 ` segaloco via TUHS
2023-12-28 22:23 Brian Walden

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CANCZdfpxy8G-G+zZ_KjRUbtuM77GNiRTGsx0-0Zkvhk4xkMz=A@mail.gmail.com' \
    --to=imp@bsdimp.com \
    --cc=ken.unix.guy@gmail.com \
    --cc=reed@reedmedia.net \
    --cc=tuhs@tuhs.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).