Test plan: <http://overlays.gentoo.org/proj/emacs/wiki/test%20plans> @ppc: New stabilisation for you, so as usual, you may remove yourself from CC. Thanks in advance.
The package doesn't respect the ldflags * QA Notice: Files built without respecting LDFLAGS have been detected * Please include the following list of files in your report: * /usr/bin/teachjove * /usr/bin/jove * /usr/lib/jove/recover
(In reply to comment #1) > The package doesn't respect the ldflags > > * QA Notice: Files built without respecting LDFLAGS have been detected > * Please include the following list of files in your report: > > * /usr/bin/teachjove > * /usr/bin/jove > * /usr/lib/jove/recover Sorry, but I cannot follow. Is that related to version 4.16.0.73? From my build.log, it appears that LDFLAGS are honoured: gcc -O -Wl,-O1 -Wl,--as-needed -march=core2 -ggdb -O2 -pipe -o teachjove teachjove.o gcc -O -Wl,-O1 -Wl,--as-needed -march=core2 -ggdb -O2 -pipe -o recover recover.o gcc -O -Wl,-O1 -Wl,--as-needed -march=core2 -ggdb -O2 -pipe -o jjove commands.o keys.o argcount.o ask.o buf.o jctype.o delete.o disp.o insert.o io.o jove.o marks.o misc.o re.o screen.o termcap.o unix.o util.o vars.o list.o keymaps.o mouse.o abbrev.o rec.o paragraph.o fmt.o c.o wind.o fp.o move.o extend.o macros.o iproc.o reapp.o proc.o scandir.o term.o case.o -lncurses
Yes Apparently some of the object files that get linked all together to build the final binaries have been built without your LDFLAGS. I assume you are looking at the wrong place in the build.log Look at these lines: x86_64-pc-linux-gnu-gcc -Wall -ggdb -march=amdfam10 -O2 -pipe -DSYSVR4 -_XOPEN_SOURCE=500 -c -o case.o case.c x86_64-pc-linux-gnu-gcc -Wall -ggdb -march=amdfam10 -O2 -pipe -DSYSVR4 -D_XOPEN_SOURCE=500 -c -o recover.o recover.c x86_64-pc-linux-gnu-gcc -Wall -ggdb -march=amdfam10 -O2 -pipe -DSYSVR4 -D_XOPEN_SOURCE=500 -c -o teachjove.o teachjove.c x86_64-pc-linux-gnu-gcc -Wall -ggdb -march=amdfam10 -O2 -pipe -DSYSVR4 -D_XOPEN_SOURCE=500 -c -o portsrv.o portsrv.c See? These object files are built without my/your LDFLAGS so when they link together to produce the final binary you get warnings about the missing LDFLAGS
Markos, however i try to reproduce your non-respected LDFLAGS i cant. Please try to cleanup all temp files, update to latest portage and try again :) Tested on 2 stable boxes (amd64 and x86) + my dev amd64 system, good to go i would say.
That was an error on my end ( what a surprise ) amd64 done
x86 stable
ppc stable, closing