AC_CHECK_FUNC vs. function renaming? (curl on tru64/osf1, threads)

2021-07-06 Thread Jay K
Hi autoconf folks. I'm trying to build Curl on Tru64 / OSF1.  I think that will help git be useful there (I have git, but not git clone). Curl configure has this thing where it looks for a thread library. It tries to link to pthread_create: AC_CHECK_FUNC(pthread_create, [USE_THREADS_POSIX=1] )

Autoconf online tutorial

2021-07-06 Thread Anthony Scemama
Dear autoconf community, I am organizing an online "build system hackathon" for academic scientists on behalf of the TREX european center of excellence in high performance computing (https://trex-coe.eu) in November. We want our software developers to really understand how autotools work, instead o

Re: AC_CHECK_FUNC vs. function renaming? (curl on tru64/osf1, threads)

2021-07-06 Thread Paul Eggert
On 7/6/21 1:19 AM, Jay K wrote: My intuition would be more like:  #include  int main()  {  return (int)pthread_create;  } It should be easy to change curl's configure.ac to do that. But pthread_create is a bigger portability minefield than just that. See the Gnulib pthread modul

Re: Autoconf online tutorial

2021-07-06 Thread David A. Wheeler
> On Jul 6, 2021, at 9:39 AM, Anthony Scemama > wrote: > > Dear autoconf community, > I am organizing an online "build system hackathon" for academic scientists on > behalf of the TREX european center of excellence in high performance computing > (https://trex-coe.eu) in November. We want our

Re: Autoconf online tutorial

2021-07-06 Thread Anthony Scemama
David A. Wheeler writes: >> On Jul 6, 2021, at 9:39 AM, Anthony Scemama >> wrote: >> >> Dear autoconf community, >> I am organizing an online "build system hackathon" for academic scientists on >> behalf of the TREX european center of excellence in high performance >> computing >> (https://t

Re: AC_CHECK_FUNC vs. function renaming? (curl on tru64/osf1, threads)

2021-07-06 Thread Jay K
I mean, isn’t AC_CHECK_FUNC kinda wrong? In reality we have essentially pthread.h: #define pthread_create __pthread_create In ridiculous extreme we could have: stdio.h: #define fopen pthread_create AC_CHECK_FUNC or its users really should? include include “the” header, right? But, I don’t under

Re: AC_CHECK_FUNC vs. function renaming? (curl on tru64/osf1, threads)

2021-07-06 Thread Paul Eggert
On 7/6/21 11:32 AM, Jay K wrote: I mean, isn’t AC_CHECK_FUNC kinda wrong? No, it's working as documented. You just have an unusual situation with pthread_create. Again, please see Gnulib's treatment of pthread_create. Since we're talking about Tru64, this is of academic interest anyway. HP

Re: AC_CHECK_FUNC vs. function renaming? (curl on tru64/osf1, threads)

2021-07-06 Thread Jay K
But, isn't any function subject to arbitrary renaming by its "declaration"? And AC_CHECK_FUNC is probing kinda at the wrong level, or skipping a level? pragmas, defines, static inline, intrinsics, etc. It isn't specific to pthread_create. There is this repeating pattern, all these functions would

Re: AC_CHECK_FUNC vs. function renaming? (curl on tru64/osf1, threads)

2021-07-06 Thread Paul Eggert
On 7/6/21 2:25 PM, Jay K wrote: It isn't specific to pthread_create. Correct; other functions have the problem too and they also need workarounds. See Gnulib for more examples. Most functions are fine, though.