> On 2015-Mar-16, at 06:23 PM, Nathan Whitehorn <nwhiteh...@freebsd.org> wrote: > > Which compiler are you building with? Just using the normal lang/gcc works > for me without issue doing make install in lang/clang36. Are you sure you > don't have any local diffs or stale files? > -Nathan
Quoting for the "which compiler" part: "It used gcc5 to bootstrap as there was no clang present and that is the only gcc port installed". The evidence for this was watching top -PaSCHopid while it worked on the installation. As for the FBSDG5C0 SSD's 11.0-CURRENT history for compilers: gcc 4.2.1 present. clang not present. (Not 3.4.1, not 3.5, not 3.6. 3.4.1 was lost in the 10.1-STABLE -> 11.0-CURRENT conversion when I did delete-old, not realizing that I'd end up with no clang at all and no obvious way to build one on the powerpc64s/powerpcs.) (None of the below were ever on any 10.1-STABLE SSD as of when I did the copies and conversion of some to 11.0-CURRENT.) powerpc64-xtoolchain-gcc present (and so powerpc64-gcc), installed recently for the first time ever. This was the first ever not-built-into-world compiler that I've installed on any media. The powerpc64-gcc installer has a file naming problem for powerpc64 hosts I had to put copies of 5 files that it created under the names it later looked for them to finish this install (names not prefixed -> prefixed, one file copied to another place). gcc5 installed just days ago, the second ever ports-compiler installed. The install had no problems. I will note that I have started an installation of lang/clang36 on a powerpc (non-64) 11.0-CURRENT that has/had only gcc 4.2.1 and clang 3.4.1. Watching with top -PaSCHopid shows that it is doing a lang/gcc installation as part of its bootstrap, at this point that means 4.8.4. So it is not using gcc 4.2.1. Again for this SSD there is no history of compiler installs other than those that are part of world. clang 3.4.1 exists because I did not get around to doing delete-old before I noticed that I ended up with no clang as a result. This is the only copy of clang 3.4.1 that survived my ignorance to end up on 11.0-CURRENT. I have another powerpc (non-64) 11.0-CURRENT SSD that does not have powerpc64-gcc nor clang but does have gcc5 already. Again gcc5 installed in the last few days. Again before the installation there had only ever been built-into-world compilers. I've started a lang/CLANG36 install here as well. We will see how each of these goes. Side note: You can tell I got past the booting/memory-corruption problems on the G5 PowerMacs recently (via Powermac specific builds). I'm now exploring other things in FreeBSD. :) === Mark Millard markmi at dsl-only.net On 2015-Mar-16, at 06:23 PM, Nathan Whitehorn <nwhiteh...@freebsd.org> wrote: Which compiler are you building with? Just using the normal lang/gcc works for me without issue doing make install in lang/clang36. Are you sure you don't have any local diffs or stale files? -Nathan On 03/16/15 17:18, Mark Millard wrote: > Basic context (more context details listed later): > > # freebsd-version -ku; uname -ap > 11.0-CURRENT > 11.0-CURRENT > FreeBSD FBSDG5C0 11.0-CURRENT FreeBSD 11.0-CURRENT #0 r279514M: Wed Mar 11 > 19:23:14 PDT 2015 > root@FBSDG4C0:/usr/obj/powerpc.powerpc64/usr/srcC/sys/GENERIC64vtsc-NODEBUG > powerpc powerpc64 > > > The problem: > > portmaster -tDK --no-confirm lang/clang36 is how I started the build. > > The error reported was for in MSVCToolChain.cpp's member function: > > bool clang::driver::toolchains::getWindowsSDKDir(std::__cxx1:string&,int&, > int&) const > > The report was: > > MSVCToolChain.cpp:25:5: error: '::sscanf' has not been declared > ::sscanf(sdkVersion.c_str(), "v%d.%d", &major, &minor); > > > I'd be surprised if 11.0-CURRENT vs. 10.1-STABLE matters. And it not being > likely to be powerpc64 specific would be my guess. May be that it > bootstrapped via gcc5? I've not yet tried from a powerpc (non-64) FreeBSD > build. > > > > Context details: > > # svnlite info /usr/ports/lang/clang36 > Path: lang/clang36 > Working Copy Root Path: /usr/ports > URL: https://svn0.us-west.freebsd.org/ports/head/lang/clang36 > Relative URL: ^/head/lang/clang36 > Repository Root: https://svn0.us-west.freebsd.org/ports > Repository UUID: 35697150-7ecd-e111-bb59-0022644237b5 > Revision: 381120 > Node Kind: directory > Schedule: normal > Last Changed Author: brooks > Last Changed Rev: 380295 > Last Changed Date: 2015-03-02 12:21:38 -0800 (Mon, 02 Mar 2015) > > It used gcc5 to bootstrap as there was no clang present and that is the only > gcc port installed: > > # svnlite info /usr/ports/lang/gcc5 > Path: lang/gcc5 > Working Copy Root Path: /usr/ports > URL: https://svn0.us-west.freebsd.org/ports/head/lang/gcc5 > Relative URL: ^/head/lang/gcc5 > Repository Root: https://svn0.us-west.freebsd.org/ports > Repository UUID: 35697150-7ecd-e111-bb59-0022644237b5 > Revision: 381120 > Node Kind: directory > Schedule: normal > Last Changed Author: gerald > Last Changed Rev: 380943 > Last Changed Date: 2015-03-10 10:00:25 -0700 (Tue, 10 Mar 2015) > > # more /etc/make.conf > #CPP=clang-cpp > #CC=clang > #CXX=clang++ > WRKDIRPREFIX=/usr/obj/portswork > #WITH_DEBUG= > MALLOC_PRODUCTION= > > === > Mark Millard > markmi at dsl-only.net > > _______________________________________________ > freebsd-toolchain@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-toolchain > To unsubscribe, send any mail to "freebsd-toolchain-unsubscr...@freebsd.org" > _______________________________________________ freebsd-toolchain@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-toolchain To unsubscribe, send any mail to "freebsd-toolchain-unsubscr...@freebsd.org"
