Build error in FreeBSD head, main-n259058-105019e0d6c -> main-n259061-b1258b76435

And the only commit after main-n259061-b1258b76435 so far is 004bb636ca65f3239da284c20abb7f9d1d953dee, which claims: | tcp: Move sysctl OIDs related to ECN to tcp_ecn. | Keep all ECN related code in (mostly) one place. | | No functional change. I'm seeing: ... building shared library

openzfs-kmod build error

CURRENT r362292 sysutils/openzfs-kmod build aborts with error:... /usr/ports/sysutils/openzfs-kmod/work/zfs-c0eb5c35e/module/os/freebsd/zfs/zfs_vfsops.c:128:19: error:   incompatible pointer types initializing 'vfs_checkexp_t *' (aka 'int (*)(struct   mount *, struct

Re: openzfs-kmod build error

On 6/23/20 11:12 AM, Rick Macklem wrote: Kostya Berger wrote: CURRENT r362292 sysutils/openzfs-kmod build aborts with error:... /usr/ports/sysutils/openzfs-kmod/work/zfs->c0eb5c35e/module/os/freebsd/zfs/zfs_vfsops.c:128:19: error: incompatible pointer types initializing

Re: openzfs-kmod build error

Kostya Berger wrote: >CURRENT r362292 >sysutils/openzfs-kmod build aborts with error:... >/usr/ports/sysutils/openzfs-kmod/work/zfs->c0eb5c35e/module/os/freebsd/zfs/zfs_vfsops.c:128:19: > error: > incompatible pointer types initializing 'vfs_checkexp_t *' (aka 'int > (*)(struct >

Re: llvm 10 libomp build error

On 12 Mar 2020, at 11:38, Kristof Provost wrote: > > On 12 Mar 2020, at 16:58, Ronald Klop wrote: ... >> cc: error: no such file or directory: >> '/data/src/freebsd-current/contrib/llvm-pr >> oject/openmp/runtime/src/thirdparty/ittnotify/ittnotify_static.c' >> cc: error: no input files >> ***

Re: llvm 10 libomp build error

On 12 Mar 2020, at 16:58, Ronald Klop wrote: Hi, Clean build after svn update gives: cc: error: no such file or directory: '/data/src/freebsd-current/contrib/llvm-pr oject/openmp/runtime/src/thirdparty/ittnotify/ittnotify_static.c' cc: error: no input files *** [ittnotify_static.pico] Error

Re: llvm 10 libomp build error

On Thu, Mar 12, 2020 at 09:13:38AM +, Filippo Moretti wrote: > Same problem yesterdayFilippo > > On Thursday, March 12, 2020, 08:59:17 AM GMT+1, Ronald Klop > wrote: > > Hi, > > Clean build after svn update gives: > > cc: error: no such file or directory:  >

Re: llvm 10 libomp build error

Same problem yesterdayFilippo On Thursday, March 12, 2020, 08:59:17 AM GMT+1, Ronald Klop wrote: Hi, Clean build after svn update gives: cc: error: no such file or directory:  '/data/src/freebsd-current/contrib/llvm-pr

llvm 10 libomp build error

Hi, Clean build after svn update gives: cc: error: no such file or directory: '/data/src/freebsd-current/contrib/llvm-pr oject/openmp/runtime/src/thirdparty/ittnotify/ittnotify_static.c' cc: error: no input files *** [ittnotify_static.pico] Error code 1 make[5]: stopped in

current 350855 build error / intel hd 5500 / intel wifi 7265 / sierra em7305

Hello world :-) I have switched to a Panasonic Toughbook CF-MX4 (i5-5300U based), which has problematic: 1. Intel HD 5500 GPU. Cannot see screen (DRM issue?). 2. Intel WiFi 7265. Load format error. 3. Sierra Wireless EM7305. Not recognised by U3G. None of them seem to work out of the box in

Re: current 350855 build error / intel hd 5500 / intel wifi 7265 / sierra em7305

On Sun, Aug 11, 2019 at 4:03 PM Tomasz CEDRO wrote: > I have switched to a Panasonic Toughbook CF-MX4 (i5-5300U based), > which has problematic: > 1. Intel HD 5500 GPU. Cannot see screen (DRM issue?). > 2. Intel WiFi 7265. Load format error. > 3. Sierra Wireless EM7305. Not recognised by U3G. > >

Re: r111 build error

On Wed, 12 Dec 2018 at 10:19, Ed Maste wrote: > > While we could take this to > root cause I think the most expedient fix is probably just to check > for evidence of clang 6 in the object tree, and rm the .depend files > and objects if found. A patch implementing this is available for review in

Re: r111 build error

On Wed, 12 Dec 2018 at 07:35, Lev Serebryakov wrote: > > On 12.12.2018 14:59, Dimitry Andric wrote: > > ld: error: undefined symbol: clang::CallExpr::getLocStart() const > >>> referenced by MacOSXAPIChecker.cpp:86 > >>>

Re: r111 build error

On 12.12.2018 14:59, Dimitry Andric wrote: ld: error: undefined symbol: clang::CallExpr::getLocStart() const >>> referenced by MacOSXAPIChecker.cpp:86 >>> (/usr/src/contrib/llvm/tools/clang/lib/StaticAnalyzer/Checkers/MacOSXAPIChecker.cpp:86) >>> MacOSXAPIChecker.o:((anonymous

Re: r111 build error

ding very last r341836 (with new llvm/clang 7) on r341726 and > > > get this build > > > error (with MALLOC_PRODUCTION=yes): > > > > > > > Worked for me from r341824 to r341840, but I deleted /usr/obj/usr > > before starting the build. I even added MAL

Re: r111 build error

clang 7) on r341726 and get > > this build > > error (with MALLOC_PRODUCTION=yes): > > > > Worked for me from r341824 to r341840, but I deleted /usr/obj/usr > before starting the build. I even added MALLOC_PRODUCTION=yes to > /etc/src.conf. A "me, too" from h

Re: r111 build error

On Wed, 12 Dec 2018 02:11:10 +0300 Lev Serebryakov wrote: > Hello Freebsd-current, > > I'm building very last r341836 (with new llvm/clang 7) on r341726 and get > this build > error (with MALLOC_PRODUCTION=yes): > Worked for me from r341824 to r341840, but I deleted /

Re: r341836 build error

Hello Lev, Wednesday, December 12, 2018, 2:11:10 AM, you wrote: Sorry for messed up subject, I mean r341836 of course. -- Best regards, Levmailto:l...@freebsd.org ___ freebsd-current@freebsd.org mailing list

r111 build error

Hello Freebsd-current, I'm building very last r341836 (with new llvm/clang 7) on r341726 and get this build error (with MALLOC_PRODUCTION=yes): ===> usr.bin/clang/clang (all) c++ -target x86_64-unknown-freebsd13.0 --sysroot=/usr/obj/usr/src/amd64.amd64/tmp -B/usr/obj/usr/src/amd64.amd64/

Re: nvidia-driver build error (last ports, FreeBSD-HEAD)

00, Alex V. Petrov wrote: >>>>> ---- Перенаправленное сообщение >>>>> Тема: nvidia-driver build error (last ports, FreeBSD-HEAD) >>>>> Дата: Tue, 21 Aug 2018 16:41:42 +0700 >>>>> От: Alex V. Petrov >>>>> Кому: Free

Re: nvidia-driver build error (last ports, FreeBSD-HEAD)

On 22/08/2018 16:29, Alan Cox wrote: All of kmem_alloc_attr(), kmem_alloc_contig(), and kmem_malloc() should have their first parameter, typically kernel_arena, but sometimes kmem_arena, removed in FreeBSD 12. There is still one more pending change to kmem_free() that has not hit HEAD yet.

Re: nvidia-driver build error (last ports, FreeBSD-HEAD)

Перенаправленное сообщение >>>> Тема: nvidia-driver build error (last ports, FreeBSD-HEAD) >>>> Дата: Tue, 21 Aug 2018 16:41:42 +0700 >>>> От: Alex V. Petrov >>>> Кому: FreeBSD Ports >>> Should be fixed as of r477761. >>

Re: nvidia-driver build error (last ports, FreeBSD-HEAD)

енаправленное сообщение >>>> Тема: nvidia-driver build error (last ports, FreeBSD-HEAD) >>>> Дата: Tue, 21 Aug 2018 16:41:42 +0700 >>>> От: Alex V. Petrov >>>> Кому: FreeBSD Ports >>> Should be fixed as of r477761. >>> >

Re: nvidia-driver build error (last ports, FreeBSD-HEAD)

On 22/08/2018 05:29, Manfred Antar wrote: On Aug 21, 2018, at 7:23 PM, Alexey Dokuchaev wrote: On Tue, Aug 21, 2018 at 11:22:56PM +0700, Alex V. Petrov wrote: Перенаправленное сообщение Тема: nvidia-driver build error (last ports, FreeBSD-HEAD) Дата: Tue, 21 Aug 2018 16:41

Re: nvidia-driver build error (last ports, FreeBSD-HEAD)

On 08/21/2018 23:29, Manfred Antar wrote: > >> On Aug 21, 2018, at 7:23 PM, Alexey Dokuchaev wrote: >> >> On Tue, Aug 21, 2018 at 11:22:56PM +0700, Alex V. Petrov wrote: >>> Перенаправленное сообщение ---- >>> Тема: nvidia-driver build error (

Re: nvidia-driver build error (last ports, FreeBSD-HEAD)

> On Aug 21, 2018, at 7:23 PM, Alexey Dokuchaev wrote: > > On Tue, Aug 21, 2018 at 11:22:56PM +0700, Alex V. Petrov wrote: >> >> Перенаправленное сообщение >> Тема: nvidia-driver build error (last ports, FreeBSD-HEAD) >> Дата: Tue, 21 Aug

Re: Fwd: nvidia-driver build error (last ports, FreeBSD-HEAD)

On Tue, Aug 21, 2018 at 11:22:56PM +0700, Alex V. Petrov wrote: > > Перенаправленное сообщение > Тема: nvidia-driver build error (last ports, FreeBSD-HEAD) > Дата: Tue, 21 Aug 2018 16:41:42 +0700 > От: Alex V. Petrov > Кому: FreeBSD Ports Should be f

Fwd: nvidia-driver build error (last ports, FreeBSD-HEAD)

Перенаправленное сообщение Тема: nvidia-driver build error (last ports, FreeBSD-HEAD) Дата: Tue, 21 Aug 2018 16:41:42 +0700 От: Alex V. Petrov Кому: FreeBSD Ports cc -O2 -pipe -fno-strict-aliasing -DNV_VERSION_STRING=\"390.77\" -D__KERNEL__ -DNVRM -Wno-unuse

Re: Kernel build error rev.328485

On Saturday, January 27, 2018 06:54:03 PM Per Gunnarsson wrote: > I am back with new build errors. If I post too frequently, please inform me. These all look like you have stale sources in your tree somehow (e.g. sys/compat/freebsd/freebsd32_misc.c doesn't seem to match

Re: Kernel build error

[ Charset UTF-8 unsupported, converting... ] > Hello! > > I am trying to build the kernel with revision 328463. > > It halts with this error: > > /usr/src/sys/cam/scsi/scsi_da.c:1514:9: error: 'CAM_PERIPH_PRINT' macro > redefined [-Werror,-Wmacro-redefined] > #define CAM_PERIPH_PRINT(p, msg,

Kernel build error rev.328485

I am back with new build errors. If I post too frequently, please inform me. /usr/src/sys/compat/freebsd32/freebsd32_misc.c:122:1: error: static_assert failed "compile-time assertion failed" CTASSERT(sizeof(struct kevent32) == 20); ^    ~

Kernel build error

Hello! I am trying to build the kernel with revision 328463. It halts with this error: /usr/src/sys/cam/scsi/scsi_da.c:1514:9: error: 'CAM_PERIPH_PRINT' macro redefined [-Werror,-Wmacro-redefined] #define CAM_PERIPH_PRINT(p, msg, args...)     ^ /usr/src/sys/cam/cam_periph.h:263:9: note:

Re: Build error: 'emmintrin.h' file not found

Hi, indeed, `emmintrin.h` was missing. Along with everything else in `/usr/lib/clang`. I copied its contents from a recent snapshot release and the build went fine. I just don't know how I managed to mess that up. Thank you for the pointer! Regards flo Am 2018-01-24 um 19:54 schrieb Peter

Re: Build error: 'emmintrin.h' file not found

On 2018-Jan-24 17:34:33 +0100, Florian Limberger wrote: >since a few days I can't build 12-CURRENT anymore, due to the 'emmintrin.h' >header missing. I ran into a similar problem about a month ago. First of all, does your host system have emmintrin.h? E.g. what

Build error: 'emmintrin.h' file not found

Hi, since a few days I can't build 12-CURRENT anymore, due to the 'emmintrin.h' header missing. I hope this is all relevant information: uname -a: FreeBSD $HOSTNAME 12.0-CURRENT FreeBSD 12.0-CURRENT #0 r327931: Sat Jan 13 23:47:34 CET 2018

Re: Build error: 'isa/rtc.h' file not found

On Mon, Oct 02, 2017 at 09:44:36AM +0200, O. Hartmann wrote: > Am Mon, 2 Oct 2017 11:35:22 +0700 > "Alex V. Petrov" schrieb: > > > revision 324186 > > In file included from /usr/obj/usr/src/tmp/usr/include/sys/efi.h:33: > >

Re: Build error: 'isa/rtc.h' file not found

Am Mon, 2 Oct 2017 11:35:22 +0700 "Alex V. Petrov" schrieb: > revision 324186 > In file included from /usr/obj/usr/src/tmp/usr/include/sys/efi.h:33: > /usr/obj/usr/src/tmp/usr/include/machine/efi.h:35:10: fatal error: > 'isa/rtc.h' file not found Me, too here. -- O.

Build error: 'isa/rtc.h' file not found

revision 324186 In file included from /usr/obj/usr/src/tmp/usr/include/sys/efi.h:33: /usr/obj/usr/src/tmp/usr/include/machine/efi.h:35:10: fatal error: 'isa/rtc.h' file not found -- - Alex. ___ freebsd-current@freebsd.org mailing list

[Solved] [WAS:libc build error] Mostly all solved bw-iw-ik from 4-20-2016

On Wed, 20 Apr 2016 18:37:45 -0700 (PDT), "Jeffrey Bouquet" wrote: > > > On Wed, 20 Apr 2016 17:37:16 -0700 (PDT), "Jeffrey Bouquet" > wrote: > > > > > > > On Wed, 20 Apr 2016 12:28:29 -0400, Allan Jude > >

Re: [WAS:libc build error] it is HALF solved bw-iw cycle

On Wed, 20 Apr 2016 17:37:16 -0700 (PDT), "Jeffrey Bouquet" wrote: > > > On Wed, 20 Apr 2016 12:28:29 -0400, Allan Jude wrote: > > > On 2016-04-20 12:06, Jeffrey Bouquet wrote: > > > unistd > > > > > > > > >

[WAS:libc build error] installworld result not satisfactory yet...

On Wed, 20 Apr 2016 12:28:29 -0400, Allan Jude wrote: > On 2016-04-20 12:06, Jeffrey Bouquet wrote: > > unistd > > > > > > /usr/src/lib/libc/../../include/unistd.h:330:45: error: expected function > > body after function declarator > > intexecl(

Re: jpg attached, unsure if will go though... libc build error, svn of today

On 2016-04-20 12:06, Jeffrey Bouquet wrote: > unistd > > > /usr/src/lib/libc/../../include/unistd.h:330:45: error: expected function > body after function declarator > intexecl( . > 332:46: >

jpg attached, unsure if will go though... libc build error, svn of today

unistd /usr/src/lib/libc/../../include/unistd.h:330:45: error: expected function body after function declarator intexecl( . 332:46: same... stops libc otherwise clang36 seems to be building so

Re: Build error on current@r296308: 'yacc.h' file not found

On Wed, Mar 2, 2016 at 11:04 AM, Bryan Drewery wrote: > On 3/2/2016 12:52 PM, Bryan Drewery wrote: >> On 3/2/2016 11:00 AM, Kurt Jaeger wrote: >>> Hi! >>> >>> Today, I upgraded to r296308 and had this failure during buildworld: >>> >>> ===> usr.bin/mkesdb_static

Re: Build error on current@r296308: 'yacc.h' file not found

On 3/2/2016 12:52 PM, Bryan Drewery wrote: > On 3/2/2016 11:00 AM, Kurt Jaeger wrote: >> Hi! >> >> Today, I upgraded to r296308 and had this failure during buildworld: >> >> ===> usr.bin/mkesdb_static (obj,build-tools) >> cc -O2 -pipe -I/usr/src/usr.bin/mkesdb_static >>

Re: Build error on current@r296308: 'yacc.h' file not found

Hi! > I have the same compilation error when I tried to build current today as well. /usr/src/usr.bin/mkcsmapper/Makefile.inc has the same problem. -- p...@opsec.eu+49 171 3101372 4 years to go ! ___

Re: Build error on current@r296308: 'yacc.h' file not found

On 3/2/2016 11:00 AM, Kurt Jaeger wrote: > Hi! > > Today, I upgraded to r296308 and had this failure during buildworld: > > ===> usr.bin/mkesdb_static (obj,build-tools) > cc -O2 -pipe -I/usr/src/usr.bin/mkesdb_static > -I/usr/src/usr.bin/mkesdb_static/../mkesdb >

Re: Build error on current@r296308: 'yacc.h' file not found

I have the same compilation error when I tried to build current today as well. On Wed, Mar 2, 2016 at 11:48 AM, Kurt Jaeger wrote: > Hi! > >> Today, I upgraded to r296308 and had this failure during buildworld: >> >> ===> usr.bin/mkesdb_static (obj,build-tools) >> cc -O2 -pipe

Re: Build error on current@r296308: 'yacc.h' file not found

Hi! > Today, I upgraded to r296308 and had this failure during buildworld: > > ===> usr.bin/mkesdb_static (obj,build-tools) > cc -O2 -pipe -I/usr/src/usr.bin/mkesdb_static > -I/usr/src/usr.bin/mkesdb_static/../mkesdb > -I/usr/src/usr.bin/mkesdb_static/../../lib/libc/iconv -g -std=gnu99 >

Build error on current@r296308: 'yacc.h' file not found

Hi! Today, I upgraded to r296308 and had this failure during buildworld: ===> usr.bin/mkesdb_static (obj,build-tools) cc -O2 -pipe -I/usr/src/usr.bin/mkesdb_static -I/usr/src/usr.bin/mkesdb_static/../mkesdb -I/usr/src/usr.bin/mkesdb_static/../../lib/libc/iconv -g -std=gnu99

Re: emulators/virtualbox-ose-kmod build error

On Thu, 25 Feb 2016 09:46:04 +0100 "O. Hartmann" wrote: > On Thu, 25 Feb 2016 09:31:00 +0100 > Tommy Scheunemann wrote: > > > > Am Wed, 24 Feb 2016 22:04:29 +0200 > > > Ivan Klymenko schrieb: > > > > > >> After update from

Re: emulators/virtualbox-ose-kmod build error

On Thu, 25 Feb 2016 09:31:00 +0100 Tommy Scheunemann wrote: > > Am Wed, 24 Feb 2016 22:04:29 +0200 > > Ivan Klymenko schrieb: > > > >> After update from r295867 to r295994: > >> > >> ... > >> /usr/local/bin/ccache cc -O2 -pipe -march=native

Re: emulators/virtualbox-ose-kmod build error

Am Wed, 24 Feb 2016 22:04:29 +0200 Ivan Klymenko schrieb: > After update from r295867 to r295994: > > ... > /usr/local/bin/ccache cc -O2 -pipe -march=native -fno-strict-aliasing > -DRT_OS_FREEBSD > -DIN_RING0 -DIN_RT_R0 -DIN_SUP_R0 -DSUPDRV_WITH_RELEASE_LOGGER -DVBOX >

emulators/virtualbox-ose-kmod build error

After update from r295867 to r295994: ... /usr/local/bin/ccache cc -O2 -pipe -march=native -fno-strict-aliasing -DRT_OS_FREEBSD -DIN_RING0 -DIN_RT_R0 -DIN_SUP_R0 -DSUPDRV_WITH_RELEASE_LOGGER -DVBOX -DRT_WITH_VBOX -w -DVBOX_WITH_HARDENING -DVBOX_WITH_64_BITS_GUESTS -DRT_ARCH_AMD64 -march=native

Build error on i386 when building

Hi Mark, I ran into the following error when trying to build the dtrace tests on i386 (both with 10.2-RELEASE-p7 and 11.0-CURRENT) — have you seen this issue before? Thanks, -NGie --- all_subdir_cddl --- usdt.o: In function `dtrace_dof_init':

Re: Build error on i386 when building

On Sat, Dec 19, 2015 at 05:03:51PM -0800, NGie Cooper wrote: > Hi Mark, > I ran into the following error when trying to build the dtrace tests on > i386 (both with 10.2-RELEASE-p7 and 11.0-CURRENT) — have you seen this issue > before? Yes, that's because drti.o in stable/10 depends on

Re: Build error on i386 when building dtrace tests

(fixed the subject line again..) > On Dec 19, 2015, at 17:57, Mark Johnston wrote: > > On Sat, Dec 19, 2015 at 05:03:51PM -0800, NGie Cooper wrote: >> Hi Mark, >> I ran into the following error when trying to build the dtrace tests on >> i386 (both with 10.2-RELEASE-p7

gcc/amd64 head build error after r281316

Hi, the r281316 commit introduces the following lines which break compilation with gcc on amd64 (as far as i know immintrin.h is only available in our clang). If there are no objections I'd like to add a further check for the use of clang, see attached patch Index:

Re: gcc/amd64 head build error after r281316

On 08 Jul 2015, at 19:05, Luigi Rizzo ri...@iet.unipi.it wrote: the r281316 commit introduces the following lines which break compilation with gcc on amd64 (as far as i know immintrin.h is only available in our clang). If there are no objections I'd like to add a further check for the use

Re: gcc/amd64 head build error after r281316

On Wed, Jul 8, 2015 at 9:36 PM, Dimitry Andric d...@freebsd.org wrote: On 08 Jul 2015, at 19:05, Luigi Rizzo ri...@iet.unipi.it wrote: the r281316 commit introduces the following lines which break compilation with gcc on amd64 (as far as i know immintrin.h is only available in our

Re: PicoBSD build error after r281316

2015-06-22 17:03 GMT+02:00 Luigi Rizzo ri...@iet.unipi.it: On Monday, June 22, 2015, Stefano Garzarella stefanogarzare...@gmail.com wrote: Hi all, I'm using picobsd on FreeBSD-head (r284697) to build a picobsd image with gcc, but I have the following errors during the init phase

Re: PicoBSD build error after r281316

On Monday, June 22, 2015, Stefano Garzarella stefanogarzare...@gmail.com wrote: Hi all, I'm using picobsd on FreeBSD-head (r284697) to build a picobsd image with gcc, but I have the following errors during the init phase (release/picobsd/build/picobsd --init): In file included from

PicoBSD build error after r281316

Hi all, I'm using picobsd on FreeBSD-head (r284697) to build a picobsd image with gcc, but I have the following errors during the init phase (release/picobsd/build/picobsd --init): In file included from /usr/home/stefano/repos/freebsd/lib/liblzma/../../contrib/xz/src/liblzma/lz/lz_encoder.c:23:

Re: ipfw build error with WITHOUT_PF (pfvar.h)

Andrey, On Sat, Nov 23, 2013 at 12:07:35PM +0400, Andrey Chernov wrote: A There is a problem in recent -current to build ipfw with WITHOUT_PF A option, introduced in r257215. altq.c file produce error due to included A net/pfvar.h have following includes A A #include netpfil/pf/pf.h A #include

ipfw build error with WITHOUT_PF (pfvar.h)

Hi. There is a problem in recent -current to build ipfw with WITHOUT_PF option, introduced in r257215. altq.c file produce error due to included net/pfvar.h have following includes #include netpfil/pf/pf.h #include netpfil/pf/pf_altq.h #include netpfil/pf/pf_mtag.h and netpfil/pf directory is

Re: ipfw build error with WITHOUT_PF (pfvar.h)

On 23.11.2013 12:12, Gleb Smirnoff wrote: Andrey, On Sat, Nov 23, 2013 at 12:07:35PM +0400, Andrey Chernov wrote: A There is a problem in recent -current to build ipfw with WITHOUT_PF A option, introduced in r257215. altq.c file produce error due to included A net/pfvar.h have following

Re: ipfw build error with WITHOUT_PF (pfvar.h)

On Sat, Nov 23, 2013 at 12:20:40PM +0400, Andrey Chernov wrote: A On Sat, Nov 23, 2013 at 12:07:35PM +0400, Andrey Chernov wrote: A A There is a problem in recent -current to build ipfw with WITHOUT_PF A A option, introduced in r257215. altq.c file produce error due to included A A net/pfvar.h

graphics/gnash build error

When I try to build gnash libtool: link: g++46 -O2 -pipe -Wl,-rpath=/usr/local/lib/gcc46 -fno-strict-aliasing -Wl,-rpath=/usr/local/lib/gcc46 -W -Wall -Wcast-align -Wcast-qual -Wpointer-arith -Wreturn-type -Wnon-virtual-dtor -Wunused -fvisibility-inlines-hidden /usr/local/lib/libintl.so

build error revision 255864

Hi all, I'm having this errorbuilding 255864 revision: cc -O2 -pipe -DHAVE_CONFIG_H -DLOCALEDIR=\/usr/share/locale\ -I/usr/src/gnu/usr.bin/texinfo/makeinfo/../../../../contrib/texinfo -I/usr/src/gnu/usr.bin/texinfo/makeinfo/../../../../contrib/texinfo/lib -std=gnu99 -Qunused-arguments

Re: build error revision 255864

On Tue, Sep 24, 2013 at 09:38:11PM -0300, Marcelo Gondim wrote: Hi all, I'm having this errorbuilding 255864 revision: This is due to the recent changes in sys/cam. We're working on it. Glen cc -O2 -pipe -DHAVE_CONFIG_H -DLOCALEDIR=\/usr/share/locale\

Re: build error revision 255864

On Tue, Sep 24, 2013 at 08:45:22PM -0400, Glen Barber wrote: On Tue, Sep 24, 2013 at 09:38:11PM -0300, Marcelo Gondim wrote: Hi all, I'm having this errorbuilding 255864 revision: This is due to the recent changes in sys/cam. We're working on it. I have reverted the commit in

Re: libreoffice build error

19.09.2013, 04:02, Jung-uk Kim j...@freebsd.org: On 2013-09-18 13:20:27 -0400, Jung-uk Kim wrote: 2013년  9월 18일 13:20, Jung-uk Kim 쓴 글: On 2013-09-18 12:39:46 - -0400, David Chisnall wrote:  On 18 Sep 2013, at 16:26, Tijl Coosemans t...@freebsd.org  wrote:  On Tue, 17 Sep 2013 21:04:14

build error

cc -pg -O2 -pipe -I/usr/src/lib/libngatm/../../sys/contrib/ngatm -I/usr/obj/usr/src/ lib/libngatm -I/usr/src/lib/libngatm/../../contrib/ngatm/libngatm -std=gnu99 -Qunused-arguments -fstack-protector -Wsystem-headers -Werror -Wall -Wno-format-y2k -W -Wno-unused-parameter -Wstrict-prototypes

Re: libreoffice build error

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Wed, 18 Sep 2013 20:00:09 -0400 Jung-uk Kim j...@freebsd.org wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 2013-09-18 13:20:27 -0400, Jung-uk Kim wrote: 2013년 9월 18일 13:20, Jung-uk Kim 쓴 글: On 2013-09-18 12:39:46 - -0400, David

gnome2 build error (evolution-data-server-2.32.1_4)

Hello, I was trying to install gnome2 port but it ends up with an error in evolution-data-server. Any clues? === Building for evolution-data-server-2.32.1_4 gmake[7]: Entering directory `/usr/obj/usr/ports/databases/evolution-data-server/work/evolution-data-server-2.32.1' gmake all-recursive

Re: gnome2 build error (evolution-data-server-2.32.1_4)

This looks like the namespace pollution that was caused by iconv.h including stdbool.h, which I have already fixed. David On 18 Sep 2013, at 14:57, Ricardo Campos Passanezi ri...@ige.unicamp.br wrote: Hello, I was trying to install gnome2 port but it ends up with an error in

Re: libreoffice build error

On Tue, 17 Sep 2013 21:04:14 -0400 Jung-uk Kim wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 2013-09-17 13:24:41 -0400, Jung-uk Kim wrote: I am still working on libc++ issues but it is much more complicated. :-( I fixed almost everything except for exception handling issues.

Re: libreoffice build error

On 18 Sep 2013, at 16:26, Tijl Coosemans t...@freebsd.org wrote: On Tue, 17 Sep 2013 21:04:14 -0400 Jung-uk Kim wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 2013-09-17 13:24:41 -0400, Jung-uk Kim wrote: I am still working on libc++ issues but it is much more complicated. :-(

Re: libreoffice build error

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 2013-09-18 12:39:46 -0400, David Chisnall wrote: On 18 Sep 2013, at 16:26, Tijl Coosemans t...@freebsd.org wrote: On Tue, 17 Sep 2013 21:04:14 -0400 Jung-uk Kim wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 2013-09-17 13:24:41

Re: libreoffice build error

On 18 Sep 2013, at 19:31, Tijl Coosemans t...@freebsd.org wrote: There are some pointers to the start such as the caughtExceptions field in struct __cxa_eh_globals and the nextException field in struct __cxa_exception itself. These are not part of the public API. David

Re: libreoffice build error

On 18 Sep 2013, at 19:49, David Chisnall thera...@freebsd.org wrote: These are not part of the public API. Oh. Yes it is. Ho hum... David ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To

Re: libreoffice build error

On Wed, 18 Sep 2013 17:39:46 +0100 David Chisnall wrote: On 18 Sep 2013, at 16:26, Tijl Coosemans t...@freebsd.org wrote: On Tue, 17 Sep 2013 21:04:14 -0400 Jung-uk Kim wrote: On 2013-09-17 13:24:41 -0400, Jung-uk Kim wrote: I am still working on libc++ issues but it is much more complicated.

Re: libreoffice build error

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 2013-09-18 14:51:20 -0400, David Chisnall wrote: On 18 Sep 2013, at 19:49, David Chisnall thera...@freebsd.org wrote: These are not part of the public API. Oh. Yes it is. Ho hum... It seems it's removed from GCC because it broke

Re: libreoffice build error

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 2013-09-18 13:20:27 -0400, Jung-uk Kim wrote: 2013년 9월 18일 13:20, Jung-uk Kim 쓴 글: On 2013-09-18 12:39:46 - -0400, David Chisnall wrote: On 18 Sep 2013, at 16:26, Tijl Coosemans t...@freebsd.org wrote: On Tue, 17 Sep 2013 21:04:14 -0400

libreoffice build error

Hi list, the following error occures when I try to build editors/libreoffice: [build CXX] sal/rtl/source/ustrbuf.cxx In file included from /usr/ports/editors/libreoffice/work/libreoffice-4.0.5.2/sal/rtl/source/bootstrap.cxx:22: In file included from

Re: libreoffice build error

On Tue, 17 Sep 2013 14:57:19 +0400 S.N.Grigoriev serguey-grigor...@yandex.ru wrote: Hi list, the following error occures when I try to build editors/libreoffice: [build CXX] sal/rtl/source/ustrbuf.cxx In file included from

Re: libreoffice build error

On Tue, Sep 17, 2013 at 04:20:45PM +0200, O. Hartmann wrote: On Tue, 17 Sep 2013 14:57:19 +0400 S.N.Grigoriev serguey-grigor...@yandex.ru wrote: Hi list, the following error occures when I try to build editors/libreoffice: [build CXX] sal/rtl/source/ustrbuf.cxx In file

Re: libreoffice build error

On Tue, Sep 17, 2013 at 11:51:41AM -0400, Shawn Webb wrote: I'm getting a build error as well, but on 9-STABLE under Poudriere. Relevant part of the logfile: In file included from /wrkdirs/usr/ports/editors/libreoffice/work/libreoffice-4.0.5.2/sc/source/core/tool/scmatrix.cxx:34: In file

Re: libreoffice build error

I'm getting a build error as well, but on 9-STABLE under Poudriere. Relevant part of the logfile: In file included from /wrkdirs/usr/ports/editors/libreoffice/work/libreoffice-4.0.5.2/sc/source/core/tool/scmatrix.cxx:34: In file included from /usr/local/include/mdds/multi_type_matrix.hpp:31: /usr

build error svn revision 255636

Error em make buildworld clang/libllvmvectorize/../../../contrib/llvm/lib/Transforms/Vectorize/BBVectorize.cpp -o BBVectorize.o c++ -O2 -pipe -I/usr/src/lib/clang/libllvmvectorize/../../../contrib/llvm/include -I/usr/src/lib/clang/libllvmvectorize/../../../contrib/llvm/tools/clang/include

Re: libreoffice build error

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 2013-09-17 11:52:45 -0400, Baptiste Daroussin wrote: On Tue, Sep 17, 2013 at 11:51:41AM -0400, Shawn Webb wrote: I'm getting a build error as well, but on 9-STABLE under Poudriere. Relevant part of the logfile: In file included from

Re: libreoffice build error

17.09.2013, 21:27, Jung-uk Kim j...@freebsd.org: On 2013-09-17 11:52:45 -0400, Baptiste Daroussin wrote:  On Tue, Sep 17, 2013 at 11:51:41AM -0400, Shawn Webb wrote:  I'm getting a build error as well, but on 9-STABLE under  Poudriere. Relevant part of the logfile:  In file included from

Re: libreoffice build error

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 2013-09-17 13:24:41 -0400, Jung-uk Kim wrote: I am still working on libc++ issues but it is much more complicated. :-( I fixed almost everything except for exception handling issues. Unfortunately, libc++/libcxxrt's exception handling is not

aicasm build error

For a while I've been getting a build error on aicasm during the early steps of the build. Today I finally dug into it and discovered it's because the build is using a mix of header files, some from /usr/include on the build host, and some from obj/... for the target being built. It happens

Re: aicasm build error

On Sep 14, 2013, at 19:50, Ian Lepore i...@freebsd.org wrote: For a while I've been getting a build error on aicasm during the early steps of the build. Today I finally dug into it and discovered it's because the build is using a mix of header files, some from /usr/include on the build host

Re: aicasm build error

On Sat, 2013-09-14 at 20:42 +0200, Dimitry Andric wrote: On Sep 14, 2013, at 19:50, Ian Lepore i...@freebsd.org wrote: For a while I've been getting a build error on aicasm during the early steps of the build. Today I finally dug into it and discovered it's because the build is using a mix

Re: aicasm build error

On Sat, 2013-09-14 at 20:42 +0200, Dimitry Andric wrote: On Sep 14, 2013, at 19:50, Ian Lepore i...@freebsd.org wrote: For a while I've been getting a build error on aicasm during the early steps of the build. Today I finally dug into it and discovered it's because the build is using a mix

Re: devel/gettext build error in jail i386 environment on amd64 host

Hello. Have same problem. Clear enviroment (just new installed system + i386 jail) When building gettext and libiconv find system uniq crashing pid 88854 (uniq), uid 0: exited on signal 11 (core dumped) pid 88859 (uniq), uid 0: exited on signal 11 (core dumped) pid 88864 (uniq), uid 0:

Re: devel/gettext build error in jail i386 environment on amd64 host

IK Thank you :) IK I watch the mailing list. ;) IK http://docs.freebsd.org/cgi/mid.cgi?20130903172529.GA9 IK Unfortunately I did not have time to check the problem with uniq... Gettext build failed because of failed uniq, so if u steel have problem u know what to do.

Re: devel/gettext build error in jail i386 environment on amd64 host

Try to disable options options CAPABILITY_MODE # Capsicum capability mode options CAPABILITIES# Capsicum capabilities in kernel conf, for me it's resolve problem Ivan Klymenko wrote: IK В Sat, 24 Aug 2013 13:26:01 +0200 IK Hans Petter Selasky

  1   2   3   >