binutils-config.8 2.6 KB

1234567891011121314151617181920212223242526272829303132333435363738394041424344454647484950515253545556575859606162636465666768697071727374
  1. .TH "BINUTILS-CONFIG" "8" "Jan 2005" "Gentoo" "Gentoo"
  2. .SH "NAME"
  3. binutils-config \- manage active versions of the binutils programs
  4. .SH "DESCRIPTION"
  5. The \fBbinutils-config\fR script allows you to switch between different
  6. versions of binutils when you have installed multiple copies (see
  7. USE=multislot). It also allows you to manage multiple cross-compiling
  8. targets simultaneously.
  9. Remember, you may have one version of binutils active per \fICTARGET\fR,
  10. and changing the version for one target has no bearing on any other. So
  11. changing an active cross-compiler will not break your native compiler
  12. (i.e. \fICHOST\fR).
  13. .SH "SYNOPSIS"
  14. \fBbinutils-config\fR [\fIcrufty options\fR] \fIPROFILE\fR
  15. \fBbinutils-config\fR \fB--get-current-profile\fR \fI[TARGET]\fR
  16. \fBbinutils-config\fR \fB--list-profiles\fR
  17. \fBbinutils-config\fR \fB--uninstall\fR \fITARGET\fR
  18. .SH "GENERIC OPTIONS"
  19. .TP
  20. \fBPROFILE\fR
  21. Change the system to use the specified binutils version. This may take the
  22. form of the list index number (the number shown on the left in the
  23. \fB\-\-list\-profiles\fR output), a full \fITARGET-VERSION\fR (useful when
  24. working with cross-compilers), just a \fITARGET\fR where the \fIVERSION\fR
  25. is picked from the active, or just a binutils \fIVERSION\fR where the
  26. \fITARGET\fR is assumed to be the native \fIHOST\fR value.
  27. .TP
  28. \fBTARGET\fR
  29. Similiar to \fBPROFILE\fR, but this is only the target and no version info
  30. (i.e. \fICTARGET\fR or \fICHOST\fR).
  31. .TP
  32. \fB\-c\fR, \fB\-\-get\-current\-profile\fR \fI[TARGET]\fR
  33. Display the active profile for \fITARGET\fR. If none is specified, the
  34. host system's \fITARGET\fR will be shown (i.e. \fICHOST\fR).
  35. .TP
  36. \fB\-l\fR, \fB\-\-list\-profiles\fR
  37. Show all the profiles that your system currently has installed and what
  38. versions are active. The active native version is noted with a bright green
  39. asterisk while the active cross-compiler versions are noted with a light blue
  40. asterisk.
  41. .TP
  42. \fB-u\fR, \fB\-\-uninstall\fR \fITARGET\fR
  43. This is really for internal use only. Used to remove all traces of the
  44. \fITARGET\fR binutils from your system.
  45. .SH "CRUFTY OPTIONS"
  46. .TP
  47. \fB\-\-linker\fR \fB<linker>\fR
  48. Change the default linker for the specified \fIPROFILE\fR to the \fB<linker>\fR.
  49. Common names are \fBld.gold\fR for the newer gold linker and \fBld.bfd\fR for
  50. the classic linker. Note that not all targets support the gold linker.
  51. .SH "REPORTING BUGS"
  52. Please report bugs via https://bugs.gentoo.org/
  53. .SH "SEE ALSO"
  54. .BR ar (1),
  55. .BR as (1),
  56. .BR ld (1),
  57. .BR nm (1),
  58. .BR objcopy (1),
  59. .BR ranlib (1),
  60. .BR readelf (1),
  61. .BR strings (1),
  62. .BR strip (1)
  63. .SH "FILES"
  64. .nf
  65. .BR /usr/bin/binutils-config
  66. .BR /etc/env.d/binutils/*
  67. .fi
  68. .SH "AUTHORS"
  69. Mike Frysinger <vapier@gentoo.org>