Mac Link Undefined Symbols glDispatchCompute, glBindImageTexture and glMemoryBarrier

Mac Link Undefined Symbols glDispatchCompute, glBindImageTexture and glMemoryBarrier

[Roger]

I am trying to implement the OpenGL Redbook particle simulator example in Ada using OpenGLAda.
glDispatchCompute, glBindImageTexture and glMemoryBarrier are not currently available in OpenGLAda so I am attempting to update OpenGLAda to include them.
Previously I have updated OpenGLAda with numerous OpenGL functions.
However, when I attempt to implement  glDispatchCompute, glBindImageTexture and glMemoryBarrier, linking any of my OpenGLAda examples fails with:
Undefined symbols for architecture x86_64:
  "_glBindImageTexture", referenced from:
      _gl__objects__textures__bind_image in libOpenGLAda.a(gl-objects-textures.o)
  "_glDispatchCompute", referenced from:
      _gl__objects__programs__dispatch_compute in libOpenGLAda.a(gl-objects-programs.o)
  "_glMemoryBarrier", referenced from:
      _gl__objects__programs__memory_barrier in libOpenGLAda.a(gl-objects-programs.o)

Any suggestions as to why these undefined symbols occur will be greatly appreciated.
Thanks in advance,
Roger

Re: Mac Link Undefined Symbols glDispatchCompute, glBindImageTexture and glMemoryBarrier

[Simon Wright]

Could they be (C) macros?

Re: Mac Link Undefined Symbols glDispatchCompute, glBindImageTexture and glMemoryBarrier

[Egil H H]

On Monday, October 21, 2019 at 11:28:37 AM UTC+2, Simon Wright wrote:
> Could they be (C) macros?

Could your bindings be a bit old?
Looks like they were added in OpenGL 4.2 and 4.3

-- 
~egilhh

Re: Mac Link Undefined Symbols glDispatchCompute, glBindImageTexture and glMemoryBarrier

[Egil H H]

On Monday, October 21, 2019 at 12:10:53 PM UTC+2, Egil H H wrote:
> On Monday, October 21, 2019 at 11:28:37 AM UTC+2, Simon Wright wrote:
> > Could they be (C) macros?
> 
> Could your bindings be a bit old?

Sorry, should be "bindings too new" or "OpenGL library too old", of course...

Re: Mac Link Undefined Symbols glDispatchCompute, glBindImageTexture and glMemoryBarrier

[Chris M Moore]

On 21/10/2019 11:19, Egil H H wrote:
> On Monday, October 21, 2019 at 12:10:53 PM UTC+2, Egil H H wrote:
>> On Monday, October 21, 2019 at 11:28:37 AM UTC+2, Simon Wright wrote:
>>> Could they be (C) macros?
>>
>> Could your bindings be a bit old?
> 
> Sorry, should be "bindings too new" or "OpenGL library too old", of course...
> 

https://www.khronos.org/registry/OpenGL-Refpages/gl4/html/glBindImageTexture.xhtml 
says "The glBindImageTexture is available only if the GL version is 4.2 
or greater."

https://www.khronos.org/registry/OpenGL-Refpages/gl4/html/glDispatchCompute.xhtml 
says v4.3.

https://www.khronos.org/opengl/wiki/GLAPI/glMemoryBarrier says 4.2.

I don't know if this is up to date but 
https://developer.apple.com/library/archive/documentation/GraphicsImaging/Conceptual/OpenGL-MacProgGuide/opengl_intro/opengl_intro.html 
says "supporting versions of OpenGL from 1.x through OpenGL 3.2". 
Conclusion "OpenGL library too old".


--
sig pending (since 1995)

Re: Mac Link Undefined Symbols glDispatchCompute, glBindImageTexture and glMemoryBarrier

[Roger]

On Monday, October 21, 2019 at 8:28:37 PM UTC+11, Simon Wright wrote:
> Could they be (C) macros?

Sorry!
I thought I'd deleted this post.
I found my problem in that I'd misspecfied a declaration parameter.
The linker now finds glDispatchCompute, glBindImageTexture and glMemoryBarrier.
Thanks for all responses.

Re: Mac Link Undefined Symbols glDispatchCompute, glBindImageTexture and glMemoryBarrier

[Roger]

On Monday, October 21, 2019 at 9:19:50 PM UTC+11, Egil H H wrote:
> On Monday, October 21, 2019 at 12:10:53 PM UTC+2, Egil H H wrote:
> > On Monday, October 21, 2019 at 11:28:37 AM UTC+2, Simon Wright wrote:
> > > Could they be (C) macros?
> > 
> > Could your bindings be a bit old?
> 
> Sorry, should be "bindings too new" or "OpenGL library too old", of course...

Yes, sort of.
Apple doesn't support OpenGL beyond 4.1!
However, I was able to compile, link and build using the 4.3 routines.
Of course, the program crashed as soon as it tried to build  a compute shader.

Re: Mac Link Undefined Symbols glDispatchCompute, glBindImageTexture and glMemoryBarrier

