Has been in the tree for months, no reported problems.
Please remove -ggdb3 from CFLAGS: /bin/sh ../libtool --tag=CC --mode=link x86_64-pc-linux-gnu-gcc -I../include/ntfs-3g -march=native -O2 -g0 -Wall -ggdb3 -DDEBUG -Wl,-O1 -Wl,--as-needed -Wl,--hash-style=gnu -o ntfs-3g.probe ntfs_3g_probe-ntfs-3g.probe.o ../libntfs-3g/libntfs-3g.la And please provide to a static-libs USE; from qlist $package /usr/lib64/libntfs-3g.a /usr/lib64/libntfs-3g.so /usr/lib64/libntfs-3g.la Please remove also .la file.
I removed the .la files and added a static-libs USE flag. The -ggdb3 is only in the CFLAGS with USE=debug, it's enabled by the upstream configure script with --enable-debug. I would rather follow upstream on this then maintaining a local patch to remove this logic.
(In reply to comment #2) > I removed the .la files and added a static-libs USE flag. > Good job ;) > The -ggdb3 is only in the CFLAGS with USE=debug, it's enabled by the upstream > configure script with --enable-debug. I would rather follow upstream on this > then maintaining a local patch to remove this logic. Anyway any useflags mustn't modify cflags environment.
@Agostino - With my limited ebuild knowledge, looking through it, the debug USE flag doesn't modify the CFLAGS, it seems the configure script modifies the CFLAGS which is perfectly normal. I'm not an official AT nor do i have any clue what i'm doing, but i'm going to consider this to not be an issue, personally at least.
@JD I meant that any USE, like also debug must not append -g/-ggdb via obvioulsy $(use_enable $USE) that modify configure script at configure time.
(In reply to comment #5) > @JD > > I meant that any USE, like also debug must not append -g/-ggdb via obvioulsy > $(use_enable $USE) that modify configure script at configure time. ah, gotcha. I'm still learning. sorry :)
Archtested on x86: Everything fine
amd64 done. Thank you all
x86 stable, thanks JD
ppc stable
ppc64 done
