[Bug 236772] build error on cross compile: '.../c++/v1/experimental/' does not exist

2020-02-05 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=236772 Mark Millard changed: What|Removed |Added CC||marklmi26-f...@yahoo.com --- Commen

[Bug 236772] build error on cross compile: '.../c++/v1/experimental/' does not exist

2020-02-05 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=236772 HIROKI MORI changed: What|Removed |Added Resolution|Not A Bug |--- Status|Closed

[Bug 236772] build error on cross compile: '.../c++/v1/experimental/' does not exist

2019-07-27 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=236772 HIROKI MORI changed: What|Removed |Added Resolution|--- |Not A Bug Status|Open

[Bug 236772] build error on cross compile: '.../c++/v1/experimental/' does not exist

2019-07-19 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=236772 --- Comment #8 from HIROKI MORI --- Created attachment 205908 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=205908&action=edit This is build log. -- You are receiving this mail because: You are the assignee for the bug. __

[Bug 236772] build error on cross compile: '.../c++/v1/experimental/' does not exist

2019-07-19 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=236772 --- Comment #7 from Dimitry Andric --- (In reply to HIROKI MORI from comment #6) > I update 11.3 host os. But still I need this patch. > > *** Makefile.inc1.origMon Jul 8 14:27:19 2019 > --- Makefile.inc1 Fri Jul 19 18:05:11 2

[Bug 236772] build error on cross compile: '.../c++/v1/experimental/' does not exist

2019-07-19 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=236772 --- Comment #6 from HIROKI MORI --- I update 11.3 host os. But still I need this patch. *** Makefile.inc1.orig Mon Jul 8 14:27:19 2019 --- Makefile.inc1 Fri Jul 19 18:05:11 2019 *** *** 1086,1091 --- 1086,1092

[Bug 236772] build error on cross compile: '.../c++/v1/experimental/' does not exist

2019-04-09 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=236772 --- Comment #5 from HIROKI MORI --- I use NO_CLEAN again. I think make directory at "stage 2.2: rebuilding the object tree" by lib/clang/8.0.0/include. But I don't found that log. Where define this? -- You are receiving this mail because

[Bug 236772] build error on cross compile: '.../c++/v1/experimental/' does not exist

2019-03-30 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=236772 --- Comment #4 from Dimitry Andric --- (In reply to HIROKI MORI from comment #3) > Thanks for you comment. > > I check my build environment then that set NO_CLEAN. > > I delete this option but I have other error. > > ===> lib/clang/libll

[Bug 236772] build error on cross compile: '.../c++/v1/experimental/' does not exist

2019-03-30 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=236772 --- Comment #3 from HIROKI MORI --- Thanks for you comment. I check my build environment then that set NO_CLEAN. I delete this option but I have other error. ===> lib/clang/libllvm (all) llvm-tblgen -gen-attrs -I /usr/home/hiroki/freebs

[Bug 236772] build error on cross compile: '.../c++/v1/experimental/' does not exist

2019-03-25 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=236772 --- Comment #2 from Dimitry Andric --- (In reply to HIROKI MORI from comment #0) > I build sys/arm/ralink(armv5t) on amd64 host. I have build error on > buildworld after clang update 7.0. > > Now clang is 8.0. I have

[Bug 236772] build error on cross compile: '.../c++/v1/experimental/' does not exist

2019-03-25 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=236772 --- Comment #1 from HIROKI MORI --- This is my temporary workaround. diff --git a/Makefile.inc1 b/Makefile.inc1 index cf166a813d2..0dc58016601 100644 --- a/Makefile.inc1 +++ b/Makefile.inc1 @@ -1084,6 +1084,7 @@ _cross-tools: @echo

[Bug 236772] build error on cross compile: '.../c++/v1/experimental/' does not exist

2019-03-25 Thread bugzilla-noreply
|freebsd-...@freebsd.org |toolch...@freebsd.org CC||freebsd-...@freebsd.org Severity|Affects Only Me |Affects Some People Flags||mfc-stable12? Summary|build error on cross

Re: powerpc64 11.0-CURRENT portmaster lang/clang36 gets error: llvm-build: error: invalid native target: 'powerpc64' (not in project)

2015-03-18 Thread Brooks Davis
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. >

Re: powerpc64 11.0-CURRENT portmaster lang/clang36 gets error: llvm-build: error: invalid native target: 'powerpc64' (not in project)

