From: Mark Frey <markfrey@sympatico.ca>
To: Martchukov Anton <vhlist@yandex.ru>
Cc: linux-diald <linux-diald@vger.kernel.org>
Subject: Re: compilation problem
Date: Sat, 30 Aug 2003 08:30:17 -0400 [thread overview]
Message-ID: <3F5098D9.60100@sympatico.ca> (raw)
In-Reply-To: <20030830142814.790ffffb.vhlist@yandex.ru>
[-- Attachment #1: Type: text/plain, Size: 945 bytes --]
Hi VH,
I've attached a patch that Duncan Haldane posted to this list Jan 12,
2002. diald.h is not including the correct file with the CLK_TCK
definintion. Patch your diald.h and try compiling again.
Mark.
Martchukov Anton wrote:
> Hello, here is output of make
>
> gcc -g -O2 -DHAVE_CONFIG_H -I.
> -DDIALD_CONFIG_FILE=\"/usr/local/etc/diald.conf\"
> -DDIALD_DEFS_FILE=\"/usr/local/lib/diald/diald.defs\"
> -DRUN_PREFIX=\"/usr/local/var/run\" -c -o diald.o diald.c
> diald.c: In function `main':
> diald.c:192: `CLK_TCK' undeclared (first use in this function)
> diald.c:192: (Each undeclared identifier is reported only once
> diald.c:192: for each function it appears in.)
> make: *** [diald.o] Error 1
>
> diald version 1.0
> gcc version 2.95.3 20010315
> linux kernel 2.4.20 Vector Linux 2.0 (Slackware 8.1)
>
> Could anybody help me to compile diald?
> Maybe there is a package for Slackware, isn't it?
>
> Please help.
>
[-- Attachment #2: diald-1.0.patch --]
[-- Type: text/plain, Size: 388 bytes --]
diff -uNr diald-1.0/diald.h diald-1.0-patched/diald.h
--- diald-1.0/diald.h Sat Jun 16 12:01:25 2001
+++ diald-1.0-patched/diald.h Fri Sep 7 02:57:56 2001
@@ -29,6 +29,11 @@
#include <signal.h>
#if HAVE_SYS_TIME_H
# include <sys/time.h>
+#if TIME_WITH_SYS_TIME
+# include <time.h>
+#endif
+#else
+# include <time.h>
#endif
#ifdef _POSIX_PRIORITY_SCHEDULING
# include <sched.h>
prev parent reply other threads:[~2003-08-30 12:30 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-30 10:28 compilation problem Martchukov Anton
2003-08-30 12:30 ` Mark Frey [this message]
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=3F5098D9.60100@sympatico.ca \
--to=markfrey@sympatico.ca \
--cc=linux-diald@vger.kernel.org \
--cc=vhlist@yandex.ru \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).