Bug#1059706: epics-base.pc is still broken

[Andrius Merkys]

Hi,

On Sat, 4 May 2024 22:53:36 +0900 Kentaro HAYASHI <ken...@xdump.org> wrote:
I've attached PoC patches which are
based on https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1059706#33
Before:

  $ pkg-config --cflags epics-base
-I/build/reproducible-path/epics-base-7.0.8+dfsg1/include
-I/build/reproducible-path/epics-base-7.0.8+dfsg1/include/os/Linux
-I/build/reproducible-path/epics-base-7.0.8+dfsg1/include/compiler/gcc
-D_GNU_SOURCE -D_DEFAULT_SOURCE -D_X86_64_ -DUNIX -Dlinux
-ffile-prefix-map=/build/reproducible-path/epics-base-7.0.8+dfsg1=.
-D_FORTIFY_SOURCE=2
-ffile-prefix-map=/build/reproducible-path/epics-base-7.0.8+dfsg1=.
-fstack-protector-strong -fstack-clash-protection -fcf-protection
-D_FORTIFY_SOURCE=2 -mtune=generic -m64 

After:

  $ pkg-config --cflags epics-base
-I/usr/include/epics -I/usr/include/epics/os/Linux
-I/usr/include/epics/compiler/gcc -D_GNU_SOURCE -D_DEFAULT_SOURCE
-D_X86_64_ -DUNIX -Dlinux
-ffile-prefix-map=/debian/epics-base-7.0.8+dfsg1=. -D_FORTIFY_SOURCE=2
-ffile-prefix-map=/debian/epics-base-7.0.8+dfsg1=.
-fstack-protector-strong -fstack-clash-protection -fcf-protection
-D_FORTIFY_SOURCE=2 -mtune=generic -m64 

I hope it will help.

This looks good indeed. I will give your patch another look and apply 
it. While you are at the epics-base.pc, can you check why all buildflags 
get stored in it?

Best,
Andrius