2015-03-17 Thread Mark Millard
he error report was after it reported entering the directory: /usr/obj/portswork/usr/ports/lang/clang36/work/llvm-3.6.0.src/tools/clang/lib/Driver/ The report was: llvm-build: error: invalid native target: 'powerpc64' (not in project) I'd be surprised if 11.0-CURRENT vs. 10.1-STABLE

Re: powerpc64 11.0-CURRENT portmaster lang/clang36 gets another error: llvm-build: error: '::sscanf' has not been declared

2015-03-17 Thread Mark Millard
Looking at https://github.com/clang-omp/clang_trunk/blob/master/lib/Driver/MSVCToolChain.cpp shows that the modern source code has std::sscanf and use so that is likely the better direction to go. What I saw when I looked was: //===--- ToolChains.cpp - ToolChain Implementations --

Re: powerpc64 11.0-CURRENT portmaster lang/clang36 gets another error: llvm-build: error: '::sscanf' has not been declared

2015-03-17 Thread Mark Millard
I tried the final experiment using std::sscanf (so: adding the std) in to the official port's MSVCToolChain.cpp source without adding an explicit include of . (So also no explicit include of , just like the official source file.) It failed: MSVCToolChain.cpp: In member function 'bool clang::d

Re: powerpc64 11.0-CURRENT portmaster lang/clang36 gets another error: llvm-build: error: '::sscanf' has not been declared

2015-03-17 Thread Mark Millard
Adding a #include to MSVCToolChain.cpp fixed the specific ::sscanf problem for compiling MSVCToolChain.cpp with gcc5. It also allowed the lang/clang36 build and installation to complete. The official MSVCToolChain.cpp for the port does not directly or indirectly include a header that guarant

Re: powerpc64 11.0-CURRENT portmaster lang/clang36 gets another error: llvm-build: error: '::sscanf' has not been declared

2015-03-17 Thread Mark Millard
Please excuse all the "gcc491" references. It is lang/gcc49 and currently that has 4.9.3 . The gcc 4.9.1 in my head was from earlier powerpc64-xtoolchain-gcc experiments. === Mark Millard markmi at dsl-only.net On 2015-Mar-17, at 02:19 AM, Mark Millard wrote: On a powerpc (non-64) I did pkg d

Re: powerpc64 11.0-CURRENT portmaster lang/clang36 gets another error: llvm-build: error: '::sscanf' has not been declared

2015-03-17 Thread Mark Millard
On a powerpc (non-64) I did pkg delete's for lang/gcc5 and lang/clang36 and tried installing lang/gcc491 first then reinstalling lang/clang36 (so it would bootstrap via gcc491). The result was the same as for lang/gcc5: llvm[4]: Compiling MSVCToolChain.cpp for Release build MSVCToolChain.cpp: I

Re: powerpc64 11.0-CURRENT portmaster lang/clang36 gets error: llvm-build: error: invalid native target: 'powerpc64' (not in project)

2015-03-16 Thread Mark Millard
: llvm-build: error: invalid native target: 'powerpc64' (not in project) I'd be surprised if 11.0-CURRENT vs. 10.1-STABLE matters. But powerpc64 likely does. I've not yet tried from a powerpc (non-64) FreeBSD build. I'll note that with top -PaSCHopid I watched it

Re: powerpc64 11.0-CURRENT portmaster lang/clang36 gets another error: llvm-build: error: '::sscanf' has not been declared

2015-03-16 Thread Mark Millard
The last powerpc (non-64) build test to complete ran where only built-in-world compilers originally existed (gcc 4.2.1 and clang 3.4.1 this time. For this context "portmaster -tDK --no-confirm lang/clang36" initiated installing lang/gcc (i.e., 4.8.4 at this point) in order to provide itself with

Re: powerpc64 11.0-CURRENT portmaster lang/clang36 gets another error: llvm-build: error: '::sscanf' has not been declared

2015-03-16 Thread Mark Millard
I tried "portmaster -tDK --no-confirm lang/clang36" on a powerpc (non-64): $ freebsd-version -ku ; uname -ap 11.0-CURRENT 11.0-CURRENT FreeBSD FBSDG4C0 11.0-CURRENT FreeBSD 11.0-CURRENT #0 r279514M: Mon Mar 9 22:24:27 PDT 2015 root@FBSDG4S0:/usr/obj/usr/srcC/sys/GENERICvtsc-NODEBUG powerpc

Re: powerpc64 11.0-CURRENT portmaster lang/clang36 gets another error: llvm-build: error: '::sscanf' has not been declared

2015-03-16 Thread Mark Millard
> On 2015-Mar-16, at 06:23 PM, Nathan Whitehorn 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 compil

Re: powerpc64 11.0-CURRENT portmaster lang/clang36 gets another error: llvm-build: error: '::sscanf' has not been declared

2015-03-16 Thread Nathan Whitehorn
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): # f

