1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
|
[[!meta copyright="Copyright © 2007, 2008, 2010, 2011 Free Software Foundation,
Inc."]]
[[!meta license="""[[!toggle id="license" text="GFDL 1.2+"]][[!toggleable
id="license" text="Permission is granted to copy, distribute and/or modify this
document under the terms of the GNU Free Documentation License, Version 1.2 or
any later version published by the Free Software Foundation; with no Invariant
Sections, no Front-Cover Texts, and no Back-Cover Texts. A copy of the license
is included in the section entitled [[GNU Free Documentation
License|/fdl]]."]]"""]]
[[!tag stable_URL open_issue_binutils]]
Here's what's to be done for maintaining GNU Binutils.
As these tools primarily deal with low-level parts of the target architecture
and the object file format (ELF ABI), which are essentially (at least meant to
be) the same, there shouldn't be many differences comparing the binutils
between the GNU/Hurd and GNU/Linux ports, for example. There are a few,
though, as explained below.
[[!toc levels=2]]
# [[General information|/binutils]]
# [[Sources|source_repositories/binutils]]
# Configuration
Last reviewed up to the [[Git mirror's 31fd5921fbb68f2b5ca4ca416cb5f5f7657b3f4d
(2011-09-04) sources|source_repositories/binutils]].
* Globally
* a.out, COFF, PE image support and 64 bit support are not interesting.
* In the testsuites, `.exp` and `.d` files very likely should not only
care for `*-*-linux*`, but also `*-*-gnu*`. (If the need to be
conditionalized like this at all.)
* `bfd/`
* `config.bfd`
* `i[3-7]86-*-gnu*`
Comparing to `i[3-7]86-*-linux-*`:
* `i386linux_vec` -- a.out.
* `i386pei_vec` -- PE.
* 64 bit.
* `configure.host`
Souldn't need anything. x86 Linux neither.
* `configure.in`
Linux:
* `COREFILE=trad-core.lo` with `TRAD_HEADER='"hosts/i386linux.h"'`
We don't have any such core file support configured. TODO: should
we? Where is this core file reading exactly used? GDB?
* `i386linux_vec` -- a.out.
* `i386pei_vec` -- PE.
* `binutils/`
* `configure.tgt`
* `gas/`
* `config/te-gnu.h`
C.f. `te-linux.h`; search tree for `TE_LINUX` vs. `TE_GNU` usage.
* `tc-i386.h`
Sole `TE_LINUX` usage is for a.out.
* `configure.tgt`
* `ld/`
* `configure.host`
* `*-*-gnu*`
TODO: resolve `crt0.o` vs. `crt1.o` issue. [[Testsuite
failures|binutils#static]].
* `configure.tgt`
* `i[3-7]86-*-gnu*`
Compare to `i[3-7]86-*-linux-*`, but don't need a.out (`i386linux`)
and 64 bit support.
# Build
Here's a log of a binutils build run; this is from our [[Git repository's
6f6a8f5b0176a3e5a8fdd80627d2422831738c7e (2011-09-04)
sources|source_repositories/binutils]], run on kepler.SCHWINGE and
coulomb.SCHWINGE.
$ export LC_ALL=C
$ ../master/configure --prefix="$PWD".install SHELL=/bin/dash CC=gcc-4.6 CXX=g++-4.6 2>&1 | tee log_build
[...]
$ make 2>&1 | tee log_build_
[...]
Different hosts may default to different shells and compiler versions; thus
harmonized.
This takes up around 110 MiB, and needs roughly 4 min on kepler.SCHWINGE and
15 min on coulomb.SCHWINGE.
## Analysis
x86 GNU/Linux' and GNU/Hurd's configurations are slightly different, thus mask
out most of the differences that are due to GNU/Linux supporting more core file
formats, and more emulation vectors.
$ diff -wu <(ssh kepler.SCHWINGE 'cd tmp/source/binutils/ && cat hurd/master.build/log_build* | sed -e "s%\(/media/data\)\?${PWD}%[...]%g"' | sed -f open_issues/binutils/log_build-linux.sed) <(ssh coulomb.SCHWINGE 'cd tmp/binutils/ && cat hurd/master.build/log_build* | sed -e "s%\(/media/erich\)\?${PWD}%[...]%g"' | sed -f open_issues/binutils/log_build-hurd.sed) > open_issues/binutils/log_build.diff
[[log_build.diff]].
# Install
$ make install 2>&1 | tee log_install
[...]
This takes up around 70 MiB, and needs roughly 1 min on kepler.SCHWINGE and 5
min on coulomb.SCHWINGE.
## Analysis
$ diff -wu <(ssh kepler.SCHWINGE 'cd tmp/source/binutils/ && cat hurd/master.build/log_install | sed -e "s%\(/media/data\)\?${PWD}%[...]%g"' | sed -f open_issues/binutils/log_install-linux.sed) <(ssh coulomb.SCHWINGE 'cd tmp/binutils/ && cat hurd/master.build/log_install | sed -e "s%\(/media/erich\)\?${PWD}%[...]%g"' | sed -f open_issues/binutils/log_install-hurd.sed) > open_issues/binutils/log_install.diff
[[log_install.diff]].
* `libtool: finish`: `ldconfig` is not run for the Hurd.
# Testsuite
$ make -k check
[...]
This needs roughly 5 min on kepler.SCHWINGE and 15 min on coulomb.SCHWINGE.
$ ssh kepler.SCHWINGE 'cd tmp/source/binutils/ && cat hurd/master.build/*/*.sum hurd/master.build/*/*/*.sum | sed -e "s%\(/media/data\)\?${PWD}%[...]%g"' > open_issues/binutils/sum_linux
$ ssh coulomb.SCHWINGE 'cd tmp/binutils/ && cat hurd/master.build/*/*.sum hurd/master.build/*/*/*.sum | sed -e "s%\(/media/erich\)\?${PWD}%[...]%g"' > open_issues/binutils/sum_hurd
Comparing the results files, [[sum_linux]] to [[sum_hurd]]:
$ diff -u -F ^Running open_issues/binutils/sum_linux open_issues/binutils/sum_hurd > open_issues/binutils/sum.diff
[[open_issues/binutils/sum.diff]].
## Analysis
* <a name="static"><!-- stable_URL -->`FAIL: static [...]`</a>
The testsuite isn't prepared for using `crt0.o` instead of `crt1.o`
depending on whether a static or dynamic executable is created. Documented
in `ld/configure.host`. Perhaps we should finally rewrite this messy code
in glibc?
* <a name="64ksec">`FAIL: ld-elf/64ksec`</a>
On the idle grubber, this one takes a few minutes wall time to complete
successfully ([[I/O system
weakness|performance/io_system/binutils_ld_64ksec]]), so assuming some
system load variation, the testsuite's timeout may trigger.
* <a name="weak"><!-- stable_URL -->`FAIL: ELF weak [...]`</a>
[[I|tschwinge]] suppose this is due to us having an override w.r.t. weak
symbol handling in glibc, needed for our external [[/libpthread]]. TODO:
document properly.
|