[Jere]

On Monday, October 21, 2019 at 8:24:39 PM UTC-4, Roger wrote:
> On Monday, October 21, 2019 at 8:28:37 PM UTC+11, Simon Wright wrote:
> > Could they be (C) macros?
> 
> Sorry!
> I thought I'd deleted this post.
> I found my problem in that I'd misspecfied a declaration parameter.
> The linker now finds glDispatchCompute, glBindImageTexture and glMemoryBarrier.
> Thanks for all responses.

Since these are not forum posts, you cannot just delete them.  They are
emails that get sent out as soon as you "post".  You can delete some
emails from showing up on google groups, but they still go out
after you send them and if an archive site catches them, they will be
archived somewhere else on the web.  Hope that helps!

Re: Mac Link Undefined Symbols glDispatchCompute, glBindImageTexture and glMemoryBarrier

[Roger]

On Thursday, October 24, 2019 at 9:43:30 PM UTC+11, Jere wrote:
> On Monday, October 21, 2019 at 8:24:39 PM UTC-4, Roger wrote:
> > On Monday, October 21, 2019 at 8:28:37 PM UTC+11, Simon Wright wrote:
> > > Could they be (C) macros?
> > 
> > Sorry!
> > I thought I'd deleted this post.
> > I found my problem in that I'd misspecfied a declaration parameter.
> > The linker now finds glDispatchCompute, glBindImageTexture and glMemoryBarrier.
> > Thanks for all responses.
> 
> Since these are not forum posts, you cannot just delete them.  They are
> emails that get sent out as soon as you "post".  You can delete some
> emails from showing up on google groups, but they still go out
> after you send them and if an archive site catches them, they will be
> archived somewhere else on the web.  Hope that helps!

Thanks for the explanation.

Re: Mac Link Undefined Symbols glDispatchCompute, glBindImageTexture and glMemoryBarrier

[Dennis Lee Bieber]

On Thu, 24 Oct 2019 03:43:28 -0700 (PDT), Jere <jhb.chat@gmail.com>
declaimed the following:


>Since these are not forum posts, you cannot just delete them.  They are
>emails that get sent out as soon as you "post".  You can delete some
>emails from showing up on google groups, but they still go out
>after you send them and if an archive site catches them, they will be
>archived somewhere else on the web.  Hope that helps!

	More than that -- I'm accessing this as a Usenet Newsgroup
(comp.lang.ada) which distributes posts to peer servers. NNTP does support
a delete command, which can be forwarded to those peer servers -- but most
servers will not honor deletes (too easy for spoofers to delete posts from
someone they don't like).

	In the old days, news servers tended to expire articles rather fast
(When I started, Netcom expired text groups at around 30-days, and binary
groups expired in three days, if not two [miss a day and you lost a lot of
binary posts). I currently use Giganews (Netcom -> Mindspring -> Earthlink:
and Earthlink subcontracted to Giganews, so when I lost my Earthlink DSL in
a move I had to pay for my own news account [I still pay Earthlink a token
to maintain my old email addresses, but also lost my old static web page
sites]). Giganews claims 16+ years for text, and 3+ years for binaries.



-- 
	Wulfraed                 Dennis Lee Bieber         AF6VN
	wlfraed@ix.netcom.com    http://wlfraed.microdiversity.freeddns.org/

Re: Mac Link Undefined Symbols glDispatchCompute, glBindImageTexture and glMemoryBarrier

[Keith Thompson]

Jere <jhb.chat@gmail.com> writes:
> On Monday, October 21, 2019 at 8:24:39 PM UTC-4, Roger wrote:
>> On Monday, October 21, 2019 at 8:28:37 PM UTC+11, Simon Wright wrote:
>> > Could they be (C) macros?
>> 
>> Sorry!
>> I thought I'd deleted this post.
>> I found my problem in that I'd misspecfied a declaration parameter.
>> The linker now finds glDispatchCompute, glBindImageTexture and glMemoryBarrier.
>> Thanks for all responses.
>
> Since these are not forum posts, you cannot just delete them.  They are
> emails that get sent out as soon as you "post".  You can delete some
> emails from showing up on google groups, but they still go out
> after you send them and if an archive site catches them, they will be
> archived somewhere else on the web.  Hope that helps!

Mostly correct, but Usenet posts are not emails (though they have
some similarities, particularly in the organization of the headers),
nor are they part of the web (Usenet predates http).

The Usenet protocol does provide for cancelling messages (by
sending a control message that refers to the message-id of the
message being cancelled), but due to past abuse (cancel messages
are not authenticated) most Usenet servers ignore cancels.

Note also that Google Groups merely provides an interface to Usenet.
GG has the biggest archive, but the core of Usenet is a collection
of independent NNTP servers.

Bottom line: You almost certainly can't cancel a Usenet post once
you've sent it.

-- 
Keith Thompson (The_Other_Keith) kst-u@mib.org  <http://www.ghoti.net/~kst>
Will write code for food.
void Void(void) { Void(); } /* The recursive call of the void */