powerpc64 11.0-CURRENT portmaster lang/clang36 gets another error: llvm-build: error: '::sscanf' has not been declared

2015-03-16 Thread Mark Millard
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 pow

powerpc64 11.0-CURRENT portmaster lang/clang36 gets error: llvm-build: error: invalid native target: 'powerpc64' (not in project)

2015-03-16 Thread Mark Millard
powerpc64 The problem: portmaster -tDK --no-confirm lang/clang36 is how I started the build. The error report was after it reported entering the directory: /usr/obj/portswork/usr/ports/lang/clang36/work/llvm-3.6.0.src/tools/clang/lib/Driver/ The report was: llvm-build: error: invalid native

Re: llvm build error on ppc

2014-11-14 Thread Andrew Turner
On Thu, 13 Nov 2014 20:17:09 +0200 Konstantin Belousov wrote: > Is ppc the only architecture where we do build clang, but with gcc ? > Since the failure only occured on ppc/pcc64, and not on e.g. arm. We build with clang on little-endian ARM and don't try to build clang and llvm on big-endian ARM

Re: llvm build error on ppc

2014-11-13 Thread Dimitry Andric
On 13 Nov 2014, at 19:19, David Chisnall wrote: > > On 13 Nov 2014, at 18:17, Konstantin Belousov wrote: > >> Is ppc the only architecture where we do build clang, but with gcc ? >> Since the failure only occured on ppc/pcc64, and not on e.g. arm. > > It may be the only architecture where we b

Re: llvm build error on ppc

2014-11-13 Thread David Chisnall
On 13 Nov 2014, at 18:17, Konstantin Belousov wrote: > Is ppc the only architecture where we do build clang, but with gcc ? > Since the failure only occured on ppc/pcc64, and not on e.g. arm. It may be the only architecture where we build with gcc by default, but try to install clang as well.

Re: llvm build error on ppc

2014-11-13 Thread Konstantin Belousov
On Thu, Nov 13, 2014 at 07:11:45PM +0100, Dimitry Andric wrote: > On 13 Nov 2014, at 18:13, Konstantin Belousov wrote:FYI, > > > > I did make tinderbox today for HEAD at r274464, and got the following > > both for ppc and ppc64 worlds. Other arches build successfully. > > > > ===> lib/clang/lib

Re: llvm build error on ppc

2014-11-13 Thread Dimitry Andric
On 13 Nov 2014, at 18:13, Konstantin Belousov wrote:FYI, > > I did make tinderbox today for HEAD at r274464, and got the following > both for ppc and ppc64 worlds. Other arches build successfully. > > ===> lib/clang/libllvmtablegen (all) > /scratch/tmp/kib/src/lib/clang/libllvmselectiondag/../.

llvm build error on ppc

2014-11-13 Thread Konstantin Belousov
FYI, I did make tinderbox today for HEAD at r274464, and got the following both for ppc and ppc64 worlds. Other arches build successfully. ===> lib/clang/libllvmtablegen (all) /scratch/tmp/kib/src/lib/clang/libllvmselectiondag/../../../contrib/llvm/lib/CodeGen/SelectionDAG/SelectionDAG.cpp: In m

Re: Build error

2014-08-29 Thread Dimitry Andric
On 29 Aug 2014, at 18:31, Sinha, Prokash wrote: > I was trying to build the latest from the svn trunk - clang/llvm - > > langAttrEmitter.cpp:994:29: error: 'SimpleArgument' does not refer to a value >Ptr = llvm::make_unique(Arg, Attr, "int"); >^ > ClangAttrEmitter

Build error

2014-08-29 Thread Sinha, Prokash
I was trying to build the latest from the svn trunk - clang/llvm - langAttrEmitter.cpp:994:29: error: 'SimpleArgument' does not refer to a value Ptr = llvm::make_unique(Arg, Attr, "int"); ^ ClangAttrEmitter.cpp:216:9: note: declared here class SimpleArgument : pu