search

amagnasco / xwpe

Upload of an abandoned ncurses-based programming environment
http://www.identicalsoftware.com/xwpe/
GNU General Public License v2.0
31 stars 7 forks source link

configure.in (using autoreconf) seems to not work properly #52

Closed gbonnema closed 7 years ago

gbonnema commented 7 years ago

Hi Alessandro,

Working with the original configure files and Makefile.in is a struggle. Wanting to compare how it should be and what I am changing, I checked out experiemental without changes to configuration, and I can just compile. No problems.

However.

As soon as I do the sequence autoreconf --install -vv followed by ./configure I get errors. The base of the problem is that the original configure.in (which autoreconf uses as input) does not result in the correct defines. For instance, I have X installed, but after autoreconf, configure concludes that I have no X configured. Also, I have /usr/include/string.h containing strstr, but configure concludes I don't have strstr, so it defines it's own prototype for strstr, which ofcourse leads to errors, because the prototypes don't match.

I am now working on why the detection of features does not work correctly. My suspicion is that the current, newer versions of autotools, treat some of the code differently in some way. This might cause the detection of features to be erronous.

Could you please do the the same experiment and check whether it detects the environmental features properly? I would be very grateful. If the problems are repeatable, I should really try to improve the current configure.in. I would really appreciate your input.

The steps to reproduce are as follows:

  1. checkout a clean experimental branch
  2. run ./configure
  3. run make
  4. Check that everything compiles error free and xwpe is created. Also remark the defines in the compile statement for comparison with the next part
  1. checkout a clean experimental branch
  2. run autoreconf --install -vv
  3. Check no errors were found in the output the verbose options return
  4. run ./configure
  5. Check the output of make. It should contain errors. Also, compare the defines in the compile statements. Lots of features seem to be absent now.

Kind regards, Guus.

gbonnema commented 7 years ago

I have created a branch with new configure.ac and Makefile.am where this is no problem any more. Although I did not do a pull request yet, I will as soon as I have checked all the defines hidden in configuration and out. I will leave the issue open, and close it as soon as we have the new configuration files implemented and tested.

gbonnema commented 7 years ago

issue was solved in the autotools modification. Closing issue.