undefined reference to glProgramUniform3fv when building opengl app

Bug #1521806 reported by Dan Kegel
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
mesa (Ubuntu)
Expired
Undecided
Unassigned

Bug Description

A library which is being developed against the nvidia libGL.so fails to link against mesa's libGL.so.
The linker complains:

foo: undefined reference to `glProgramUniform1fv'
foo: undefined reference to `glProgramUniform1i'
foo: undefined reference to `glProgramUniform2fv'
foo: undefined reference to `glProgramUniform3fv'
foo: undefined reference to `glProgramUniform4fv'
foo: undefined reference to `glProgramUniformMatrix3fv'
foo: undefined reference to `glProgramUniformMatrix4fv'
foo: undefined reference to `glXCreateContextAttribsARB'

Is this expected behavior, punishing the developer for not using an extension loader, or something?
Or should mesa export everything nvidia exports?

Sounds like it's expected behavior, given http://sourceforge.net/p/mesa3d/mailman/message/26157363/
but I thought I'd file it in case some other OpenGL noob runs into it.

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: libgl1-mesa-dev 10.1.3-0ubuntu0.4
ProcVersionSignature: Ubuntu 3.13.0-55.92-generic 3.13.11-ckt20
Uname: Linux 3.13.0-55-generic x86_64
NonfreeKernelModules: veth aufs xt_CHECKSUM iptable_mangle ipt_MASQUERADE iptable_nat nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 nf_nat nf_conntrack xt_tcpudp bridge stp llc iptable_filter ip_tables x_tables rfcomm bnep bluetooth coretemp crct10dif_pclmul crc32_pclmul ghash_clmulni_intel vmw_balloon aesni_intel aes_x86_64 lrw gf128mul glue_helper ablk_helper cryptd serio_raw vmwgfx ppdev ttm parport_pc lp parport drm shpchp mac_hid vmw_vmci i2c_piix4 psmouse vmw_pvscsi vmxnet3 mptspi e1000 floppy mptscsih mptbase pata_acpi
ApportVersion: 2.14.1-0ubuntu3.19
Architecture: amd64
Date: Tue Dec 1 15:29:17 2015
ProcEnviron:
 TERM=xterm
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: mesa
UpgradeStatus: No upgrade log present (probably fresh install)

Revision history for this message
Dan Kegel (dank) wrote :
Revision history for this message
Oibaf (oibaf) wrote :

The used Ubuntu version (14.04) is obsolete, also mesa was updated (from 10.1.3-0ubuntu0.4 to 10.1.3-0ubuntu0.6), can you check if the problem is still reproducible with the newer mesa or on a newer Ubuntu?

Changed in mesa (Ubuntu):
status: New → Incomplete
Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for mesa (Ubuntu) because there has been no activity for 60 days.]

Changed in mesa (Ubuntu):
status: Incomplete → Expired
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.