From: Brian Walden <tuhs@cuzuco.com>
To: <tuhs@tuhs.org>
Subject: [TUHS] Re: Trying to compile cron
Date: Thu, 28 Dec 2023 17:23:02 -0500 (EST) [thread overview]
Message-ID: <202312282223.3BSMN2W8004242@cuzuco.com> (raw)
As I messed with making a custom cron in the late 80s,
remembered the the el_ functions are for event list processing.
But you didn't specify the source of your source, by the hardware
it needs to be of System V heritage. And a lot of that source is hard
to offically come by due to licensing. Good way to view old SVR4 is
to look at OpenIndiana, Illumos, or OpenSolaris code bases that you can
find. You're in luck, as TUHS has a copy, see -- https://www.tuhs.org/cgi-bin/utree.pl?file=OpenSolaris_b135/cmd/cron/elm.c
Look at the Makefile for the other files you need to compile into it too.
-Brian
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
> 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.
next reply other threads:[~2023-12-28 22:25 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-28 22:23 Brian Walden [this message]
-- strict thread matches above, loose matches on Subject: below --
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
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=202312282223.3BSMN2W8004242@cuzuco.com \
--to=tuhs@cuzuco.com \
--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).