Closed tchaikov closed 4 months ago
Which OS is this on? It builds fine for me with GCC 14.1.1_p20240622 on Gentoo.
@maharmstone hi Mark, i am building on fedora rawhide .
@maharmstone hi Mark, i am building on fedora rawhide .
Thanks. This is weird - I've tried it in the rawhide Docker image, and it works there too [g++ (GCC) 14.1.1 20240701 (Red Hat 14.1.1-7)]. Is there something screwy with your installation?
probably, i am using the latest rawhide. see https://download.copr.fedorainfracloud.org/results/tchaikov/fmt-11/fedora-rawhide-aarch64/07740392-ntfs2btrfs/builder-live.log.gz and https://download.copr.fedorainfracloud.org/results/tchaikov/fmt-11/fedora-rawhide-x86_64/07740392-ntfs2btrfs/builder-live.log.gz .
but anyhow, i think it's more resilient to include the header for using the symbols declared by it instead of relying on another (random) header to do this for us.
Thanks. I agree, I just want to make sure that this sort of thing gets picked up by CI if at all possible. It looks like we were including \<memory> transitively through libfmt.
Committed as https://github.com/maharmstone/ntfs2btrfs/commit/4375a142fe635044fe54e0c897bdc2bd07225d97, thank you
when building with libstdc++ from GCC-14, we have
so include accordingly.