Which ports to install to compile gnu binutils?

Lowell Gilbert freebsd-questions-local at be-well.ilk.org
Sat Oct 17 22:35:00 UTC 2020

Christoph Kukulies <kuku at kukulies.org> writes:

>> Am 16.10.2020 um 22:11 schrieb Lowell Gilbert <freebsd-questions-local at be-well.ilk.org>:
>> Do you need that specific version?
> Yes. Reason: I „inherited“ a project from someone, who passed away and
> it is to me to continue the project. He had developed everything under
> that specific
> version of the gnu-arm toolchain. I moved everything to Unix and to be
> sure that my build environment will produce the exact same results -
> which isn’t the
> case at the moment (some instructions are assembled differently) - I’m in need of the exact version.

But not necessarily permanently; only until you can verify that another
version gives you good results. [Where "good" is for you to define based
on the project's criteria.]

>> If not, the devel/binutils port with the arm-none-eabi flavor will build
>> it for you. I can't find the user documentation for using flavors at the
>> moment, but
>> # make -C /usr/ports/devel/binutils FLAVOR=arm_none_eabi install
>> should do it, or the equivalent for your build system (e.g.
>> # portmaster devel/binutils at arm_none_eabi
>> will also work).
>> If you do need the specific version, then the (some would say optional)
>> first step is to badmouth the person forcing you to use a specific old
> :) difficult. I could stand at his grave. May God bless him.

Yeah, sounds inappropriate for this case. My sympathies to his memory.

If he were around, I'm sure you wouldn't have the problem at all.

>> version. After you've done that, you can either change the port or build
>> it by hand. Both are fairly simple: the first involves changing the
>> tarfile name in the Makefile and distinfo, while the second involves
>> unpacking the tarball and following the README instructions, which will
>> generally lead you to a 2-line command invocation.
> This gives me a little hope. 

I suspect that doing everything out-of-tree until you've verified your
changes is probably the way to go. I typically do this in my own home
directory until I'm ready to package it up for production, but that's
somewhat a matter of personal style.

The tarball you quoted has a lot more than just binutils in it; the
binutils tarball is included, but lots of other things are also. The
instructions in the top directory of it seem to cover everything,
including scripts to build it. They'll all need to be adapted slightly
(for example, they assume that the base system's /bin/sh is bash, or can
be made so), but there's a full set of build scripts included for
Ubuntu, so it's a nice start.

I'd go a little further in terms of helping, but some of the details
depend on exactly what your "real" project is like and why you can't
actually use other versions.

Be well.

More information about the freebsd-questions mailing list