public inbox for binutils@sourceware.org
 help / color / mirror / Atom feed
From: Jan Beulich <jbeulich@suse.com>
To: Nick Clifton <nickc@redhat.com>
Cc: Indu Bhagat <indu.bhagat@oracle.com>, binutils@sourceware.org
Subject: Re: Question regarding min reqd dejagnu version
Date: Tue, 4 Oct 2022 12:05:03 +0200	[thread overview]
Message-ID: <0a0ce700-4ee1-1ac8-cab5-981ea96917a7@suse.com> (raw)
In-Reply-To: <92cab149-dd27-43ff-f6e6-da0e9e9d29fc@redhat.com>

On 04.10.2022 11:52, Nick Clifton via Binutils wrote:
> Hi Guys,
> 
>    I am checking in the attached patch to update the README-maintainer-mode
>    file so that it also lists a minimum version of dejagnu required to run
>    the testsuites.  Whilst I was at it I noticed that the URLs needed a https:
>    prefix rather than ftp:, so I changed that as well.

I'm concerned: We support building with pretty old gcc. The minimum
dejagnu version is now much newer, which will require me to see if I
can sensibly build myself a newer version of it on some of my older
systems, not even thinking of yet whether it'll be possible to
install the newer version side by side with the distro provided one.

Also - is this patch really meant to also change src-release.sh?

Jan

  reply	other threads:[~2022-10-04 10:05 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-01  0:18 Indu Bhagat
2022-10-03 10:23 ` Nick Clifton
2022-10-03 17:55   ` Indu Bhagat
2022-10-04  9:52     ` Nick Clifton
2022-10-04 10:05       ` Jan Beulich [this message]
2022-10-04 10:20         ` Nick Clifton
2022-10-04 10:27           ` Jan Beulich
2022-10-04 11:40             ` Nick Clifton
2022-10-05 18:28               ` Indu Bhagat

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=0a0ce700-4ee1-1ac8-cab5-981ea96917a7@suse.com \
    --to=jbeulich@suse.com \
    --cc=binutils@sourceware.org \
    --cc=indu.bhagat@oracle.com \
    --cc=nickc@redhat.com \
    /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 read-only IMAP folder(s) and NNTP newsgroup(s).