Re: glibc-2.3.3-51 breaks m4

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Steve G wrote:

> The patch is trivial. I just wanted to know which way this should be fixed. Do
> you want to leave glibc in this form or do you want me to file this in bugzilla
> with m4's patch?

glibc-2.3.3-53 (when released) will have the __P macro in the form m4
and other packages expects it.  glibc itself will simply not use the
macro anymore, at all, so it doesn't matter the optimizations we
introduced through __P are not present.  No need to file any bugs
related to this.

- --
â Ulrich Drepper â Red Hat, Inc. â 444 Castro St â Mountain View, CA â
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.6 (GNU/Linux)

iD8DBQFBR6m22ijCOnn/RHQRAge8AJ47VzRIY++2k9LXDzWuka2IQWdwaQCfWzdj
2Z2USg50OdXY9GQeFZ6bAhA=
=JvUf
-----END PGP SIGNATURE-----



[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Index of Archives]     [Fedora Announce]     [Fedora Kernel]     [Fedora Testing]     [Fedora Formulas]     [Fedora PHP Devel]     [Kernel Development]     [Fedora Legacy]     [Fedora Maintainers]     [Fedora Desktop]     [PAM]     [Red Hat Development]     [Gimp]     [Yosemite News]
  Powered by Linux