Re: Deterministic builds, part 2

On Thu, Dec 02, 2010 at 02:52:33PM +0100, Erik Cederstrand wrote: > Hi Joerg, > > Den 02/12/2010 kl. 13.49 skrev Joerg Sonnenberger: > > > On Thu, Dec 02, 2010 at 11:08:09AM +0100, Erik Cederstrand wrote: > >> I wonder if I could hack __FILE__ to be a path relative to src/. That > >> would be a w

Re: Deterministic builds, part 2

Hi Joerg, Den 02/12/2010 kl. 13.49 skrev Joerg Sonnenberger: > On Thu, Dec 02, 2010 at 11:08:09AM +0100, Erik Cederstrand wrote: >> I wonder if I could hack __FILE__ to be a path relative to src/. That >> would be a way to fix all the source file paths I see. > > I have a patch for that in NetBS

Re: Deterministic builds, part 2

On Thu, Dec 02, 2010 at 11:08:09AM +0100, Erik Cederstrand wrote: > I wonder if I could hack __FILE__ to be a path relative to src/. That > would be a way to fix all the source file paths I see. I have a patch for that in NetBSD's gcc. Joerg ___ freebsd

Re: Deterministic builds, part 2

Hi Ryan, Den 02/12/2010 kl. 05.01 skrev Ryan Stone: > asn1.c uses the assert macro, while I believe uses __FILE__. Thanks for the help! asn1.c does indeed import src/include/assert.h, which optionally uses __FILE__ if NDEBUG is not defined. I've tried adding -DNDEBUG to my CFLAGS, but apart f

Re: Deterministic builds, part 2

asn1.c uses the assert macro, while I believe uses __FILE__. ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "freebsd-hackers-unsubscr...@freebsd.org"

Re: Deterministic builds, part 2

Den 02/12/2010 kl. 03.44 skrev Ryan Stone: > Does the C file use the __FILE__ macro? There are a bit over 1000 files with checksum mismatches, but they seem to differ in the same way. I've picked an example: /usr/lib/libbsnmp.a It contains the string "/usr/home/erik/freebsd/head1/src/lib/libb

Re: Deterministic builds, part 2

Does the C file use the __FILE__ macro? ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "freebsd-hackers-unsubscr...@freebsd.org"

Re: Deterministic builds, part 2

Den 25/11/2010 kl. 13.08 skrev Erik Cederstrand: > rodata.str1.4: > -- > Some *.o files (all?) contain the path to the corresponding source file: > > Contents of section .rodata.str1.4: > 2f757372 2f686f6d 652f6572 696b2f66 /usr/home/erik/f > 0010 72656562 73642f68 6561642f

Re: Deterministic builds, part 2

Den 25/11/2010 kl. 20.17 skrev Mark Johnston: > On Thu, Nov 25, 2010 at 01:08:58PM +0100, Erik Cederstrand wrote: >> Kernel modules: >> -- >> In the ELF section .gnu-debuglink, there is a link to the corresponding >> *.ko.symbols file. It seems to be an inode or such rather t

Re: Deterministic builds, part 2

On Thu, Nov 25, 2010 at 01:08:58PM +0100, Erik Cederstrand wrote: > Kernel modules: > -- > In the ELF section .gnu-debuglink, there is a link to the corresponding > *.ko.symbols file. It seems to be an inode or such rather than a file path > since nothing shows up in strings(1

Re: Deterministic builds, part 2

Den 25/11/2010 kl. 13.08 skrev Erik Cederstrand: > Symbol tables: > > For example, libstand.a shows up in a diff. Looking with objdump, I see the > contained _setjmp.o file has the following symbol table: > > SYMBOL TABLE: > ldf *ABS* > /usr/home/eri

Deterministic builds, part 2

Hello hackers, With a simple version of deterministic builds done (see my previous post here - anyone willing to comment the patch?), I have started to look at the more general case where OBJDIR and SRCDIR change between builds. The following are my findings. Kernel modules: -