From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from ffbox0-bg.ffmpeg.org (ffbox0-bg.ffmpeg.org [79.124.17.100]) by master.gitmailbox.com (Postfix) with ESMTPS id 1CED14F4DF for ; Tue, 17 Jun 2025 14:06:30 +0000 (UTC) Received: from [127.0.1.1] (localhost [127.0.0.1]) by ffbox0-bg.ffmpeg.org (Postfix) with ESMTP id E1E2568D2FD; Tue, 17 Jun 2025 17:06:22 +0300 (EEST) Received: from mail-ed1-f50.google.com (mail-ed1-f50.google.com [209.85.208.50]) by ffbox0-bg.ffmpeg.org (Postfix) with ESMTPS id 8062868C54E for ; Tue, 17 Jun 2025 17:06:16 +0300 (EEST) Received: by mail-ed1-f50.google.com with SMTP id 4fb4d7f45d1cf-60780d74c8cso10412155a12.2 for ; Tue, 17 Jun 2025 07:06:16 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1750169176; x=1750773976; darn=ffmpeg.org; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=HNaHsX/dT6ag9WQ1iuTDREkaI1L5QtUM5bksq63R1iU=; b=IhIu309BS8w2biwJus1JA4NsGV/qT/JUFSVXxHmkpd7N8Rd+csbcrwoH/9qQrFJIk1 fQHEtgju8udMZCa3Ih5WJz0a50tb78S0DmMc096j9Ssnjg2ga/TLwiMWrBz7VpH3tl93 SZXGub4P0NbKR3vglzdpA5FJ2sFfxcptqcNfW11xLcDs0RFAt+rlJg9peKW93uRfGAW4 J+YrL/IFJEKEBFtKSaZQoJtvwAU5D7KqjXGTBm3BqOwBn5jioDNxqTf5M27WzyvWE4xv 3AbZNsOdUzWUhBD8Mz9IhyUpyvoR+CTNlkaNeKLEXDCSTaCXdku6rVZ4K0nVgHvAQPWk f2QA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1750169176; x=1750773976; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=HNaHsX/dT6ag9WQ1iuTDREkaI1L5QtUM5bksq63R1iU=; b=WoQXovHpWKgTgkZv9vC6fzwR/HlPaijjREJEVJLnNFcKRKsj87jgqaI3VrQMGhBR6J T89coT8LaecksN5mC0P3RZZL5EPuZiE+XZyLMiJ0VyZYknpRCCUEgEK6aEaMJ2zuhcUd SsXZ+CBBHub6Nkxi+mkDmFGdqesoAKGnKwOqKTQfDHQw3xVJC1jHtiA2FgGhL2WByht1 aTJpmd+PHqXaqb5ZKdA1s2IXBgrgS5hpQNtucl2ZeORlM7tK/ExYjWhSofY14d7F7Dyx 0Il8nMKJ1IZacjwLkg7Ycc/DvSatEMjK2QtxfFxOD1/57Uthgw4ZMgCh5PgHC8Ft8T0N UqQg== X-Gm-Message-State: AOJu0YwmwOj6ez/cmjSnv/C+iaurVkkp2i/V9pVa6+ZS0gtS8DScMFcJ roVI40ZqhtD8bLJkAVy/2IJGH25eN7eE3aPbkh1z229iNqMzKF15gJUK7t/dfeWvX+bqPrFTVuj 0u1MhKXLU42pS5IcP7Stf4g3T/9QTcNqbhg== X-Gm-Gg: ASbGnctpOEDhMbslec1xmkGWxhrrHf8RaKATAmOMlogh5+uhzgEUtumHVETwIqq0vWi +RwM5x48ORbg/RWrXD9qKGRelCSEsA/fzMH4N45IlReKGgEmdi2eWJSj7d5ouELelrUSG+loOlJ AaUcpM4I9Az/dJmCvnuuBhVvs7L0lXNuXqhR0c94WY X-Google-Smtp-Source: AGHT+IFD4ssAmRnG+Iw6L8iBwBr0Ccfqe9zXJnfFM3CrDGgWVrVaK7Gqbw38kncg7ofgp29aWSKoAaqOQ9uc5Bz8lws= X-Received: by 2002:a05:6402:26c7:b0:604:5659:8ca7 with SMTP id 4fb4d7f45d1cf-608d09482c1mr11999423a12.19.1750169175426; Tue, 17 Jun 2025 07:06:15 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: From: Kacper Michajlow Date: Tue, 17 Jun 2025 16:06:04 +0200 X-Gm-Features: AX0GCFtfTfrmO67THaQN2w9orKqAEA5zKjhJspImPoDkhm8FYFvCow-LmaioEpA Message-ID: To: "softworkz ." Subject: Re: [FFmpeg-devel] graph.{html,css} embed failure on Windows build X-BeenThere: ffmpeg-devel@ffmpeg.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: FFmpeg development discussions and patches List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Reply-To: FFmpeg development discussions and patches Cc: FFmpeg development discussions and patches Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Errors-To: ffmpeg-devel-bounces@ffmpeg.org Sender: "ffmpeg-devel" Archived-At: List-Archive: List-Post: On Tue, 17 Jun 2025 at 15:10, Kacper Michajlow wrote: > > On Tue, 17 Jun 2025 at 04:07, softworkz . wrote: > > > > > > > -----Original Message----- > > > From: Kacper Michajlow > > > Sent: Sunday, June 15, 2025 12:49 AM > > > To: FFmpeg development discussions and patches > > devel@ffmpeg.org> > > > Cc: softworkz@hotmail.com > > > Subject: graph.{html,css} embed failure on Windows build > > > > > > Hello, > > > > > > Since the recent addition of resman.c and embedding of graph.{html,css} > > > some of the Windows builds fail. There seems to be a regression in path > > > joining, caused by \ / mismatch. > > > > > > Generally those issues were never a problem and I would prefer to keep it this > > > way. This configuration has always been flaky and undertested. > > > I could set-up a pipeline to report to the fate server if that's something that > > > would help stabilize it. > > > > > > Example of failure: > > > ``` > > > BIN2C fftoolsresourcesgraph.html.c > > > BIN2C fftools/resources/graph.html.c > > > SED fftoolsresourcesgraph.css.min > > > sed: can't read /c/a/FFmpeg/FFmpeg/fftoolsresources/graph.css: No such file > > > or directory SED fftools/resources/graph.css.min > > > make: *** No rule to make target 'fftools\resources\graph.html.c', needed by > > > 'fftools/resources/graph.html.o'. Stop. > > > make: *** Waiting for unfinished jobs.... > > > HOSTCC tests/videogen.o > > > rm fftools\resources\graph.css.min fftools/resources/graph.html.c ``` > > > > > > Note that BIN2C is called twice, once with the correct path and with the > > > wrong one. > > > > > > Removing resman.c fixes the build. This has to be done forcefully in the code, > > > because there is no configure option to disable this html/css embedding. > > > > > > You can see the details and whole failing build logs here: > > > code: https://github.com/kasper93/FFmpeg/tree/gha > > > build: > > > https://github.com/kasper93/FFmpeg/actions/runs/15653223193/job/44100 > > > 735119 > > > command: $ ../configure --enable-gpl --enable-version3 --enable-nonfree -- > > > samples=../samples --enable-memory-poisoning > > > --arch=amd64 --enable-w32threads --as=clang --ar=llvm-ar --cxx=clang++ -- > > > ld=lld-link --windres=llvm-windres --strip=llvm-strip --cc=clang --nm=llvm-nm > > > --extra-ldflags='msvcrt.lib oldnames.lib' > > > --host_extralibs='' --toolchain=msvc && make -j`nproc` && make -j`nproc` > > > run-checkasm && make -j`nproc` fate-rsync && make -j`nproc` fate > > > > > > Here is exactly the same pipeline with removed graph.{html,css} > > > https://github.com/kasper93/FFmpeg/tree/gha2 > > > https://github.com/kasper93/FFmpeg/actions/runs/15656127992 > > > Builds just fine. > > > Ignore win32 (windows-11-arm, arm64, --toolchain=msvc) failure, as this is > > > affected by unrelated regression in dxvenc.c on arm64 target, but the build > > > itself is passing just fine. > > > > > > Any ideas how we can restore the ability to build ffmpeg on Windows? > > > > Hi Kasper, > > > > I was able to reproduce the issue by adding a new CI build (for PRs to > > ffstaging/ffmpeg (on GitHub, not yet for Patchwork). > > > > It appears to be all about dir separators when building under MSYS2 with > > Clang. Clang insists on using backslashes (unlike GCC and MSVC) and that > > screws the Gnu make logic (pattern rules, dependency and up-to-date > > checks). > > Why is Clang involved in .css conversion rules? It seems to fail at > the `%.css.min: %.css` rule already, which shouldn't involve any C > toolchain related bits. Is this propagated from the .o file? In which > case why does the .o have "wrong" path separators? > > Isn't there an issue in vpath? Maybe we can make it somehow proper > separators. Few days I briefly looked at this, but it wasn't obvious > what would be the correct solution here. Changing vpath to extract > only files in fftools/resources was improving things, but still not > fully. > > Also vpath in fftools/resources/Makefile is setting search path in the > whole SRC_PATH, while imho it should be restricted to the > fftools/resources directory only. > > - Kacper Ok, Martin explained to me on IRC that Windows Clang is generating dependency files with backward slashes, which is then choking because Make ingest that, which when not escaped \\ makes paths all go wrong. There is no issue with llvm-mingw or alike, because Clang can be configured during compile time to output forward slashes in dep files. So, probably a solution would be to postproc .d files. But I didn't look at the issue closely, as you can see :) Or make Make work with backward slashes where needed, but this may be tricky to cover all internal matching. Dunno, just wanted to correct my previous message. - Kacper - Kacper _______________________________________________ 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".