From: Nacho de los RÃÂos Tormo <irios@proin.es>
To: Ben Elliston <bje@redhat.com>
Cc: sourcenav@sources.redhat.com
Subject: Re:include file problems
Date: Wed, 29 Nov 2000 06:53:00 -0000 [thread overview]
Message-ID: <00112915522100.01532@irios> (raw)
In-Reply-To: <Pine.LNX.4.30.0011292313170.20902-100000@moshpit.cygnus.com>
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 503 bytes --]
I am AWFULLY sorry; this was all my fault. ... I tried to compile the file
from the command line and got the same errors. I tried gcc -E to do just the
preprocessing, and the declaration was there OK. I checked the code, and
there it was, glaring:
struct timeval system_time;
...
gettimeofday(&timeval, 0);
...
&timeval????? SHAME on me! I'll try to get smarter ...
Thanks again.
Nacho de los RÃos Tormo
Procedimientos Integrados S.L.
Sevillanos, 67
28609 Sevilla la Nueva, Madrid
SPAIN
next parent reply other threads:[~2000-11-29 6:53 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <Pine.LNX.4.30.0011292313170.20902-100000@moshpit.cygnus.com>
2000-11-29 6:53 ` Nacho de los RÃos Tormo [this message]
2000-11-28 9:52 Nacho de los RÃos Tormo
2000-11-28 10:14 ` Mo DeJong
2000-11-29 2:41 ` Nacho de los RÃos Tormo
2000-11-29 4:02 ` Nacho de los RÃos Tormo
2000-11-28 13:42 ` Ben Elliston
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=00112915522100.01532@irios \
--to=irios@proin.es \
--cc=bje@redhat.com \
--cc=sourcenav@sources.redhat.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 read-only IMAP folder(s) and NNTP newsgroup(s).