From: Nacho de los RÃÂos Tormo <irios@proin.es>
To: sourcenav@sources.redhat.com
Subject: Re:include file problems
Date: Tue, 28 Nov 2000 09:52:00 -0000 [thread overview]
Message-ID: <00112818511300.00635@irios> (raw)
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 1260 bytes --]
I am also having this problem on a SuSE 7.0 installation. For example:
I'm trying to call the library function:
gettimeofday(struct timeval* tv, struct timezone * tz).
According to man pages, I need
#include <sys/time.h> (which should expand to /usr/include/sys/time.h)
#include <unistd.h> (which should expand to /usr/include/unistd.h)
SNav is unable to find the correct files -- which are indeed there.
I have toyed with the project settings include tab, as well as with the build
settings. Depending on the combination, it either finds /usr/include/time.h
(wrong file) or /usr/include/sys/unistd.h (also wrong).
SNav only manages to find the correct files if I include them explicitly in
the project (which calls for a trip to the project editor and to have the
project reparsed). But these files themselves do include a variety of other
files, which in their turn call others.
Trying to manually include all the tree soon leads into confusion and
dispair. And this is just for gettimeofday()! The thought of throwing in some
threads and an ncurses interface sends shivers down my spine.
Any ideas on what is wrong?
--
Nacho de los RÃos Tormo
Procedimientos Integrados S.L.
Sevillanos, 67
28609 Sevilla la Nueva, Madrid
SPAIN
next reply other threads:[~2000-11-28 9:52 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-11-28 9:52 Nacho de los RÃos Tormo [this message]
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-29 4:10 ` include " Bruce Stephens
2000-11-28 13:42 ` Ben Elliston
[not found] <Pine.LNX.4.30.0011292313170.20902-100000@moshpit.cygnus.com>
2000-11-29 6:53 ` Nacho de los RÃos Tormo
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=00112818511300.00635@irios \
--to=irios@proin.es \
--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).