Date: Wed, 19 Feb 2014 19:08:12 -0800 From: Steve Kargl <sgk@troutmask.apl.washington.edu> To: hiren panchasara <hiren.panchasara@gmail.com> Cc: freebsd-current <freebsd-current@freebsd.org> Subject: Re: Help fixing clang 3.4 Message-ID: <20140220030812.GA49876@troutmask.apl.washington.edu> In-Reply-To: <CALCpEUExO=pWZGoyVK9=cEzyLOWTBMO4577sVP8yX80vv13naw@mail.gmail.com> References: <20140220011939.GA49492@troutmask.apl.washington.edu> <CALCpEUExO=pWZGoyVK9=cEzyLOWTBMO4577sVP8yX80vv13naw@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, Feb 19, 2014 at 06:24:07PM -0800, hiren panchasara wrote: > On Wed, Feb 19, 2014 at 5:19 PM, Steve Kargl > <sgk@troutmask.apl.washington.edu> wrote: > > Can someone point to where I disable clang from > > issuing an error and aborting on an unknown option? > > > > % cd /usr/ports/databases/py-sqlite3 > > % make > > > > cc ... -R/usr/local/lib -lsqlite3 -o build/lib.freebsd-11.0-CURRENT-amd64-2.7/_sqlite3.so > > cc: error: unknown argument: '-R/usr/local/lib' > > I do not know the answer but I see it being discussed here: > http://lists.freebsd.org/pipermail/freebsd-toolchain/2014-January/001103.html > Sigh, I forgot about that discussion. Nothing like getting caught by the libc++ ABI breakage and unbreakage, which is requiring a recompile of everything linked to libc++, only to be foiled by the impossibility of actually doing the recompile. Guess I'll chalk it up to The Joys of Current(tm). -- Steve
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20140220030812.GA49876>