From: Rich Salz <rich.salz@gmail.com>
To: KenUnix <ken.unix.guy@gmail.com>
Cc: UNIX TUHS Group <tuhs@tuhs.org>
Subject: [TUHS] Re: Trying to compile cron
Date: Thu, 28 Dec 2023 17:44:58 -0500 [thread overview]
Message-ID: <CAFH29to0bokGHQ+CyiZyKxgAmU7aCcnmW5Om4g4Z3F3kLbBM1w@mail.gmail.com> (raw)
In-Reply-To: <CAJXSPs8ew3BaE+BkOVWsx7vdxyGgrtkkDbwYK9zvRwY74v78Yw@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1624 bytes --]
One thing that would INCREDIBLY help people trying to help you is find
where the symbol is used, look up the variable types in the function call,
and create a prototype. For example, both of these are valid xmalloc
instances:
char *xmalloc(int size);
char *xmalloc(int size, unsigned char fillvalue)
Seeing the use in the code you are trying to compile will help avoid wrong
answers.
People already likely gave you the answers, but a little leg work on your
own before posting will help.
On Thu, Dec 28, 2023 at 4:22 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: 2400 bytes --]
next prev parent reply other threads:[~2023-12-28 22:45 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 [this message]
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=CAFH29to0bokGHQ+CyiZyKxgAmU7aCcnmW5Om4g4Z3F3kLbBM1w@mail.gmail.com \
--to=rich.salz@gmail.com \
--cc=ken.unix.guy@gmail.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).