public inbox for sourcenav@sourceware.org
 help / color / mirror / Atom feed
From: Bruce Stephens <bruce.stephens@messagingdirect.com>
To: sourcenav@sources.redhat.com
Subject: Re: include file problems
Date: Wed, 29 Nov 2000 04:10:00 -0000	[thread overview]
Message-ID: <vbhf4rm11x.fsf@erwin.isode.com> (raw)
In-Reply-To: <00112913010300.01118@irios>

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 934 bytes --]

Nacho de los Ríos Tormo <irios@proin.es> writes:

[...]

> Dumb me! Why not add the whole /usr/include and all its
> subdirectories in one go with the project editor? .... Well, I've
> done so, so all involved files MUST now be included in the
> project. Still I get the same compilation errors:
> 	
> 	dos_in_lin.c: In function 'get_time_ms'
> 	dos_in_lin.c: 30: 'timeval' undeclared (first use in this function)
> 	....
> 	make: *** [dos_in_lin.o] Error 1
> 	+++ End +++

That's a compiler error: it's got nothing to do with Source Navigator.
SN doesn't tell the compiler what header files to use.  Something like
this ought to compile, regardless of what include files Source
Navigator finds:

#include <sys/time.h>
void
foo()
{
    struct timeval tv;
    struct timezone tz;
    gettimeofday(&tv, &tz);
}

-- 
Bruce Stephens			Bruce.Stephens@MessagingDirect.com
MessagingDirect(UK) Ltd		<URL: http://www.MessagingDirect.com/ >

  reply	other threads:[~2000-11-29  4:10 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
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-29  4:10       ` Bruce Stephens [this message]
2000-11-28 13:42 ` Ben Elliston
  -- strict thread matches above, loose matches on Subject: below --
2000-10-28 10:26 include " Merlyn Cousins
2000-10-28 13:22 ` Ian Roxborough
2000-10-28 14:32   ` Merlyn
2000-10-29 13:57 ` Ben Elliston
2000-10-29 17:26   ` Eray Ozkural (exa)

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=vbhf4rm11x.fsf@erwin.isode.com \
    --to=bruce.stephens@messagingdirect.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).