[SOLVED] Building Lazarus 2.0.12 with FreePascal 3.2.2 fails under OpenBSD

[TCH]

After installing FPC 3.2.2 (with sources) i try to gmake clean bigide and it crashes half the way

Code: [Select]

(3104) Compiling iphttpbroker.pas
Fatal: (10022) Can't find unit cNetDB used by netdb
Fatal: (1018) Compilation aborted
gmake[2]: *** [Makefile:3234: turbopoweripro.ppu] Error 1
gmake[2]: Leaving directory '/tmp/lazarus/components/turbopower_ipro'
gmake[1]: *** [Makefile:1788: bigide] Error 2
gmake[1]: Leaving directory '/tmp/lazarus/components'
gmake: *** [Makefile:3673: bigidecomponents] Error 2It's OpenBSD 6.8 AMD64.

Before this, i could compile Lazarus 2.0.10 with FreePascal 3.2.0 and everything worked. I did not change anything in the system, aside from FreePascal and Lazarus.

[DonAlfredo]

This might be a regression. I encountered the same problem. It is solved by using the included patch.

[TCH]

Thanks for the help and the patch. Now i know where to look next time if i encounter a similar error. (BTW, NetBSD is still missing from that list, or is that unsupported?)

[marcov]

In general unit are often only enabled for the platforms they are validated for. This is often a problem with *BSD.

[TCH]

Would not be better to enable for all and let the problems happen with the unit itself on the specific platforms? At least then it will be tested and hopefully fixed.

[marcov]

Would not be better to enable for all and let the problems happen with the unit itself on the specific platforms? At least then it will be tested and hopefully fixed.

But it is not a nice thing to hear that some unit that has been enabled for project X for half a decade turns out to not even work superficially. That makes platform status quite convoluted.

Note that this is not a general rule, it depends on the assessment of whoever did this. Resolver is a sensitive part, security wise, that might have factored in to it.

If you have tested it somewhat, just file a change request bug to enable it for the tested targets and packages.

[TCH]

I did not tested that particular unit, it was just missing during the installation, preventing me to update to the latest FPC and Lazarus. I did not use it with my previous setup either, but it was not missing during the install.

[marcov]

Maybe something network related was switched from netdb to cnetdb.