mailing list of musl libc
 help / color / mirror / code / Atom feed
From: "Alex Xu (Hello71)" <alex_y_xu@yahoo.ca>
To: naruto canada <narutocanada@gmail.com>
Cc: musl@lists.openwall.com
Subject: Re: [musl] need help with libGL
Date: Mon, 07 Mar 2022 09:15:34 -0500	[thread overview]
Message-ID: <1646661505.19vhhjuz7c.none@localhost> (raw)
In-Reply-To: <CAKrOiPR_Uq-6CzVqAbd3ZXP4zNCP-YuZ-74M2_NHA=nWaJhm7Q@mail.gmail.com>

Excerpts from naruto canada's message of March 7, 2022 12:43 am:
> hi
> 
> I've finally managed to get xorg-server compiled and running.
> I've also managed to get llvm and mesa compiled.
> When I tried to run simple 3d test program,
> I got "Error: GLX version >= 1.3 is required"
> I've checked /var/log/Xorg.log, and got:
> Failed to load /usr/lib/xorg/modules/extensions/libglx.so: Error
> relocating /usr/lib/libGL.so.1: _ITM_dereg
> isterTMCloneTable: initial-exec TLS resolves to dynamic definition in
> /usr/lib/libGL.so.1
> 
> I've searched the web and found this thread:
> https://bugs.freedesktop.org/show_bug.cgi?id=35268
> 
> It seems musl was fixed 4 years ago.
> I've checked musl-1.2.2 source code, indeed, the fix seems to be
> there. (tlsdesc.s)
> 
> So, I recompiled mesa with patches from the thread.
> but I still get the same error message.
> 
> I also tried this simple code:
> #include <dlfcn.h>
> #include <stdio.h>
> int main()
> {
>     void *handle = dlopen("/usr/lib/libglapi.so", RTLD_LOCAL | RTLD_NOW);
>     if (!handle) {
>         printf("dlopen failed with message '%s'\n", dlerror());
>     }
> }
> 
> dlopen failed with message 'Error relocating /usr/lib/libglapi.so:
> _glapi_tls_Context: initial-exec TLS resolves to dynamic definition in
> /usr/lib/libglapi.so'
> 
> Most of what was discussed in the thread was way over my head.
> I could use some help. Thanks.
> 

The short answer is that I have submitted a fix which is included in 
Mesa 22. It seems that Mesa 22 has been delayed several times; -rc2 is 
out, but I don't know when the final will be released.

In general, I would suggest using a full Linux distribution instead of 
compiling packages individually. If for some reason you insist on 
compiling packages individually, the various musl-based Linux 
distributions are still a good reference for which patches and 
other adjustments are required for musl compatibility.

Cheers,
Alex.

      parent reply	other threads:[~2022-03-07 14:15 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-07  5:43 naruto canada
2022-03-07  6:04 ` A. Wilcox
2022-03-07  7:57   ` naruto canada
2022-03-09 22:40   ` Jory A. Pratt
2022-03-07 14:15 ` Alex Xu (Hello71) [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1646661505.19vhhjuz7c.none@localhost \
    --to=alex_y_xu@yahoo.ca \
    --cc=musl@lists.openwall.com \
    --cc=narutocanada@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.vuxu.org/mirror/musl/

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).