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
|
.TH "BINUTILS-CONFIG" "8" "Jan 2005" "Gentoo" "Gentoo"
.SH "NAME"
binutils-config \- manage active versions of the binutils programs
.SH "DESCRIPTION"
The \fBbinutils-config\fR script allows you to switch between different
versions of binutils when you have installed multiple copies via portage.
It also allows you to quickly manage for multiple compiling targets.
You may have 1 version of binutils active per target at a time. Multiple
targets is really only useful for those who wish to cross-compile code.
.SH "SYNOPSIS"
.B binutils-config --get-current-profile [TARGET]
.B binutils-config --list-profiles
.B binutils-config --uninstall <TARGET>
.SH "GENERIC OPTIONS"
.TP
\fBTARGET-VERSION\fR
Update the system to use the \fBTARGET-VERSION\fR of binutils.
.TP
\fB\-\-get\-current\-profile\fR (\fB\-c\fR) \fI[TARGET]\fR
Display the active profile for \fITARGET\fR. If none is specified, the
host system's \fITARGET\fR will be shown.
.TP
\fB\-\-list\-profiles\fR (\fB\-l\fR)
Show all the profiles that your system currently has installed.
.TP
\fB\-\-uninstall\fR (\fB-u\fR) <\fBTARGET\fR>
This is really for internal use only. Used to remove all traces of the
\fBTARGET\fR binutils from your system.
.SH "SPECIFIC OPTIONS"
.TP
\fB\-\-amd64\fR
A nice feature of the amd64/x86 toolchain is that each can produce code for
other. The typical user could care less, but some may want to be able to
cross-compile for an amd64 on a x86 system. This will install the extra
symlinks ('x86_64') to facilitate this process.
.TP
\fB\-\-arm\fR
The arm architecture comes in both big and little endian versions. Typically
you only need support for the native target, but sometimes it's helpful to
have links for the other endian target. This will make sure you have both the
big endian target ('armeb') and the little endian target ('arm').
.TP
\fB\-\-mips\fR
The mips architecture (like arm) comes in both big and little endian versions.
Typically you only need support for the native target, but sometimes it's
helpful to have links for the other endian target. This will make sure you
have both the big endian target ('mips') and the little endian target
('mipsel').
.TP
\fB\-\-x86\fR
One oddity of the x86 toolchain is that they may be named 'i386', or 'i486',
or 'i586', or 'i686', yet still produce the same exact code. When dealing
with distcc systems that are mixed (some i586 and some i686), you will need
symlinks for all these targets. This option will install those extra targets.
.SH "REPORTING BUGS"
Please report bugs via http://bugs.gentoo.org/
.SH "SEE ALSO"
.BR ar (1),
.BR as (1),
.BR ld (1),
.BR nm (1),
.BR objcopy (1),
.BR ranlib (1),
.BR readelf (1),
.BR strings (1),
.BR strip (1)
.SH "FILES"
.nf
.BR /usr/bin/binutils-config
.BR /etc/env.d/binutils/*
.fi
.SH "AUTHORS"
Mike Frysinger <vapier@gentoo.org>
.SH "CVS HEADER"
$Header: /var/cvsroot/gentoo-x86/sys-devel/binutils-config/files/binutils-config.8,v 1.2 2005/01/30 06:21:38 vapier Exp $
|
GitWeb