public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Andrew Crabtree <andrewc@typhoon.rose.hp.com>
To: law@cygnus.com
Cc: egcs@cygnus.com
Subject: Re: fixincludes problem
Date: Thu, 15 Jan 1998 16:30:00 -0000	[thread overview]
Message-ID: <199801141810.AA034401445@typhoon.rose.hp.com> (raw)
In-Reply-To: <9902.884762827@hurl.cygnus.com>

> The 'fixed' version
>   > is pretty ugly though.  It repeats stuff.
> Weird.  I wonder if the djgpp version already had one of the #ifdef/#endif
> pairs -- else something in fixincludes or sed has gone nuts.
This seems likely.  The original header file I put in /usr/local/lib/gcc....
did not have any #if __cplus_plus around the struct expection.  But
I do build snapshots fairly regularly so its likely that math.h had 
already been fixed during a previous install.  At least, the version
currently in /usr has one set of #ifdefs around it.  

> This isn't done by fixincludes -- gcc uses its own stddef.h which bears
> no resemblance to any one provided by the system (this is true for a few
> files, including stddef.h, varargs.h, stdarg.h and a few others).
Oh - well this is my problem then.  After building libgcc
the make process crashes with

__gcc_bcmp
_varargs
__dummy
_eprintf
In file included from ./libgcc2.c:1393:
include/stdio.h:36: redefinition of `size_t'
include/stddef.h:168: `size_t' previously declared here

I just assumed it was the fixinclude's screwing things up.  Does gcc
intend that its newly supplied copy of stddef.h be used always 
by the resulting cross-compiler?  DJs stddef.h is very specific to it, 
and cannot be replaced by a generic one.  Will setting fixincludes=Makefile.in
disable this version of stddef.h from being used?  Or alternatively, can
I just modify the copy of stddef that will be used to support the DJ 
specific stuff?  Right now, I just copy the original DJ supplied stddef.h
into the build directory and restart things.

Thanks for the help

Andy

--
_______       ___________________________________________________________
           /                       	                  Andrew Crabtree 
          /                          	      Workgroup Networks Division 
         ____       ___  /                                Hewlett-Packard 
        /     /    /    /   		                    Roseville, CA 
     __/   __/    _____/                                     916/785-1675
                 /                           andrewc@rosemail.rose.hp.com
___________   __/   _____________________________________________________


  reply	other threads:[~1998-01-15 16:30 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1998-01-09 16:41 Andrew Crabtree
1998-01-10 22:02 ` Jeffrey A Law
1998-01-10 23:23   ` Andrew Crabtree
1998-01-12 11:39     ` Jeffrey A Law
1998-01-12 20:31       ` Andrew Crabtree
1998-01-12 22:13         ` Jeffrey A Law
1998-01-13 18:59           ` Andrew Crabtree
1998-01-14  4:17             ` Jeffrey A Law
1998-01-15 16:30               ` Andrew Crabtree [this message]
1998-01-14 23:17                 ` Jeffrey A Law

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=199801141810.AA034401445@typhoon.rose.hp.com \
    --to=andrewc@typhoon.rose.hp.com \
    --cc=egcs@cygnus.com \
    --cc=law@cygnus.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).