~lattis/muon

2

Re: Build with libpkgconf

Details
Message ID
<1361807469.115767.1642221113660@office.mailbox.org>
DKIM signature
missing
Download raw message
Well, now that I got muon, I tried it on a port I’m working on, but it
segfaults :)
Here [1] is a reproducible build.
[1] https://builds.sr.ht/~iemaghni/job/672519

Re: Build with libpkgconf

Details
Message ID
<20220117211957.5bshzp7wahvrbhan@localhost>
In-Reply-To
<1361807469.115767.1642221113660@office.mailbox.org> (view parent)
DKIM signature
missing
Download raw message
> Well, now that I got muon,

Great :)

> I tried it on a port I’m working on, but it segfaults :)

Could you rerun that muon invocation under a debugger or valgrind and
provide the stacktrace?  Also, please add the `-v` flag. That would
really help me debug your issue!

Thanks,
Stone

Re: Build with libpkgconf

Details
Message ID
<20220131130735.rdftkwirjg4c6pv4@hostomei>
In-Reply-To
<1361807469.115767.1642221113660@office.mailbox.org> (view parent)
DKIM signature
missing
Download raw message
Hello,

I spent a little time digging in to this, and my suspicion was correct.
The bug is in pkgconf, not muon.  I have submitted an issue[1] to the
pkgconf issue tracker, and may have a PR at some point if I get the
time.  Basically it is yet another case of differences between glibc and
musl.

By the way, I noticed this build was on alpine.  You can just add
`pkgconf-dev` to your dependencies and muon won't need the pkgconf
subproject.  The official alpine pkgconf build uses autotools to build,
which apparently is more correct than pkgconf's meson.build.

Stone

[1]: https://github.com/pkgconf/pkgconf/issues/244
Reply to thread Export thread (mbox)