The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: segaloco via TUHS <tuhs@tuhs.org>
To: The Eunuchs Hysterical Society <tuhs@tuhs.org>
Subject: [TUHS] Re: Trying to compile cron
Date: Fri, 29 Dec 2023 02:27:12 +0000	[thread overview]
Message-ID: <dxV8LctXeexS2_jsBD-t7orLN68Oimmq5QfT76oU3qvy7jSbOVr9SZcGKFCte1ayzHZ_bvbYzPBVksTdgRD5sSIVaEb3nydHxF6TbnApwN4=@protonmail.com> (raw)
In-Reply-To: <CAJXSPs8ew3BaE+BkOVWsx7vdxyGgrtkkDbwYK9zvRwY74v78Yw@mail.gmail.com>

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

If you're building on SVR3, cd /usr/src/cmd/cron && make -f cron.mk should suffice, all four variations on SVR3 sources I have have a cron.mk included.

Curiously, my SVR3.2 for 3B2 sources are missing elm.c and some other bits, and actually wouldn't build, if you've specifically snagged SVR3.2, you might try sources from another revision, if we pulled from the same source you're probably also missing elm.c in that specific revision. There's also an M68k version of SVR3.1 floating around out there somewhere that appears to have the necessary bits, I can't imagine there's anything platform specific in cron.

Finally, there's always good old "grep -r 'el_add' /usr/src" and "find /usr/src -name elm.c"

Best of luck!

- Matt G.
On Thursday, December 28th, 2023 at 1:21 PM, KenUnix <ken.unix.guy@gmail.com> 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
> 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.
> --
>
> WWL 📚

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

  parent reply	other threads:[~2023-12-29  2:27 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
2023-12-28 22:13   ` KenUnix
2023-12-28 22:44 ` Rich Salz
2023-12-29  2:27 ` segaloco via TUHS [this message]
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='dxV8LctXeexS2_jsBD-t7orLN68Oimmq5QfT76oU3qvy7jSbOVr9SZcGKFCte1ayzHZ_bvbYzPBVksTdgRD5sSIVaEb3nydHxF6TbnApwN4=@protonmail.com' \
    --to=tuhs@tuhs.org \
    --cc=segaloco@protonmail.com \
    /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).