From: jjohnstn <jjohnstn@redhat.com>
To: Corinna Vinschen <vinschen@redhat.com>
Cc: gdb-patches@sources.redhat.com, <newlib@sources.redhat.com>,
<binutils@sources.redhat.com>
Subject: Re: [RFA]: Top-level configure patch to build Cygwin native newlib
Date: Wed, 16 Jun 2004 17:47:00 -0000 [thread overview]
Message-ID: <Pine.LNX.4.44.0406161342140.7927-100000@tooth.toronto.redhat.com> (raw)
In-Reply-To: <20040616165152.GJ1365@cygbert.vinschen.de>
On Wed, 16 Jun 2004, Corinna Vinschen wrote:
> On Jun 16 12:23, jjohnstn wrote:
> > Hi Corinna,
> >
> > I have no problem with the patch, but would it be possible to add
> > to the patch to issue a warning message to the user to tell them that
> > winsup is missing?
>
> No, that shouldn't be a problem. In that case the
>
> test -d winsup && skipdirs=`echo " ${skipdirs} " | sed -e 's/ target-newlib / /'`
>
> would become a
>
> if test -d winsup
> then
> skipdirs=`echo " ${skipdirs} " | sed -e 's/ target-newlib / /'`
> else
> echo "Warning: winsup is missing so newlib can't be build."
> fi
>
Thanks, just change "build" to "built".
>
> If that's fine with everyone...
>
> Erm... btw., should I Cc the gcc-patches list, perhaps?
>
It would be a good idea. IIRC, most of the top-level files are
copied by sources from gcc. Did I get that correct, Chris?
>
> Corinna
>
>
>
> >
> > -- Jeff J.
> >
> > On Wed, 16 Jun 2004, Corinna Vinschen wrote:
> >
> > > Hi,
> > >
> > > perhaps I could just apply the patch but I would like to ask people first
> > > if there something is in the way of applying the below patch.
> > >
> > > The idea is the following: If you have a source tree containing the newlib
> > > subdir but the source tree does not contain the winsup subdir, then it's
> > > impossible to build a native Cygwin newlib. The reason is, that building a
> > > Cygwin native newlib requires a bunch of header files from the winsup/cygwin
> > > directory. If the winsup directory is missing, the build will break when
> > > trying to build newlib.
> > >
> > > For that reason, the below patch to configure.in checks if the winsup
> > > directory is available and removes newlib from the target_configdirs
> > > if winsup is missing.
> > >
> > > Is that ok to apply?
> > >
> > >
> > > Corinna
> > >
> > >
> > > * configure.in: Don't build Cygwin native newlib if winsup
> > > directory is missing.
> > > * configure: Regenerate.
> > >
> > >
> > > Index: configure.in
> > > ===================================================================
> > > RCS file: /cvs/cvsfiles/gnupro/configure.in,v
> > > retrieving revision 1.32
> > > diff -p -u -r1.32 configure.in
> > > --- configure.in 9 Jun 2004 17:31:01 -0000 1.32
> > > +++ configure.in 16 Jun 2004 15:19:40 -0000
> > > @@ -548,8 +548,8 @@ case "${target}" in
> > > *-*-cygwin*)
> > > target_configdirs="$target_configdirs target-libtermcap target-winsup"
> > > noconfigdirs="$noconfigdirs target-gperf target-libgloss ${libgcj}"
> > > - # always build newlib.
> > > - skipdirs=`echo " ${skipdirs} " | sed -e 's/ target-newlib / /'`
> > > + # always build newlib if winsup directory is present.
> > > + test -d winsup && skipdirs=`echo " ${skipdirs} " | sed -e 's/ target-newlib / /'`
> > >
> > > # Can't build gdb for Cygwin if not native.
> > > case "${host}" in
> > >
> > >
> > >
>
>
next prev parent reply other threads:[~2004-06-16 17:47 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-16 15:56 Corinna Vinschen
2004-06-16 16:23 ` jjohnstn
2004-06-16 16:52 ` Corinna Vinschen
2004-06-16 17:47 ` jjohnstn [this message]
2004-06-16 19:11 ` Alexandre Oliva
2004-06-16 19:19 ` DJ Delorie
2004-06-17 7:57 ` Corinna Vinschen
2004-06-17 19:55 ` DJ Delorie
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=Pine.LNX.4.44.0406161342140.7927-100000@tooth.toronto.redhat.com \
--to=jjohnstn@redhat.com \
--cc=binutils@sources.redhat.com \
--cc=gdb-patches@sources.redhat.com \
--cc=newlib@sources.redhat.com \
--cc=vinschen@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