Hi Martin,

On Thu Oct 2, 2025 at 8:55 PM CEST, Martin Reindl wrote:
> Am 21.09.25 um 12:12 schrieb Marco van Hulten:
>> On Sat, 20 Sep 2025 22:14:14 +0200 Martin Reindl wrote:
>
> Hi Marco,
>
>> Does that mean the core CVS tree, as opposed to ports and packages?
>
> Yes, is there something special with ncview which makes it incompatible
> with clang?

I don't know.

>> Right now it works with 8.4.0 that is in the ports tree.  I understand
>> you'd prefer it to work with /usr/bin/cc.
>> 
>> There are many (types of) errors and warnings that that compiler
>> throws.  I appears to me that the code could use improvements.  I have
>> not been able to reach the author and I have to consider if I have
>> sufficient time and skills to patch it up.
> checking whether we are using the GNU C compiler... (cached) yes
>
> This line from the configure script puzzles me, when using clang. There
> seem to be more problems around with the configure script.
>
> We can ask for OKs to get ncview imported with ports-gcc set, but it
> might be better to fix configure first.

I have a working port that I can use.  Fixing the most important things
first, be it in configure or the program code, would be nice, but I have
little time for probably at least the next two months.  I would probably
look in ernst at fixing this up in 2026 Q1.  I have not a strong opinion
about having soon a ncview package with more buggy configure and code
than it could be in months from now.  :/

For me the incentive to improve it would be the same, regardless of if
there is already a package or not.

 Marco