Re: Still some issues/warnings..

[Dr . Jürgen Sauermann]

    Hi Peter,
      
      thanks for sharing your .configur result. I had a closer look at
      your config log. Nothing critial, though.
      
      autoconf does a number of checks that frequently fail. For
      example, the 
      
    conftest.c:52:10: fatal error:
        'minix/config.h' file not found
    
    error will happen on almost all operating systems other than Minix
    (and therefore also
    on my Linux Mint). The config.log provides very valuable
    additional information when
    ./configure fails, but confuses more than it helps when ./configure
    succeeds. This
    type of errors is caused by autoconf itself (and also occurs
    on my Linux Mint).
    
    A whole lot of other errors in config.log are caused by
    incompatibilities between gcc
    and clang. These do not occur on my machine, but are also harmless.
    Your config.log
    has 4503 lines while mine has 2995 for the same source code. That is
    is 50% more
    and almost all are caused by gcc/clang incompatibilities.
    
    So, as far as I can see we have now fixed all issues caused by GNU
    APL itself and
    should look forward to the next bogus compiler warning from the gcc
    guys :-).
    
    Best Regards,
    Jürgen

On 10/20/22 7:06 PM, Peter Teeson wrote:

Thanks for finding & fixing the issues. Successful checkout, configure, and build on macOS Mojave 14.6.

The following does not seem to have affected my build.

However FYI attached are 2 files related to the 150 errors in the config.log:

(1) the config.log and (2) a list of the errors with line numbers

                   

On Oct 20, 2022, at 11:08 AM, Chris Moller <moller@mollerware.com> wrote:

Brings back unfond memories of decades ago of the significance of invisible leading tabs in Makefiles...

On 10/20/22 08:06, Dr. Jürgen Sauermann wrote:

Hi again,

I may have found the problem. I am so much used to nicely looking indentation that
my brain keeps refusing to remember the counter-intuitive fact that, in bash, blanks
before and after = make a (in this case) huge difference. To make things worse, this
happens in a conditional  and therefore only occurs on some systems and not on
others.

Fixed in SVN 1609.
 
Best Regards,
Jürgen

<OpenPGP_0xDA6C01938888083E.asc>