Re: [PATCH 4/6] newlib: drop libtool support
Mike Frysinger <[email protected]>
| Newsgroups | gmane.comp.lib.newlib |
|---|---|
| Message-ID | <YgMIwEPk3jA5ywMv@vapier> |
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
signature.asc
(application/pgp-signature, 833 B)
-----BEGIN PGP SIGNATURE----- iQIzBAABCAAdFiEEuQK1JxMl+JKsJRrUQWM7n+g39YEFAmIDCMAACgkQQWM7n+g3 9YFQFA//X94VopIN/pqavIPxbg4J1U3zXcqPN7POXuh19eofVbwR/wuPlpl+T7bO FpuFv4zXxgycQv6BDvMXyJu+sG4fX3KYnm2zxr8fGhVuIepVCnKBz/+OoFfMpGOk H0FaZn/MR1ExbqLpu9uUWTjnFnHJk94jpRTlr7zBOBsQ/JOjiKoax1rDscNIKqD2 vCXTC1y8jfw03tsBDpeGDfi7wRm01xuaF5s+iGRx7EYwViA60QHkH16Gu/mmAfWv g6oSy32BTSaYXRthZzcUOeVR+buHi0dLVEBmF2HL2H3ST47qLxmyErO7jNpMCssR SUE7RmFn0tOmqsUX6wZ7o/GqCyLMpOqIKTD+8FTTiZG84VJar52bFHEuyYwvUdnp lCCbVGgU8FmvjyVDxr3XE5JukDISrA1ULVAbtu+3E7wzmpEfH14idbZT41qZHYNR 54/GFfILn2MLgs0d0IGUfH+SW2rBv+KCyyqxSXkur14ZZELdwzWwjRvwZFgjHxnl Sa+pD40/7QUKQKA74f7oUjiKxSQcgV2Ftr2IBUAyPi9Kv1+SP6PKC4DZ+Hyv9BuP I3TMy04tYcocpuxyClHNgGKDdRR/l34vsuMCUQE/OWweot5i8s4uzpEBDmjHa9/t HZG6oBCX7BzPbRbt3fFlfXewuAxf38Nfueiv4cY2Q5hG4TLKdLA= =42eQ -----END PGP SIGNATURE-----