The GNU Binutils are a collection of binary tools. The main ones are:
* ld - the GNU linker.
* as - the GNU assembler.
Most of these programs use BFD, the Binary File Descriptor library, to do
low-level manipulation. Many of them also use the opcodes library to assemble
and disassemble machine instructions.
This port may be used as a replacement for the system binutils and support
features from the latest versions of GCC.
For cross-compilation, see the devel/cross-binutils port.
WWW: https://www.gnu.org/software/binutils/
===> The following configuration options are available for avr-binutils-2.32_1,1:
RELRO=off: enable -z relro in ELF linker by default
STATIC=off: Build static executables and/or libraries
===> Use 'make config' to modify these settings
Update binutils to 2.33.1
While here, convert binutils into flavors, that ease a lot maintenance
and helps cleaning out the code.
This is inspired by the same work on going on the xtoolchained gcc by jhb@
PR: 241756
Exp-run: antoine (portmgr)
Discussed with: jhb
Differential Revision: https://reviews.freebsd.org/D22258
Update to 2.27
Remove aarch64 patches which are now upstream
Disable new x86 relocation to avoid incompatibilities with the old base binutils
Activate all targets on the default binutils (requested by royger@)
Add a RELRO option (default off) to be able to define the default behaviour of
ld(1) on passing or not -z relro
Reorganize the avr-binutils port to use the central binutils one
(as the various arm*binutils ports are doing, too).
Add a patch to recognize the "avrtiny" architecture MCUs (ATtiny10
et al.), extracted from the Atmel AVR Toolchain 3.4.5 (they still
didn't push it upstream, alas).
Force numerous ports that fail to build with clang over to instead always
rely on gcc. The patch uses the new USE_GCC=any code in Mk/bsd.gcc.mk to
accomplish this.
The ports chosen were ports that blocked 2 or more ports from building with
clang. (There are several hundred other ports that still fail to build with
clang, even with this patch. This is merely one step along the way.)
Those interested in fixing these ports with clang, and have clang as their
default compiler, can simply set FORCE_BASE_CC_FOR_TESTING=yes.
For those who have gcc as their default compiler, this change is believed
to cause no change.
Hat: portmgr
Tested with: multiple runs on amd64-8-exp-bcm and 9-exp-clang, with various
combinations of patch/no-patch and flag settings.
Upgrade to binutils 2.20.1.
Completely reorganize the patches for this port.
Patches for new devices are now synchronized with the Atmel AVR tools.
The main difference is the naming scheme, as FreeBSD patches start
with "patch-", while the Atmel AVR Tools patches end up in ".patch".
- Add LDFLAGS to CONFIGURE_ENV and MAKE_ENV (as it was done with LDFLAGS)
- Fix all ports that add {CPP,LD}FLAGS to *_ENV to modify flags instead
PR: 157936
Submitted by: myself
Exp-runs by: pav
Approved by: pav
Incorporate the ATxmega patch from WinAVR.
Silense an assembler warning that triggered too frequently on
legitimate code (binutils bug 5523).
Make $DATA_ORIGIN a configurable value within the linker script
templates.
Add support for ATtiny88, ATmega32HVB, ATmega1284P.
Fix support for AT90USB82/162, move them into "avr35" architecture.
Add basic support for fuse and lock bit sections in ELF file.
Fix a compiler warning in the AVR-COFF generator that appeared with
GCC 4.x, and caused the compilation to fail due to the -Werror option
used.
Remove an annoying assembler warning in the ATmega256x patch that was
frequently triggered by large C switch() statements in GCC, and
generally considered to be a regression. The author of that patch
agreed that the warning isn't particularly useful anyway for a number
of reasons, and recommended to just drop it.
Update the description to match the reality:
. we are based on binutils-2.17 now
. most of the AVRs are now supported by the stock distribution of
binutils now, so update our local additions
Mass-conversion to the USE_AUTOTOOLS New World Order. The code present
in bsd.autotools.mk essentially makes this a no-op given that all the
old variables set a USE_AUTOTOOLS_COMPAT variable, which is parsed in
exactly the same way as USE_AUTOTOOLS itself.
Moreover, USE_AUTOTOOLS has already been extensively tested by the GNOME
team -- all GNOME 2.12.x ports use it.
Preliminary documentation can be found at:
http://people.FreeBSD.org/~ade/autotools.txt
which is in the process of being SGMLized before introduction into the
Porters Handbook.
Light blue touch-paper. Run.
Remove individual patches for adding new AVR devices to the toolchain,
and combine them into a single unified patch, as only two files need
to be patched anyway.
This will extend support of avr-binutils (over stock binutils-2.16) to
the following AVR devices:
ATtiny25/45/85
AT90PWM2/3
ATmega164/324/644
ATmega329/3290/649/6490
ATmega640/1280/1281
Merge some patches that have meanwhile be integrated in binutil's CVS,
and apply them to the latest released version (2.15). This mainly
adds support for new AVR devices that appeared on the market recently,
and fixes one relocation bug for the EEPROM section that could be
noted when a bootloader section is also present.
Apply a big libtool patch to allow porters to use the libtool installed by
the libtoolX ports instead of the one included with each port. Ports that
set USE_LIBTOOL_VER=X will now use the ports version of libtool instead of
the included version. To restore previous behavior, use the new macro,
USE_INC_LIBTOOL_VER. Both macros accept the same argument: a libtool version.
For example, to use the ports version of libtool-1.5, add the following to
your Makefile:
USE_LIBTOOL_VER= 15
To use the included version of libtool with extra hacks provided by
libtool-1.5, add the following to your Makefile:
USE_INC_LIBTOOL_VER= 15
With this change, ports that had to add additional libtool hacks to prevent
.la files from being installed or to fix certain threading issues can now
delete those hacks (after appropriate testing, of course).
PR: 63944
Based on work by:eik and marcus
Approved by: ade (autotools maintainer)
Tested by: kris on pointyhat
Bound to be hidden problems: You bet
Upgrade to binutils 2.15.
Also fixed is the way the tweak for amd64 -> x86_64 is done, and
Manuel Stuehn <manuel dot stuehn at gmx dot net> verified it is OK
on that architecture now.
Whoa there, boy, that's a mighty big commit y'all have there...
Begin autotools sanitization sequence by requiring ports to explicitly
specify which version of {libtool,autoconf,automake} they need, erasing
the concept of a "system default".
For ports-in-waiting:
USE_LIBTOOL=YES -> USE_LIBTOOL_VER=13
USE_AUTOCONF=YES -> USE_AUTOCONF_VER=213
USE_AUTOMAKE=YES -> USE_AUTOMAKE_VER=14
Ports attempting to use the old style system after June 1st 2004 will be
sorely disappointed.
Update to binutils 2.14.
Also included now the "AVR COFF beta" patch that allows avr-objcopy to
generate AVR (extended) COFF files. Note the beta state (which only
affects this conversion though).
This commit also fixes a minor pkg-plist problem noticed by kris.
Mega-upgrade the AVR GNU utils toolchain, part #1:
Upgrade binutils to a recent snapshot, since this is a prerequisite
for the remaining ports.
Unfortunately, sources.redhat.com frequently purges older snapshot
tarballs, thus i gotta keep the one to use here around privately.
Do not, never, nikogda install lib{bfd,opcodes,iberty}.a. They might clash
with other binutils ports for different targets, and are not needed to be
installed at all.