Github messages for voidlinux
 help / color / mirror / Atom feed
From: ericonr <ericonr@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: New package: universal-ctags-5.9.20210131.0
Date: Fri, 19 Feb 2021 21:50:50 +0100	[thread overview]
Message-ID: <20210219205050.Q2A0gBHSWaRrpT_qTyCQoZo5Ghn5qZq-mawLufZi9jE@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-28544@inbox.vuxu.org>

[-- Attachment #1: Type: text/plain, Size: 859 bytes --]

New comment by ericonr on void-packages repository

https://github.com/void-linux/void-packages/pull/28544#issuecomment-782339333

Comment:
```
	if type perl > /dev/null; then
		for i in ${ctags_files}; do
			o=${i%.ctags}.c
			echo "optlib2c: translating $i to $o"
			if ! ./misc/optlib2c $i > $o; then
				echo "failed in running optlib2c" 1>&2
				exit 1
			fi
		done
	else
		for i in ${ctags_files}; do
			o=${i%.ctags}.c
			echo "use pre-translated file: $o"
		done
	fi
```

I'm okay with using the pre-translated stuff...

> I don't understand what you mean, I hope you can tell me in details, thank you!

The main difference between musl and glibc iconv is that glibc allows `<enconding>//<suffix>` as parameters to `iconv_open`, which change how the function behaves. I will check out the test suite locally to see what's wrong.

  parent reply	other threads:[~2021-02-19 20:50 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-02-06  9:13 [PR PATCH] " Gottox
2021-02-06 10:03 ` [PR PATCH] [Updated] " Gottox
2021-02-06 10:05 ` Gottox
2021-02-19 20:13 ` leleliu008
2021-02-19 20:23 ` ericonr
2021-02-19 20:33 ` leleliu008
2021-02-19 20:37 ` leleliu008
2021-02-19 20:50 ` ericonr [this message]
2021-02-19 20:52 ` ericonr
2021-02-19 21:06 ` ericonr
2021-02-22 20:29 ` Gottox
2021-03-19 18:31 ` [PR PATCH] [Closed]: " Gottox

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=20210219205050.Q2A0gBHSWaRrpT_qTyCQoZo5Ghn5qZq-mawLufZi9jE@z \
    --to=ericonr@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).