Date: Sat, 25 Jan 2014 12:14:06 -0800 From: Tim Kientzle <tim@kientzle.com> To: George Mitchell <george+freebsd@m5p.com> Cc: freebsd-arm ml <freebsd-arm@freebsd.org> Subject: Re: my private build RaspberryPi Image is available Message-ID: <40C89CEB-7107-416C-80EF-FC6A4B687040@kientzle.com> In-Reply-To: <52E416E0.7060204@m5p.com> References: <20140122.190031.29969140.shigeru@os-hackers.jp> <20140122.224425.103076338.shigeru@os-hackers.jp> <CALCpEUHWc_yWZZcm6pr9O2Tk3Wq-k1NRPUcSDfhwWbZQee%2Bs_g@mail.gmail.com> <20140123.085609.53072279.shigeru@os-hackers.jp> <F5A3F8BC-D48E-42EA-8FAD-B9FF2B69B9F4@kientzle.com> <52E416E0.7060204@m5p.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Jan 25, 2014, at 11:56 AM, George Mitchell <george+freebsd@m5p.com> = wrote: > On 01/25/14 14:24, Tim Kientzle wrote: >>=20 >> On Jan 22, 2014, at 3:56 PM, shigeru@os-hackers.jp wrote: >>=20 >>> Unfortunately, there are some ports which I can't compile >>> on -current FreeBSD/RaspberryPi. >>> These ports requires GCC, but gcc ports in -current does not support >>> arm/armv6. >>=20 >> Why not? Any suggestion how to fix that? >>=20 >> Tim >> [...] >=20 > For me, specifying WITH_GCC=3D"yes" in src.conf at the time I built > the world gave me a gcc that works for at least the ports I needed. > (And any port that specifies USES_GCC=3Dany). -- George That works today, but isn't a particularly good long-term answer: * Ports that demand GCC will increasingly expect something newer than = GCC 4.2. * Someday (FreeBSD 11? FreeBSD 12?) we will no longer have GCC = in-tree. So it's certainly worth exploring how to build ports that require GCC without using the in-tree GCC. Tim
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?40C89CEB-7107-416C-80EF-FC6A4B687040>