Date: Wed, 07 May 2014 07:08:08 +0100 From: Matthew Seaman <matthew@FreeBSD.org> To: freebsd-questions@freebsd.org Subject: Re: oops re: What ports tree to use on a Raspberry Pi? Message-ID: <5369CDC8.4030808@FreeBSD.org> In-Reply-To: <CAOh3dDb2cCPP%2BaE_f%2B4aQ6c8WOFT%2B9CU1ZWnZHtVaaeX%2BchBkg@mail.gmail.com> References: <CAOh3dDb2cCPP%2BaE_f%2B4aQ6c8WOFT%2B9CU1ZWnZHtVaaeX%2BchBkg@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --X3UnUAnOdg5PkbPJQOI6476mJA0eBbbcO Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable On 07/05/2014 06:09, Alan Corey wrote: > OK, so that was a dumb statement that a database should have picked up > that this wouldn't build on arm (if it's a generic ports tree). Does > that mean arm needs its own ports tree? Or should I just build from > raw tarballs and not use the ports system? Ports are /required/ to be usable on Tier 1 architectures -- which are amd64 and i386 at the moment. Those are the two architectures provided by RedPorts, and what the pkg build cluster supplies at the moment. However, the way things are going this is likely to be changing: i386 popularity is waning fast, and ARM (including RasPi) is popping up everywhere. Do not expect changes in the next few days or weeks though -- there's a lot of work to do to get the ports tree into decent shape on a new Tier 1 platform. There may be discussion about what should be Tier 1 platforms and maybe even a consensus at BSDCan next week. As for your specific problem: libgcrypt doesn't require GCC 4.6 specifically -- it requires a compiler that understands the gnu89 standard, which should be *any* version of GCC. If a more recent GCC has grown support for the RasPi, that might be your way forwards. You will probably find the freebsd-ports@... list a more relevant audience for this topic. Cheers, Matthew --=20 Dr Matthew J Seaman MA, D.Phil. PGP: http://www.infracaninophile.co.uk/pgpkey --X3UnUAnOdg5PkbPJQOI6476mJA0eBbbcO Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG/MacGPG2 v2.0.20 (Darwin) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iQJ8BAEBCgBmBQJTac3QXxSAAAAAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXQ2NTNBNjhCOTEzQTRFNkNGM0UxRTEzMjZC QjIzQUY1MThFMUE0MDEzAAoJELsjr1GOGkATILwP/jqtKtWgwAtBNV4NXKTcuqgc EhSCzvLYVkwnQkHPpD6bxB3/g/i9S6gCOlA8PWrXNa/XJBIA4zOV3OGWu7FmvDy4 uA7gheAVMbB5y0l9g/SczDjd46wXFdOoOADut/WwoKEajuAEdeHMm9iEEmoMv0yi DBSU4z9JTtyVT4vZdhTKEMf771U76O6Mi0ruWBIMdlF/pBQQ+EwsWFuVhC1N8S9l aAmtAHCVW77ueLOjZz32m71llIxGRnAWO2zMS85WysSbXdveSkZv4FGF7ZHrV10O m9nT4kLPsa1rZwbduKBd4/HzzAKZEdQNIjIYJzPc84JHVfoSJBQHyapeZEvVghRm 3yBuckPTCqbexTmll6fNC1/Iw5tTm5g/ATxlqui56yuGSsMn3BvfLu2PJPKM3boi 7v2+qz3jej/J5osLIi63hbRHzdYYHazJa97zgqEvZ25VujEyqyGlFgYekFUiecgw siV9VUu3HRapN6KvQeEteD8bu6ekoVXru5r+OtAx2I7ZzYvB3BHSt+sdmxmVtakx gIN/tzGfH4WflmPFFxjVNPlNa5T6blJEqRxXNAn6xk7MXxxAA9LlI5CydaFORpy+ ZMwkyC1he8gYtvDkuUANddpCYV5XUOcNXSxuHyNrjmZ2GB+41vHLjg04Dhe0iEP6 Bz/tNv3CLs6Cojosb0dU =L8aF -----END PGP SIGNATURE----- --X3UnUAnOdg5PkbPJQOI6476mJA0eBbbcO--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?5369CDC8.4030808>