Skip site navigation (1)Skip section navigation (2)
Date:      Sat, 1 Jul 2006 21:55:08 +1000
From:      Peter Jeremy <peterjeremy@optushome.com.au>
To:        Mikhail Teterin <mi+kde@aldan.algebra.com>
Cc:        current@freebsd.org
Subject:   Re: weird limitation on the system's binutils
Message-ID:  <20060701115508.GC8447@turion.vk2pj.dyndns.org>
In-Reply-To: <200607010009.09231@aldan>
References:  <200607010009.09231@aldan>

next in thread | previous in thread | raw e-mail | index | archive | help

--vOmOzSkFvhd7u8Ms
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Sat, 2006-Jul-01 00:09:08 -0400, Mikhail Teterin wrote:
>I'm wondering, why the bfd and related bits and pieces of binutils are bui=
lt=20
>to support only the architecture(s), that can natively run on the system?

IMHO, the FreeBSD base system should provide tools for doing native
development - anything beyond that belongs in ports.  Given that
binutils supports quite an extensive range of targets (of thr order of
100), building them all is impractical and a waste of resources for
virtually everyone who uses FreeBSD.

>Why can't I use gdb or objdump on FreeBSD/i386 to analyze a core file, or =
a=20
>binary from another FreeBSD or even from a non-FreeBSD system?

You can if you install the relevant ports.

>The tools themselves support that. The sources (bfd-vectors) for all other=
=20
>supported architectures are part of the tree (under contrib/). So, why not=
=20
>build them?

My reading of contrib/binutils suggests that files for targets not
related to FreeBSD are in the exclude/delete list and aren't imported
into the FreeBSD repository.

>If it really is SO much of a bloat, why do we install gdb, etc. in the fir=
st=20
>place?

I'm happy with buildworld building a toolchain that supports native
development on FreeBSD.  I have used FreeBSD for cross-development and
I'm happy to manually install a toolchain to support the target I'm
developing for.  I'd be somewhat concerned if buildworld decided to
build a toolchain that supported around several targets for each of
around 100 different processors - the vast majority I'd never use.

>P.S. What I also want is the /lib/libbfd.so and friends, so I (and the 15=
=20
>devel/*binutils ports) can build my own tools linking with it. Unfortunate=
ly,=20
>that too remains impossible...

libbdf.a is built by /usr/src/gnu/usr.bin/binutils/libbfd/Makefile.
That should be a fairly simple change to arrange for it to build and
install the .so as well.

--=20
Peter Jeremy

--vOmOzSkFvhd7u8Ms
Content-Type: application/pgp-signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.3 (FreeBSD)

iD8DBQFEpmKb/opHv/APuIcRAp3zAKCvf+DrMn2O43v92eUexyxmYkNdYQCggByu
BKgPKkH1wq+wEcGEMNPJ3iQ=
=pMUw
-----END PGP SIGNATURE-----

--vOmOzSkFvhd7u8Ms--



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20060701115508.GC8447>