From: loreb <loreb@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: Tcc won't link executables
Date: Wed, 18 May 2022 17:25:06 +0200 [thread overview]
Message-ID: <20220518152506.bnq8iFqjKcyHmQzdzw_VpIs-RDkokU5FBmqnMYfnobc@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: 731 bytes --]
New comment by loreb on void-packages repository
https://github.com/void-linux/void-packages/issues/30630#issuecomment-1130161417
Comment:
@hiltjo The problem is that upstream hasn't made a release in the past years and the package is orphaned...
meaning that I have **no idea** if the upstream is conservative ("every commit could be a release!") or more let's say experimental ("there's a good reason we haven't made a release..."); the latest commit doesn't have this problem (just tested in a vm), so go on, git bisect and submit a pr to fix the crt1.o issue as well.
Before you ask: the package works well enough for me as is, I only use tcc for scripts ("#! /usr/bin/tcc -run"), and that works fine even on void/glibc.
next prev parent reply other threads:[~2022-05-18 15:25 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
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 [this message]
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=20220518152506.bnq8iFqjKcyHmQzdzw_VpIs-RDkokU5FBmqnMYfnobc@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).