Linking error in qgspdalprovider

[meerfrau]

What is the bug or the crash?

/usr/bin/ld: CMakeFiles/provider_pdal.dir/qgspdalprovider.cpp.o: in function `QgsPdalProvider::loadIndex()':
qgspdalprovider.cpp:(.text+0xd90): undefined reference to `QgsCopcPointCloudIndex::QgsCopcPointCloudIndex()'
collect2: Fehler: ld gab 1 als Ende-Status zurück
make[2]: *** [src/providers/pdal/CMakeFiles/provider_pdal.dir/build.make:192: output/lib/qgis/plugins/libprovider_pdal.so] Fehler 1
make[1]: *** [CMakeFiles/Makefile2:5207: src/providers/pdal/CMakeFiles/provider_pdal.dir/all] Fehler 2

Using -DWITH_INTERNAL_LAZPERF=FALSE as suggested in #48374 leads to

./QGIS/external/untwine/bu/CopcSupport.cpp: In Elementfunktion »void untwine::bu::CopcSupport::addEbFields()«:
./QGIS/external/untwine/bu/CopcSupport.cpp:128:29: Fehler: keine passende Funktion für Aufruf von »lazperf::eb_vlr::addField(lazperf::eb_vlr::ebfield&)«
  128 |             m_ebVlr.addField(f);
      |             ~~~~~~~~~~~~~~~~^~~
In Datei, eingebunden von ./QGIS/external/untwine/bu/CopcSupport.hpp:22,
                 von ./QGIS/external/untwine/bu/CopcSupport.cpp:16:
/usr/include/lazperf/vlr.hpp:159:10: Anmerkung: Kandidat: »void lazperf::eb_vlr::addField()«
  159 |     void addField();
      |          ^~~~~~~~
/usr/include/lazperf/vlr.hpp:159:10: Anmerkung:   Kandidat erwartet 0 Argumente, 1 angegeben

PDAL version: 2.5.5

Steps to reproduce the issue

cmake --build .

Versions

git master

Supported QGIS version

• I'm running a supported QGIS version according to the roadmap.

New profile

• I tried with a new QGIS profile

Additional context

No response

[uclaros]

Is this a duplicate of #48374 @meerfrau? Do you get an error when building with -DWITH_INTERNAL_LAZPERF=TRUE?

[alexbruy]

Is this still an issue?

[github-actions]

The QGIS project highly values your report and would love to see it addressed. However, this issue has been left in feedback mode for the last 14 days and is being automatically marked as "stale".
If you would like to continue with this issue, please provide any missing information or answer any open questions. If you could resolve the issue yourself meanwhile, please leave a note for future readers with the same problem and close the issue.
In case you should have any uncertainty, please leave a comment and we will be happy to help you proceed with this issue.
If there is no further activity on this issue, it will be closed in a week.

[github-actions]

While we hate to see this happen, this issue has been automatically closed because it has not had any activity in the last 42 days despite being marked as feedback. If this issue should be reconsidered, please follow the guidelines in the previous comment and reopen this issue.
Or, if you have any further questions, there are also further support channels that can help you.