Date: Mon, 13 May 2013 22:48:39 +0200 From: Dimitry Andric <dim@FreeBSD.org> To: Sergey Kandaurov <pluknet@gmail.com>, "Michael W. Lucas" <mwlucas@michaelwlucas.com>, Anton Shterenlikht <mexas@bris.ac.uk> Cc: "current@freebsd.org Current" <current@freebsd.org> Subject: Re: problem building -current Message-ID: <18FD45FD-430F-4AA6-9E36-D97BBDF1AACF@FreeBSD.org> In-Reply-To: <51890B61.60405@FreeBSD.org> References: <20130507132122.GA83633@bewilderbeast.blackhelicopters.org> <CAE-mSO%2Be-z6L6iLHHKenR9pL3dBR7T4=jJ2JUcu3gPqqsSAJRQ@mail.gmail.com> <51890B61.60405@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On May 7, 2013, at 16:10, Dimitry Andric <dim@freebsd.org> wrote: > On 2013-05-07 16:01, Sergey Kandaurov wrote: >> On 7 May 2013 17:21, Michael W. Lucas <mwlucas@michaelwlucas.com> wrote: > ... >>> c++ -O2 -pipe -I/usr/src/lib/clang/libllvmsupport/../../../contrib/llvm/include -I/usr/src/lib/clang/libllvmsupport/../../../contrib/llvm/tools/clang/include -I/usr/src/lib/clang/libllvmsupport/../../../contrib/llvm/lib/Support -I. -I/usr/src/lib/clang/libllvmsupport/../../../contrib/llvm/../../lib/clang/include -DLLVM_ON_UNIX -DLLVM_ON_FREEBSD -D__STDC_LIMIT_MACROS -D__STDC_CONSTANT_MACROS -fno-strict-aliasing -DLLVM_DEFAULT_TARGET_TRIPLE=\"x86_64-unknown-freebsd10.0\" -DLLVM_HOSTTRIPLE=\"x86_64-unknown-freebsd10.0\" -DDEFAULT_SYSROOT=\"\" -I/usr/obj/usr/src/tmp/legacy/usr/include -fno-exceptions -fno-rtti -c /usr/src/lib/clang/libllvmsupport/../../../contrib/llvm/lib/Support/Process.cpp -o Process.o >>> In file included from /usr/src/lib/clang/libllvmsupport/../../../contrib/llvm/lib/Support/Process.cpp:85: >>> /usr/src/lib/clang/libllvmsupport/../../../contrib/llvm/lib/Support/Unix/Process.inc: In member function 'virtual llvm::sys::TimeValue llvm::sys::self_process::get_user_time() const': >>> /usr/src/lib/clang/libllvmsupport/../../../contrib/llvm/lib/Support/Unix/Process.inc:75: error: 'CLOCK_PROCESS_CPUTIME_ID' was not declared in this scope ... > Yes, this is an annoying problem. When the CLOCK_PROCESS_CPUTIME_ID > support was originally added, it was only put in sys/time.h, not in > time.h. So any application that includes the latter will not be able to > use the define. I have added a workaround (ugly, but functional :) in r250616. -Dimitry
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?18FD45FD-430F-4AA6-9E36-D97BBDF1AACF>