From: loreb <loreb@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: Tcc won't link executables
Date: Wed, 05 May 2021 14:50:56 +0200 [thread overview]
Message-ID: <20210505125056.QRrGBrTwEUvkSXpIjA-EG7Rr9gdtJvuZkpnrHF_wZm0@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-30630@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 882 bytes --]
New comment by loreb on void-packages repository
https://github.com/void-linux/void-packages/issues/30630#issuecomment-832661216
Comment:
Confirmed; it works fine (musl&glibc) after installing gcc (probably also clang), but their templates are complicated enough that imho the easiest solution would be to depend on one or the other, even if it pulls in some unnecessary dependencies.
If you feel like doing some boring work:
- install gcc; confirm that tcc works, and write down which packages were installed
- uninstall the packages from above
- try installing&uninstalling until you find the smallest set of gcc dependencies that gets tcc working
- report your findings
- repeat on a musl virtual machine (or use WSL on windows 10 or something)
Of course. if you wish not to lose your sanity, do the first step by hand, and then write a **script** to do the rest!!!
next prev parent reply other threads:[~2021-05-05 12:50 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-02 13:34 [ISSUE] " niansa
2021-05-05 12:50 ` loreb [this message]
2021-05-05 14:25 ` ericonr
2021-08-23 21:04 ` hiltjo
2021-08-24 19:02 ` loreb
2021-08-25 16:56 ` hiltjo
2021-08-25 18:55 ` loreb
2021-08-30 9:43 ` loreb
2022-05-15 18:48 ` hiltjo
2022-05-16 15:38 ` loreb
2022-05-16 20:01 ` hiltjo
2022-05-16 20:02 ` hiltjo
2022-05-18 15:25 ` loreb
2022-05-19 12:18 ` ericonr
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=20210505125056.QRrGBrTwEUvkSXpIjA-EG7Rr9gdtJvuZkpnrHF_wZm0@z \
--to=loreb@users.noreply.github.com \
--cc=ml@inbox.vuxu.org \
/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.
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).