Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
 help / color / mirror / Atom feed
From: "Martin Storsjö" <martin@martin.st>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Subject: Re: [FFmpeg-devel] [PATCH] configure: Make MSVC version grabbing more robust
Date: Sat, 21 Jun 2025 22:49:48 +0300 (EEST)
Message-ID: <595405c-796e-63d-c55d-20475b3c19d1@martin.st> (raw)
In-Reply-To: <CABPLASQT7Z_ndth5C5EaYZDqZnbahnsRQ4C_Jg5oPu+YUSW9wg@mail.gmail.com>

On Sat, 21 Jun 2025, Kacper Michajlow wrote:

> On Sat, 21 Jun 2025 at 19:18, Alexander Strasser via ffmpeg-devel
> <ffmpeg-devel@ffmpeg.org> wrote:
>>
>>
>>
>>
>> ---------- Forwarded message ----------
>> From: Alexander Strasser <eclipse7@gmx.net>
>> To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
>> Cc:
>> Bcc:
>> Date: Sat, 21 Jun 2025 19:18:03 +0200
>> Subject: Re: [FFmpeg-devel] [PATCH] configure: Make MSVC version grabbing more robust
>> Hi Martin!
>>
>> On 2025-06-21 13:37 +0300, Martin Storsjö wrote:
>> > > On 21. Jun 2025, at 12.20, Alexander Strasser via ffmpeg-devel <ffmpeg-devel@ffmpeg.org> wrote:
>> > >
>> > >
>> > > On 2025-06-21 00:03 +0200, Kacper Michajlow wrote:
>> > >> On Fri, 20 Jun 2025 at 22:26, Hendrik Leppkes
>> > >> <h.leppkes-at-gmail.com@ffmpeg.org> wrote:
>> > >>>
>> > >>> On Fri, Jun 20, 2025 at 9:25 PM Timo Rothenpieler <timo@rothenpieler.org> wrote:
>> > >>>>
>> > >>>> Likely this patch broke multiple fate runners in a silent way.
>> > >>>> On mine, configure simply never returns, and just sits there
>> > >>>> indefinitely, with no CPU usage or any activity whatsoever.
>> > >>>>
>> > >>>> nevcairiel confirmed seeing the same behaviour on IRC.
>> > >>>>
>> > >>>> The msys+clang builds from within the same environment work fine.
>> > >>>>
>> > >>>>
>> > >>>> Didn't verify completely if it's caused by this patch, but nothing else
>> > >>>> happened with configure since the last successful run.
>> > >>>
>> > >>> I did some digging, and it happens when probe_cc probes link.exe
>> > >>>
>> > >>> link.exe has an interactive help output (its paginated) - previously
>> > >>> piping stdout disabled the pagination automatically - but redirecting
>> > >>> it to devnull does not, and it gets stuck waiting for input.
>> > >>> Additionally, link.exe outputs the ident on stdout, so there is no
>> > >>> result on stderr (not super bad, as LD_IDENT is never used - yet)
>> > >>
>> > >> Instead of redirecting to devnull, we could use the same condition as
>> > >> in if. We already look for specific ident line, so no need to head.
>> > >> _ident=$($_cc -nologo- 2>&1 | grep ^Microsoft | tr -d '\r')
>> > >> should work, no? I would be happy to see a better solution, though.
>> > >
>> > > I think making sure to only use the first line that starts with
>> > > Microsoft is more robust; there could be (in the future) more lines
>> > > that start with Microsoft.
>> > >
>> > >> btw. running cl.exe 3 times to just get its name is interesting :)
>> > >
>> > > Yes, so that as well. Could be optimized, but is probably not so
>> > > relevant in total.
>> > >
>> > > I propose the attached patch.
>> > >
>> > >
>> > >  Alexander
>> > > <0001-configure-Fix-a-regression-when-probing-link.exe.patch>
>> >
>> > Thanks, this patch looks good to me, feel free to push! (And I can push it later today if nobody else does it before that.)
>> >
>> > If you want to, one can also extend the commit message further to say more explicitly, that 45a30e03613a3c63d74a40f7ac86ce28dce14ff8 caused configure to hang in some configurations, which this fixes.
>>
>> I have attached an updated version. Hope you like the commit message
>> better.
>>
>> I can push it tomorrow or you can do earlier.
>
> LGTM. I tested locally for link.exe and cl.exe. As for server/fate
> testing, I think we can push and monitor if runners are unblocked.
> People have things automated, so it probably takes "effort" to just do
> manual patch testing out-of-tree.

Thanks! I also managed to reproduce the issue now, and can confirm that 
this seems to fix it - so I pushed it.

// Martin
_______________________________________________
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-devel

To unsubscribe, visit link above, or email
ffmpeg-devel-request@ffmpeg.org with subject "unsubscribe".

  reply	other threads:[~2025-06-21 19:50 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-06-13 14:05 Martin Storsjö
2025-06-19 20:21 ` Martin Storsjö
2025-06-20 19:25   ` Timo Rothenpieler
2025-06-20 20:26     ` Hendrik Leppkes
2025-06-20 22:03       ` Kacper Michajlow
2025-06-21  9:20         ` Alexander Strasser via ffmpeg-devel
2025-06-21 10:37           ` Martin Storsjö
2025-06-21 17:18             ` Alexander Strasser via ffmpeg-devel
2025-06-21 18:45               ` Kacper Michajlow
2025-06-21 19:49                 ` Martin Storsjö [this message]
2025-06-21 10:34         ` Martin Storsjö
2025-06-21 11:55           ` Kacper Michajlow
2025-06-21 16:04             ` Martin Storsjö

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=595405c-796e-63d-c55d-20475b3c19d1@martin.st \
    --to=martin@martin.st \
    --cc=ffmpeg-devel@ffmpeg.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

Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel

This inbox may be cloned and mirrored by anyone:

	git clone --mirror https://master.gitmailbox.com/ffmpegdev/0 ffmpegdev/git/0.git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V2 ffmpegdev ffmpegdev/ https://master.gitmailbox.com/ffmpegdev \
		ffmpegdev@gitmailbox.com
	public-inbox-index ffmpegdev

Example config snippet for mirrors.


AGPL code for this site: git clone https://public-inbox.org/public-inbox.git