mailing list of musl libc
 help / color / mirror / code / Atom feed
From: Szabolcs Nagy <nsz@port70.net>
To: musl@lists.openwall.com
Cc: "Augusto César Dias" <augusto.c.dias@gmail.com>
Subject: Re: Problems with libc6-compat
Date: Fri, 8 Nov 2019 14:15:11 +0100	[thread overview]
Message-ID: <20191108131509.GB25646@port70.net> (raw)
In-Reply-To: <CALkt1Wc0Nu3nH9TKuQkjq2L7cSojTOQc6OVN8iieYw9SredJUw@mail.gmail.com>

* Augusto César Dias <augusto.c.dias@gmail.com> [2019-11-08 13:26:33 +0100]:
> My application depends on glib2 which I installed through apk and when it
> starts it fails with the following:
> 
> **
> GLib-GObject:ERROR:../gobject/gtype.c:2743:g_type_register_static:
> assertion failed: (static_quark_type_flags)
> Aborted

there is at least one known glibc quark bug
https://gitlab.alpinelinux.org/alpine/aports/blob/master/main/glib/0001-gquark-fix-initialization-with-c-constructors.patch

but that should be fixed in alpine, and in recent musl
it should work even without patching, unless this is
static linking.

> I've trying to compile a C example directly in my alpine container and it
> works in there, so that made me believe I'm having some problems with the
> cross compilation/linking in my glibc container.
> 
> Any ideas on how can I solve this?

why do you need to cross compile?

building natively on a musl based distro where all dependencies
are correctly built and packaged should be much more reliable.


  reply	other threads:[~2019-11-08 13:15 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-11-08 12:26 Augusto César Dias
2019-11-08 13:15 ` Szabolcs Nagy [this message]
2019-11-08 13:18   ` Augusto César Dias
2019-11-08 17:47     ` Rich Felker
2019-11-08 18:57       ` Augusto César Dias
2019-11-08 21:07         ` Johannes Brechtmann
2019-11-08 22:47           ` Augusto César Dias
2019-11-08 21:35         ` A. Wilcox

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=20191108131509.GB25646@port70.net \
    --to=nsz@port70.net \
    --cc=augusto.c.dias@gmail.com \
    --cc=musl@lists.openwall.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).