Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Torbjorn SVENSSON <torbjorn.svensson@foss.st.com>
To: Simon Marchi <simark@simark.ca>, <binutils@sourceware.org>,
	<gdb-patches@sourceware.org>
Subject: Re: [PATCH] configure: Support --with-zstd=PATH
Date: Tue, 29 Sep 2026 07:36:12 +0200	[thread overview]
Message-ID: <87770b91-13aa-426b-8e4f-0454b4f815bc@foss.st.com> (raw)
In-Reply-To: <d2612532-b6d0-4439-a106-ada9ad987501@simark.ca>



On 2026-09-29 03:55, Simon Marchi wrote:
> 
> 
> On 2026-09-27 07:48, Torbjörn SVENSSON wrote:
>> Hi,
>>
>> I noticed that the configure scripts in this repository does not use the path
>> given to the --with-zstd option, while for example GCC does.  This patch adds
>> the missing logic in config/zstd.m4 and regenerat the configure files with that
>> change.
>>
>> Also worth noting is that I see blocks like below (manually excluded in this
>> patch) when I run autoconf2.69:
>>
>> -#define LARGE_OFF_T (((off_t) 1 << 62) - 1 + ((off_t) 1 << 62))
>> +#define LARGE_OFF_T ((((off_t) 1 << 31) << 31) - 1 + (((off_t) 1 << 31) << 31))
> 
> In which directory do you see that?
> 
> Normally, this builder here re-generates a bunch of things, including
> the configure machinery, and errors out if it sees any difference.  Make
> sure you use an upstream autoconf build, not a build from a distro.

Ah, my bad!
I have a vanilla autoconf 2.69, but apparently, it had got lost on my $PATH.

With the one from the distro, I got the changes for:
bfd/configure
binutils/configure
gas/configure
gdb/configure
ld/configure

> 
> https://builder.sourceware.org/buildbot/#/builders/270
> 
> Simon

Kind regards,
Torbjörn


      reply	other threads:[~2026-09-29  5:37 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-27 11:48 Torbjörn SVENSSON
2026-09-29  1:55 ` Simon Marchi
2026-09-29  5:36   ` Torbjorn SVENSSON [this message]

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=87770b91-13aa-426b-8e4f-0454b4f815bc@foss.st.com \
    --to=torbjorn.svensson@foss.st.com \
    --cc=binutils@sourceware.org \
    --cc=gdb-patches@sourceware.org \
    --cc=simark@simark.ca \
    /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