Sorry for the late reply, domain issue affected my email reception. The macros
don't change between F36 and F37; I've filed
https://gitlab.kitware.com/cmake/cmake/-/issues/23334 to see if upstream can
shed a light on this.
--
Michel
___
devel mailing
On Wed, 2022-03-16 at 07:17 -0700, Thomas Rodgers wrote:
> One more package that FTBFS due to CMake issues -
>
> grive2: FTBFS # Error: /builddir/build/BUILD/grive2-0.5.1/redhat-
> linux-build is not a directory
remove the dot and I bet that will work
>
> On Mon, Mar 14, 2022 at 2:22 PM Thoma
One more package that FTBFS due to CMake issues -
grive2: FTBFS # Error:
/builddir/build/BUILD/grive2-0.5.1/redhat-linux-build is not a directory
On Mon, Mar 14, 2022 at 2:22 PM Thomas Rodgers wrote:
>
>
>
> On Mon, Mar 14, 2022 at 4:37 AM Jonathan Wakely
> wrote:
>
>> On Fri, 4 Mar 2022 at
On Monday, March 14, 2022 10:22:19 PM CET Thomas Rodgers wrote:
> These are the CMake related issues I've encountered thus far -
>
> FlightCrew: FTBFS # CMake Error: The source directory
> "/builddir/build/BUILD/FlightCrew-0.9.1/build" does not appear to contain
> CMakeLists.txt.
> csdiff: FTBF
On Tuesday, March 15, 2022 12:18:02 AM CET Neal Gompa wrote:
> I bent over backwards to get the macros working all the way back to EPEL 7.
>
> I updated the cmake3 package in EPEL 7[1] and I got RHEL to update
> CMake[2] and sync the macros from Fedora[3] for RHEL 8.
>
> The only difference for E
On Fri, Mar 11, 2022 at 5:33 PM Fabio Valentini wrote:
>
> On Fri, Mar 11, 2022 at 11:15 PM Michel Alexandre Salim
> wrote:
> >
> > If you mean the Fedora 33 change page, it only describes the change
> > from Fedora 33+ perspective. It does not take compatibility with EPEL
> > buildroots into ac
On Mon, Mar 14, 2022 at 4:37 AM Jonathan Wakely wrote:
> On Fri, 4 Mar 2022 at 14:26, Steven A. Falco
> wrote:
> >
> > There is a new FTBFS for KiCad [1]. I filed an issue with KiCad [2] and
> got a comment from the project leader:
> >
> > This looks like cmake issue to me. For some reason
On Fri, 4 Mar 2022 at 14:26, Steven A. Falco wrote:
>
> There is a new FTBFS for KiCad [1]. I filed an issue with KiCad [2] and got
> a comment from the project leader:
>
> This looks like cmake issue to me. For some reason cmake is creating an
> incorrect build folder:
>
> -- Build f
V Fri, Mar 11, 2022 at 11:32:51PM +0100, Fabio Valentini napsal(a):
> On Fri, Mar 11, 2022 at 11:15 PM Michel Alexandre Salim
> wrote:
> >
> > On Fri, Mar 04, 2022 at 09:26:04AM -0500, Steven A. Falco wrote:
> > > There is a new FTBFS for KiCad [1]. I filed an issue with KiCad [2] and
> > > got
Fabio Valentini wrote:
> Also related, as far as I know, Neal put great effort into making the
> macros work almost exactly the same on both Fedora and EPEL.
> So I think that statement is incorrect.
(An ancient version of) CMake is part of RHEL proper though.
And, while a lot of work has been pu
On Fri, Mar 11, 2022 at 11:15 PM Michel Alexandre Salim
wrote:
>
> On Fri, Mar 04, 2022 at 09:26:04AM -0500, Steven A. Falco wrote:
> > There is a new FTBFS for KiCad [1]. I filed an issue with KiCad [2] and
> > got a comment from the project leader:
> >
> > This looks like cmake issue to me
On Fri, Mar 04, 2022 at 09:26:04AM -0500, Steven A. Falco wrote:
> There is a new FTBFS for KiCad [1]. I filed an issue with KiCad [2] and got
> a comment from the project leader:
>
> This looks like cmake issue to me. For some reason cmake is creating an
> incorrect build folder:
>
This i
On Tuesday, March 8, 2022 12:13:33 AM CET Sérgio Basto wrote:
> I advise anyone to carefully read the wiki page.
If you mean the Fedora 33 change page, it only describes the change
from Fedora 33+ perspective. It does not take compatibility with EPEL
buildroots into account at all.
Kamil
_
Hi,
On Fri, 2022-03-04 at 18:07 +0100, Kamil Dudka wrote:
> On Friday, March 4, 2022 4:17:01 PM CET Sérgio Basto wrote:
> > I think you missed the
> > https://fedoraproject.org/wiki/Changes/CMake_to_do_out-of-source_builds
>
> When the change landed, I had to fix all my packages to build althoug
On Friday, March 4, 2022 4:17:01 PM CET Sérgio Basto wrote:
> I think you missed the
> https://fedoraproject.org/wiki/Changes/CMake_to_do_out-of-source_builds
When the change landed, I had to fix all my packages to build although they
had been using out of source builds since the beginning. Now
> On 3/4/22 10:17 AM, Sérgio Basto wrote:
> I think you missed the
> https://fedoraproject.org/wiki/Changes/CMake_to_do_out-of-source_builds
> (Targeted release: Fedora 33 ) and
> https://docs.fedoraproject.org/en-US/packaging-guidelines/CMake/
I did not.
CMake in-source / out-of-source building i
On 3/4/22 10:17 AM, Sérgio Basto wrote:
On Fri, 2022-03-04 at 16:04 +0100, Michal Schorm wrote:
On Fri, Mar 4, 2022 at 3:40 PM Sérgio Basto wrote:
The fix is just remove "\ ." (the dot) on %cmake
That isn't a fix, that's a workaround for a broken CMake - atleast
that I believe, as y
On Fri, 2022-03-04 at 16:04 +0100, Michal Schorm wrote:
> On Fri, Mar 4, 2022 at 3:40 PM Sérgio Basto wrote:
> > The fix is just remove "\ ." (the dot) on %cmake
>
> That isn't a fix, that's a workaround for a broken CMake - atleast
> that I believe, as you can read in that BZ.
> I haven
On Fri, Mar 4, 2022 at 3:40 PM Sérgio Basto wrote:
> The fix is just remove "\ ." (the dot) on %cmake
That isn't a fix, that's a workaround for a broken CMake - atleast
that I believe, as you can read in that BZ.
I haven't found anything on CMake upstream that would suggest such
change i
On Fri, 2022-03-04 at 09:26 -0500, Steven A. Falco wrote:
> There is a new FTBFS for KiCad [1]. I filed an issue with KiCad [2]
> and got a comment from the project leader:
>
> This looks like cmake issue to me. For some reason cmake is
> creating an incorrect build folder:
>
> -- Buil
FTR there are more issues, e.g.:
https://bugzilla.redhat.com/show_bug.cgi?id=2057738
--
Michal Schorm
Software Engineer
Core Services - Databases Team
Red Hat
--
On Fri, Mar 4, 2022 at 3:27 PM Steven A. Falco wrote:
>
> There is a new FTBFS for KiCad [1]. I filed an issue with KiCad [2] and
There is a new FTBFS for KiCad [1]. I filed an issue with KiCad [2] and got a
comment from the project leader:
This looks like cmake issue to me. For some reason cmake is creating an
incorrect build folder:
-- Build files have been written to: /builddir/build/BUILD/kicad-6.0.2
so
22 matches
Mail list logo
