Mailing-List: contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm
Sender: cygwin-owner AT sourceware DOT cygnus DOT com
Delivered-To: mailing list cygwin AT sourceware DOT cygnus DOT com
From: "David J. Fiddes" <D DOT J AT fiddes DOT surfaid DOT org>
To: "Cygwin" <cygwin AT sourceware DOT cygnus DOT com>
Subject: FW: seeing limits.h from newlib  (fwd)
Date: Mon, 29 Mar 1999 15:57:56 +0100
Message-ID: <000601be79f4$8777a960$2a84c389@escom.fiddes-enterprises.com>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook 8.5, Build 4.71.2173.0
X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3110.3
Importance: Normal

Hi,

Anyone have any idea how Cygwin does this?

---------- Forwarded message ----------
Date: Sun, 28 Mar 1999 01:24:25 -0700
From: Jeffrey A Law <law AT upchuck DOT cygnus DOT com>
Reply-To: law AT cygnus DOT com
To: joel AT OARcorp DOT com
Cc: egcs AT egcs DOT cygnus DOT com
Subject: Re: seeing limits.h from newlib


  In message <Pine DOT LNX DOT 3 DOT 96 DOT 990209072946 DOT 6411C-100000 AT oar3remote>you write:
  >
  > Hi,
  >
  > The system limits.h for RTEMS is included with newlib.  There is an
  > ordering problem on the build that requires a manual installation of
this
  > file before gcc is built.  If you do not do this, then the limits.h
  > generated by gcc does not include the system's limits.h.  The
Makefile.in
  > stanza in question is:
  >
  > # Build the version of limits.h that we will install.
  > xlimits.h: glimits.h limitx.h limity.h
  >         if $(LIMITS_H_TEST) ; then \
  >           cat $(srcdir)/limitx.h $(srcdir)/glimits.h $(srcdir)/limity.h
>
  > tmp-xlimits.h; \
  >         else \
  >           cat $(srcdir)/glimits.h > tmp-xlimits.h; \
  >         fi
  >         mv tmp-xlimits.h xlimits.h
  >
  > I would like to come up with a way to avoid this ordering problem.  It
  > trips every RTEMS user who tries to build the toolset without using my
  > script.  If you simply following the standard "configure/make"
  > instructions, then it won't work because of this wart.  Here are my
ideas:
  >
So how does cygwin deal with this since I believe it has the same problem?

I'd bet it is similar to option #1 since the point of adding LIMITS_H_TEST
was
to help deal with some of these kinds of issues.

jeff



--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe AT sourceware DOT cygnus DOT com