From: "Martin Storsjö" <martin@martin.st> To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org> Subject: Re: [FFmpeg-devel] [PATCH] configure: improve ar test for response files Date: Tue, 18 Mar 2025 16:41:56 +0200 (EET) Message-ID: <c2c6ecb-2bed-d43f-2718-399c9f1cc210@martin.st> (raw) In-Reply-To: <20250318135252.22378-1-ffmpeg@gyani.pro> On Tue, 18 Mar 2025, Gyan Doshi wrote: > --- > configure | 13 +++++++------ > 1 file changed, 7 insertions(+), 6 deletions(-) > > diff --git a/configure b/configure > index d84e32196d..2c060b0cd4 100755 > --- a/configure > +++ b/configure > @@ -5230,12 +5230,6 @@ else > ar_o='$@' > fi > > -if $ar 2>&1 | grep -qi "@.*file"; then > - ar_objs="true" > -else > - ar_objs="" > -fi > - > add_cflags $extra_cflags > add_cxxflags $extra_cxxflags > add_objcflags $extra_objcflags > @@ -7759,6 +7753,13 @@ case $ld_type in > ;; > esac > > +{ > +ar_out=${FFTMPDIR}/test$LIBSUF > +respfile="@/dev/null" I'm a little bit hesitant about using a special file like /dev/null; I wasn't sure about how this would work e.g. with MSVC. It seems to work both with msvc-wine, MSVC run through msys2, and both GCC/binutils and llvm-mingw in msys2. (I haven't tested MSVC through WSL, but I would expect it to work if these other configs work.) So it's not an issue - this check does work as intended, but I would maybe have preferred a real rsp file. (But that requires more temp files to clean up.) > +out_arg="${ar_o/\$@/$ar_out}" This isn't posix sh syntax; running configure on e.g. ubuntu with /bin/sh == dash, gives: src/configure: 7759: Bad substitution // 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".
prev parent reply other threads:[~2025-03-18 14:42 UTC|newest] Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top 2025-03-18 13:52 Gyan Doshi 2025-03-18 14:41 ` Martin Storsjö [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=c2c6ecb-2bed-d43f-2718-399c9f1cc210@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