Date: Mon, 5 Aug 2013 14:53:12 -0700 From: John-Mark Gurney <jmg@funkthat.com> To: Tom Everett <tom@khubla.com> Cc: "freebsd-arm@freebsd.org" <arm@freebsd.org>, Ian Lepore <ian@freebsd.org> Subject: Re: problem compiling libgcrypt from ports Message-ID: <20130805215312.GF94127@funkthat.com> In-Reply-To: <CAB3ij4AMTdjSzGY%2BoNhhs9e5HZQmSsLNd3fawVjeEZpX%2BnLGSw@mail.gmail.com> References: <CAB3ij4Adknrr5yOrLLghesC0wgV6rq5dEy_jbZQam_vC9a3SyA@mail.gmail.com> <1375710734.3320.1.camel@revolution.hippie.lan> <CAB3ij4DoC-hr6zXGK=KX5t825LKYxJr53ppx6E%2B3R5vUEvH1hw@mail.gmail.com> <1375712325.3320.3.camel@revolution.hippie.lan> <CAB3ij4AMTdjSzGY%2BoNhhs9e5HZQmSsLNd3fawVjeEZpX%2BnLGSw@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Tom Everett wrote this message on Mon, Aug 05, 2013 at 09:53 -0600:
> oh i see. thanks!
it's that the port uses cc which defaults to clang, not gcc... gcc
and clang binaries are installed independent of what cc is set to...
assuming you build clang, etc...
> On Mon, Aug 5, 2013 at 8:18 AM, Ian Lepore <ian@freebsd.org> wrote:
>
> > On Mon, 2013-08-05 at 07:54 -0600, Tom Everett wrote:
> > > ok, I'll give that a try. Just FYI, it seems that my current gcc version
> > > is 4.2.1, so I'd be asking to compile with an older gcc?
> > >
> >
> > You're not compiling with gcc at all right now; those error messages you
> > posted are clang errors (it's complaining that it doesn't support a
> > particular gcc-specific extension).
--
John-Mark Gurney Voice: +1 415 225 5579
"All that I will do, has been done, All that I have, has not."
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20130805215312.GF94127>