intro:
Having to patch a package to be installed with nptl I've tried this
function (yes now I know it's wrong patch conditionally a package if not
needed).
Only few days later a user complain that the check failed (seem to
remember on amd64) .
what we have:
At the moment have_NPTL is defined in eclass/eutils.eclass, it compile a
small test program to check if glibc have nptl support.
what I've seen used in at least one other place (modified to be a
candidate substitute):
<code>
case $(getconf GNU_LIBPTHREAD_VERSION | tr abcdefghijklmnopqrstuvwxyz
ABCDEFGHIJKLMNOPQRSTUVWXYZ) in
NPTL* )
return 0
;;
LINUXTHREADS* )
return 1
;;
* )
eerror "unknown libpthread implementation"
return 1
;;
esac
</code>
there are drawbacks on the use of getconfig (that come with glibc) ?
Maybe it's not supported from *libc ?
This is also important to know (for me ;) because an important package
is going to make this check in it' "configure" and having it break on
certain gentoo supported ARCHs may be tedious.
any hints and/or feedback welcome
--
gentoo-dev@gentoo.org mailing list
Having to patch a package to be installed with nptl I've tried this
function (yes now I know it's wrong patch conditionally a package if not
needed).
Only few days later a user complain that the check failed (seem to
remember on amd64) .
what we have:
At the moment have_NPTL is defined in eclass/eutils.eclass, it compile a
small test program to check if glibc have nptl support.
what I've seen used in at least one other place (modified to be a
candidate substitute):
<code>
case $(getconf GNU_LIBPTHREAD_VERSION | tr abcdefghijklmnopqrstuvwxyz
ABCDEFGHIJKLMNOPQRSTUVWXYZ) in
NPTL* )
return 0
;;
LINUXTHREADS* )
return 1
;;
* )
eerror "unknown libpthread implementation"
return 1
;;
esac
</code>
there are drawbacks on the use of getconfig (that come with glibc) ?
Maybe it's not supported from *libc ?
This is also important to know (for me ;) because an important package
is going to make this check in it' "configure" and having it break on
certain gentoo supported ARCHs may be tedious.
any hints and/or feedback welcome
--
gentoo-dev@gentoo.org mailing list