[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]

Re: [tor-bugs] #10104 [Tor bundles/installation]: Rebase our Gitian onto latest upstream



#10104: Rebase our Gitian onto latest upstream
------------------------------------------+--------------------------------
     Reporter:  mikeperry                 |      Owner:  mikeperry
         Type:  enhancement               |     Status:  new
     Priority:  major                     |  Milestone:
    Component:  Tor bundles/installation  |    Version:
   Resolution:                            |   Keywords:  gitian,
Actual Points:                            |  MikePerry201403
       Points:                            |  Parent ID:
------------------------------------------+--------------------------------

Comment (by gk):

 Actually that is wrong. The second difference is a different CRC32
 checksum in the .gnu_debuglink section which is caused by the same build
 id in the corresponding debug file. So, the questions boil then down to:

 1) How could the different build ID get created in the first place, given
 that the contents of the libxul libs don't differ?
 2) What can we do about that problem?

 ad 1) I don't know, honestly. The default method to generate a build ID is
 SHA1 which should *not* emit different hashes given the same library
 contents.
 ad 2) A workaround is disabling the build ID in the libraries. We don't
 need it if we use the debuglink method (as well) (See:
 https://sourceware.org/gdb/onlinedocs/gdb/Separate-Debug-Files.html). This
 will be done in a different bug, though.

--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/10104#comment:7>
Tor Bug Tracker & Wiki <https://trac.torproject.org/>
The Tor Project: anonymity online
_______________________________________________
tor-bugs mailing list
tor-bugs@xxxxxxxxxxxxxxxxxxxx
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs