From: "Augusto César Dias" <augusto.c.dias@gmail.com>
To: Johannes Brechtmann <johannes@jnbr.me>
Cc: musl@lists.openwall.com, Rich Felker <dalias@libc.org>,
Szabolcs Nagy <nsz@port70.net>
Subject: Re: Problems with libc6-compat
Date: Fri, 8 Nov 2019 23:47:04 +0100 [thread overview]
Message-ID: <CALkt1WdKNQSqpp4_u-pobFJNbiLgYGVRnrab8+=V7u8bkcEjYg@mail.gmail.com> (raw)
In-Reply-To: <20191108220728.28a0723b@t440s>
[-- Attachment #1: Type: text/plain, Size: 939 bytes --]
Oh my god.
Thank you very much. It does works and everything is running smoothly now :)
Best regards,
*Augusto César Dias*
On Fri, Nov 8, 2019 at 10:08 PM Johannes Brechtmann <johannes@jnbr.me>
wrote:
> On Fri, 8 Nov 2019 19:57:24 +0100
> Augusto César Dias <augusto.c.dias@gmail.com> wrote:
>
> > Yes, even rust has an official alpine image to compile rust
> > applications on it, but it states some features won’t work such as
> > procedural macros which some libraries makes use of. Here’s an issue
> > stating what should be done...
> >
> > https://github.com/rust-lang/rust/issues/40174#issuecomment-538791091
>
> Procedural macros are not restricted by musl but by static linking,
> which rustc defaults to for musl targets. Enforcing dynamic linking
> enables you to use procedural macros on musl:
>
> https://github.com/rust-lang/rust/pull/58575#issuecomment-496026747
>
>
> Johannes
>
[-- Attachment #2: Type: text/html, Size: 2208 bytes --]
next prev parent reply other threads:[~2019-11-08 22:47 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
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 [this message]
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='CALkt1WdKNQSqpp4_u-pobFJNbiLgYGVRnrab8+=V7u8bkcEjYg@mail.gmail.com' \
--to=augusto.c.dias@gmail.com \
--cc=dalias@libc.org \
--cc=johannes@jnbr.me \
--cc=musl@lists.openwall.com \
--cc=nsz@port70.net \
/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).