public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: y2bismil@engmail.uwaterloo.ca
To: y2bismil@engmail.uwaterloo.ca
Cc: gcc@gcc.gnu.org
Subject: Re: caddr_t undefined
Date: Tue, 07 Oct 2003 18:35:00 -0000	[thread overview]
Message-ID: <1065551729.3f830771e1682@www.nexusmail.uwaterloo.ca> (raw)
In-Reply-To: <1065550201.3f830179b2467@www.nexusmail.uwaterloo.ca>

Quoting y2bismil@engmail.uwaterloo.ca:

> Hi all,
> 
> I'm trying to compile a program, and i'm getting the error of caddr_t being
> undefined.  I know its just a char* or void*, but I'm thinking this is an
> error
> I should not have to work around.
> 
> The error actually occurs in: /usr/include/cygwin/if.h
> 
> But, looking at if.h, I see it includes sys/types.h.  This is turn includes
> a
> definition for caddr_t:  typedef	char *	caddr_t;
> 
> Anyone got any ideas?  I'm using the Cygwin environment if that's an issue
> 
> Yamin
> 

Okay, 
I think this is something to do with the header search order.  It does not look
like sys/types is being included.  I think something in the ming directories is
being included.  Anyone know how to add include directories to be searched AFTER
the standard directories are searched?

Yamin



----------------------------------------
This mail sent through www.mywaterloo.ca

  reply	other threads:[~2003-10-07 18:35 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-10-07 16:34 Joining GCC for version 3.4 Tal Agmon
2003-10-07 18:10 ` caddr_t undefined y2bismil
2003-10-07 18:35   ` y2bismil [this message]
2003-10-07 21:19     ` Phil Edwards
2003-10-07 18:16 ` Joining GCC for version 3.4 Daniel Jacobowitz
2003-10-07 19:17   ` Joe Buck

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=1065551729.3f830771e1682@www.nexusmail.uwaterloo.ca \
    --to=y2bismil@engmail.uwaterloo.ca \
    --cc=gcc@gcc.gnu.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 read-only IMAP folder(s) and NNTP newsgroup(s).