freadseek.c:69:3: error: #error "Please port gnulib freadseek.c to your platform! Look at the definition of getc, getc_unlocked on your system, then report this to bug-gnulib."

2024-06-21 Thread René Nyffenegger

I am trying to compile m4 2.0, and execute the following sequence:

./bootstrap
./configure
make

After a while, the processing stops with the error message

freadseek.c:69:3: error: #error "Please port gnulib freadseek.c to your 
platform! Look at the definition of getc, getc_unlocked on your system, 
then report this to bug-gnulib."


I've experienced this in Debian 11 and assume (but don't know) that this 
is such a standard environment that I don't need to port this source 
file (and if, I would have absolutely no clue what this file is supposed 
to do), but that something else is not set up correctly.


Unfortunately, I have no idea where I have to start investigatin and 
appreciate any pointer into the right direction.


Rene





Re: freadseek.c:69:3: error: #error "Please port gnulib freadseek.c to your platform! Look at the definition of getc, getc_unlocked on your system, then report this to bug-gnulib."

2024-06-21 Thread Collin Funk
Hi René,

René Nyffenegger wrote:
> I am trying to compile m4 2.0, and execute the following sequence:

Are you trying to build branch-2.0 from the m4 git repository?

If so, that branch hasn't been updated in 7 years. Perhaps one of the
changes made since then is required for your system [1] [2]. If that
is the case branch-1.4 should build.

Collin

[1] https://lists.gnu.org/r/bug-gnulib/2018-03/msg2.html
[2] https://lists.gnu.org/r/emacs-devel/2018-03/msg00300.html



Re: freadseek.c:69:3: error: #error "Please port gnulib freadseek.c to your platform! Look at the definition of getc, getc_unlocked on your system, then report this to bug-gnulib."

2024-06-21 Thread René Nyffenegger



Are you trying to build branch-2.0 from the m4 git repository?


Yes, that's what I tried. I tried to compile it because I hoped to 
benefit from the improved regular expression support which I believed 
was promised for 2.0 - and I wanted to verify if this is already in the 
code.