From: Ekaitz Zarraga <ekaitz@elenq.tech>
To: Giovanni Biscuolo <g@xelera.eu>, 67796@debbugs.gnu.org
Subject: bug#67796: Automake is not compatible with older Autoconfs we provide
Date: Thu, 11 Jan 2024 11:40:31 +0100 [thread overview]
Message-ID: <86a3869a-0968-3c30-45e7-1f493dcbb63c@elenq.tech> (raw)
In-Reply-To: <87mstcb40b.fsf@xelera.eu>
[-- Attachment #1.1.1: Type: text/plain, Size: 838 bytes --]
Hi,
On 2024-01-11 10:42, Giovanni Biscuolo wrote:
> Hi Ekaitz
>
> Ekaitz Zarraga <ekaitz@elenq.tech> writes:
>
>> Hi,
>>
>> We have automake packaged, but it's not compatible with older autoconf
>> versions so autoconf is not very usable at this point.
>>
>> ```
>> Ekaitz@tuxedo ~/projects/nlnet/gcc/libstdc++-v3 (riscv)$ guix shell
>> automake autoconf@2.64
>
> is there a reason you need to "pin" to the 2.64 version?
I had one, I was working on GCC bootstrapping... It's not a big deal if
we just remove the older versions.
The problem I wanted to make us notice is we were keeping the 2.64
version and we didn't really provide any compatible automake, so the
autoconf@2.64 was almost useless.
If no package uses those, it's ok to remove. I can always time-machine
around the problem.
Thanks!
[-- Attachment #1.1.2: OpenPGP public key --]
[-- Type: application/pgp-keys, Size: 3185 bytes --]
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 840 bytes --]
next prev parent reply other threads:[~2024-01-11 10:41 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-12 15:00 bug#67796: Automake is not compatible with older Autoconfs we provide Ekaitz Zarraga
2023-12-12 16:59 ` Maxim Cournoyer
2023-12-12 19:47 ` Ekaitz Zarraga
2023-12-12 20:47 ` Maxim Cournoyer
2024-01-11 9:42 ` Giovanni Biscuolo
2024-01-11 10:40 ` Ekaitz Zarraga [this message]
2024-01-12 18:38 ` Giovanni Biscuolo
2024-01-12 18:53 ` Ekaitz Zarraga
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=86a3869a-0968-3c30-45e7-1f493dcbb63c@elenq.tech \
--to=ekaitz@elenq.tech \
--cc=67796@debbugs.gnu.org \
--cc=g@xelera.eu \
/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 external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.