From: Corinna Vinschen <vinschen@redhat.com>
To: newlib@sourceware.org
Subject: Re: [PATCH 4/6] newlib: drop libtool support
Date: Wed, 9 Feb 2022 11:54:55 +0100 [thread overview]
Message-ID: <YgOdfy15NVRA4Ay5@calimero.vinschen.de> (raw)
In-Reply-To: <YgMIwEPk3jA5ywMv@vapier>
On Feb 8 19:20, Mike Frysinger wrote:
> On 08 Feb 2022 10:47, Corinna Vinschen wrote:
> > On Feb 7 20:57, Mike Frysinger wrote:
> > > --- a/newlib/libm/configure.ac
> > > +++ b/newlib/libm/configure.ac
> > >
> > > - LIBM_MACHINE_DIR=machine/${libm_machine_dir}
> > > - if test "${use_libtool}" = "yes"; then
> > > - LIBM_MACHINE_LIB=${LIBM_MACHINE_DIR}/lib${libm_machine_dir}.${aext}
> > > - else
> > > - LIBM_MACHINE_LIB=${LIBM_MACHINE_DIR}/lib.${aext}
> > > - fi
> > > + LIBM_MACHINE_DIR=machine/${libm_machine_dir
> > ^^^^^^^^^^^^^^^^^^^
> > oops?
>
> yeah ... i actually remember making that mistake, and i thought i hit "undo"
> in my editor, but i guess i didn't hit it enough times.
>
> i was holding off on running my full local build suite (i've got 24 arches
> now) until after i got a favorable signal on the series.
> -mike
The series looks good otherwise.
Corinna
next prev parent reply other threads:[~2022-02-09 10:54 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-07 9:27 can i delete libtool / shared library support ? Mike Frysinger
2022-02-07 10:30 ` Mike Frysinger
2022-02-07 11:48 ` Corinna Vinschen
2022-02-07 19:30 ` Jeff Johnston
2022-02-08 1:57 ` [PATCH 0/6] delete i?86-pc-linux-gnu & libtool support Mike Frysinger
2022-02-08 1:57 ` [PATCH 1/6] newlib: drop i?86-pc-linux-* target support Mike Frysinger
2022-02-08 1:57 ` [PATCH 2/6] newlib: punt sys/linux support Mike Frysinger
2022-02-08 1:57 ` [PATCH 3/6] newlib: drop unused iconvdata Mike Frysinger
2022-02-08 4:55 ` Joel Sherrill
2022-02-08 1:57 ` [PATCH 4/6] newlib: drop libtool support Mike Frysinger
2022-02-08 9:47 ` Corinna Vinschen
2022-02-09 0:20 ` Mike Frysinger
2022-02-09 10:54 ` Corinna Vinschen [this message]
2022-02-09 8:41 ` Brian Inglis
2022-02-09 10:55 ` Corinna Vinschen
2022-02-08 1:57 ` [PATCH 5/6] newlib: drop support for $aext Mike Frysinger
2022-02-08 1:57 ` [PATCH 6/6] newlib: drop support for $oext Mike Frysinger
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=YgOdfy15NVRA4Ay5@calimero.vinschen.de \
--to=vinschen@redhat.com \
--cc=newlib@sourceware.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).