cmake issue with GLU on P.Pi bullseye and fltk-1.4

[imacarthur]

So I recently set up this Pi.4 with the new bullseye-based PiOS image, replacing the old buster-based version that I've been using (the R.Pi folks are more or less tracking debian now...)

Building fltk-1.4 on this machine, the cmake build claims I do not have GLU installed (I do, of course.) The autoconf build works just fine, however.

If I hand-edit the config.h created by cmake to enable GLU, that also works.

It seems the cmake is not looking in the right place.... or something, but I do not know what.

[Albrecht Schlosser]

Hard to say w/o such a system. I have a Pi.3 (IIRC) but I don't have the
same config and I can't remember to have setup CMake and tried to build
FLTK on it. I have a stock Debian 10 (Buster) VM though which I could
try. I could even update to Debian 11 (Bullseye), maybe.

Can you give some more details, which GL related packages you installed
and the output related to GL/GLU from CMake in a fresh build tree (i.e.
the first CMake run)?

FWIW, I believe installing 'freeglut3-dev' and/or some of the related
'mesa' packages could help, but of course I don't know about the
Bullseye constellation.

From my Linux Mint (based on Ubuntu based on Debian) I get:

$ apt list --installed | grep 'gl.*dev'

freeglut3-dev/focal,now 2.8.1-3 amd64 [installed]
libegl-dev/focal-updates,now 1.3.2-1~ubuntu0.20.04.1 amd64 [installed]
libegl1-mesa-dev/now 21.0.3-0ubuntu0.3~20.04.3 amd64
[installed,upgradable to: 21.0.3-0ubuntu0.3~20.04.5]
libgl-dev/focal-updates,now 1.3.2-1~ubuntu0.20.04.1 amd64 [installed]
libgl1-mesa-dev/now 21.0.3-0ubuntu0.3~20.04.3 amd64
[installed,upgradable to: 21.0.3-0ubuntu0.3~20.04.5]
libgles-dev/focal-updates,now 1.3.2-1~ubuntu0.20.04.1 amd64 [installed]
libgles2-mesa-dev/now 21.0.3-0ubuntu0.3~20.04.3 amd64
[installed,upgradable to: 21.0.3-0ubuntu0.3~20.04.5]
libglew-dev/focal,now 2.1.0-4 amd64 [installed]
libglib2.0-dev-bin/focal-updates,now 2.64.6-1~ubuntu20.04.4 amd64
[installed,automatic]
libglib2.0-dev/focal-updates,now 2.64.6-1~ubuntu20.04.4 amd64 [installed]
libglu1-mesa-dev/focal,now 9.0.1-1build1 amd64 [installed,automatic]
libglvnd-dev/focal-updates,now 1.3.2-1~ubuntu0.20.04.1 amd64 [installed]
libglx-dev/focal-updates,now 1.3.2-1~ubuntu0.20.04.1 amd64 [installed]
libopengl-dev/focal-updates,now 1.3.2-1~ubuntu0.20.04.1 amd64 [installed]
libqt5opengl5-dev/focal,now 5.12.8+dfsg-0ubuntu1 amd64 [installed,automatic]


I'd be interested in

(a) the CMake output before you change anything
(b) the GL related package list on your system (before changes as well)
(c) output if you install one or more packages from the above list (if
it fixes the issue)

This could help to find out where excatly "cmake is not looking in the
right place".

[imacarthur]

On Saturday, 18 December 2021 at 18:16:38 UTC Albrecht Schlosser wrote:

Hard to say w/o such a system. I have a Pi.3 (IIRC) but I don't have the
same config and I can't remember to have setup CMake and tried to build
FLTK on it. I have a stock Debian 10 (Buster) VM though which I could
try. I could even update to Debian 11 (Bullseye), maybe.

FWIW I've never seen this fail on a R.Pi before, with the older buster-based PiOS. Nor on my "real" PC's with Ubuntu...

 

Can you give some more details, which GL related packages you installed

I installed fltk after installing a load of other tools that had already pulled in many deps... so I did not explicitly install any GL dev packges.

But the GLU header is definitely there.

 

and the output related to GL/GLU from CMake in a fresh build tree (i.e.
the first CMake run)?

Well - that was interesting. I made a new clone, the cmake configure worked.

Went back to the "broken" tree, did a git pull, re-ran cmake - still broken.

So, made a new build-folder in the broken tree, set all the same options - works...

FWIW, I do not think I have added any new libs or packages...

BUT... I can not now reproduce the fail, except in the original build folder.... I might just bin that folder and carry on...

$ apt list --installed | grep 'gl.*dev'

libegl-dev/stable,now 1.3.2-1 armhf [installed,automatic]
libegl1-mesa-dev/stable,now 20.3.5-1+rpt3+rpi1 armhf [installed]
libgl-dev/stable,now 1.3.2-1 armhf [installed,automatic]
libgl1-mesa-dev/stable,now 20.3.5-1+rpt3+rpi1 armhf [installed,automatic]
libgles-dev/stable,now 1.3.2-1 armhf [installed,automatic]
libglew-dev/stable,now 2.1.0-4 armhf [installed]
libglib2.0-dev-bin/stable,now 2.66.8-1 armhf [installed,automatic]
libglib2.0-dev/stable,now 2.66.8-1 armhf [installed,automatic]
libglu1-mesa-dev/stable,now 9.0.1-1 armhf [installed,automatic]
libglvnd-dev/stable,now 1.3.2-1 armhf [installed,automatic]
libglx-dev/stable,now 1.3.2-1 armhf [installed,automatic]
libopengl-dev/stable,now 1.3.2-1 armhf [installed,automatic]
libxcb-glx0-dev/stable,now 1.14-3 armhf [installed]

 

I'd be interested in

(a) the CMake output before you change anything

zips attached.  [UPDATED: zips not attached - apparently zip files are disallowed...]

(b) the GL related package list on your system (before changes as well)

See above.

 

[Albrecht Schlosser]

On 12/19/21 6:34 PM imacarthur wrote:

On Saturday, 18 December 2021 at 18:16:38 UTC Albrecht Schlosser wrote:

Hard to say w/o such a system. I have a Pi.3 (IIRC) but I don't have the
same config and I can't remember to have setup CMake and tried to build
FLTK on it. I have a stock Debian 10 (Buster) VM though which I could
try. I could even update to Debian 11 (Bullseye), maybe.

FWIW I've never seen this fail on a R.Pi before, with the older buster-based PiOS. Nor on my "real" PC's with Ubuntu...

 

Can you give some more details, which GL related packages you installed

I installed fltk after installing a load of other tools that had already pulled in many deps... so I did not explicitly install any GL dev packges.

But the GLU header is definitely there.

 

and the output related to GL/GLU from CMake in a fresh build tree (i.e.
the first CMake run)?

Well - that was interesting. I made a new clone, the cmake configure worked.

Went back to the "broken" tree, did a git pull, re-ran cmake - still broken.

So, made a new build-folder in the broken tree, set all the same options - works...

FWIW, I do not think I have added any new libs or packages...

BUT... I can not now reproduce the fail, except in the original build folder.... I might just bin that folder and carry on...

OK, that's weird. Anyway, if it's solved it's solved. ;-)

I'm too busy to look further into it now. Thanks for the info anyway.