Missing egl.h

Bug #1062954 reported by Pavol Rusnak
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Raspbian
Opinion
Undecided
Unassigned

Bug Description

Compiling SDL or other apps from source yields this error:

Missing include <GLES/egl.h>

Most of the distributions contain this file

/usr/include/GLES/egl.h

with the following content:

#ifndef __legacy_egl_h_
#define __legacy_egl_h_

#include <EGL/egl.h>
#include <GLES/gl.h>

#endif /* __legacy_egl_h_ */

I suggest to add the same file as /opt/vc/include/GLES/egl.h to make compilation of these programs possible

Revision history for this message
peter green (plugwash) wrote :

The videocore libraries are not actually part of raspbian, please complain to the raspberry pi foundation about their packaging of them.

Changed in raspbian:
status: New → Invalid
Revision history for this message
Pavol Rusnak (prusnak) wrote :

You've got to be kidding me right? Libraries ARE part of the shipped image and thus ARE part of Raspbian.

It is a distribution's task to get all of its parts working correctly. If you don't want to ship these libraries because they are in a sad state, then don't ship them but provide working alternatives.

If you feel that you are not a right person to fix the issue then REPORT it to upstream, post a backlink and close the bug. If you are unable to do this at least provide a description how to report the bug to upstream.

information type: Public → Public Security
Pavol Rusnak (prusnak)
information type: Public Security → Public
Changed in raspbian:
status: Invalid → Opinion
Revision history for this message
peter green (plugwash) wrote :

Raspbian takes debian and rebuilds it with compiler settings suitable for the raspberry pi to create a repository of packages. We do not supply packages with the firmware or videocore specific libraries and while we do supply a kernel most people are not using it.

Various parties then take our repository and build it into images that are usable on the Pi. The most visible of those parties is the raspberry Pi foundation. They have their own repository which contains their firmware/kernel/library packaging and various other bits that they use in their images.

While it would be technically possible for us to perform a "hostile takeover" of those packages I believe that doing so would likely do more harm than good.

I agree this isn't a good situation but it's also one with no easy solution. Especially given the fact that the raspberry Pi foundations software is currently a quickly moving target with no guarantees of interface stability. In some ways it would be easier if the raspberry Pi foundation had never packaged their stuff, at least that way we would have had a clean slate to start from.

Revision history for this message
peter green (plugwash) wrote :

As for reporting this issue to the raspberry pi foundation I suspect the best place is https://github.com/raspberrypi/firmware/issues

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.