Re: aarch64-current build failure

On Sun, 12 May 2024 at 09:14, Chavdar Ivanov wrote: > > Hi, > > I am getting: > > #create libEGL/loader.d > CC=/dumps/sysbuild/evbarm64/tools/bin/aarch64--netbsd-gcc > /dumps/sysbuild/evbarm64/tools/bin/nbmkdep -f loader.d.tmp -- > -std=gnu99 -Werror

aarch64-current build failure

Hi, I am getting: #create libEGL/loader.d CC=/dumps/sysbuild/evbarm64/tools/bin/aarch64--netbsd-gcc /dumps/sysbuild/evbarm64/tools/bin/nbmkdep -f loader.d.tmp -- -std=gnu99 -Werror --sysroot=/dumps/sysbuild/evbarm64/de stdir -I/usr/xsrc/external/mit/MesaLib/dist/include

Re: i386 -current build failure

On Mon, 14 Aug 2023 at 13:50, Chavdar Ivanov wrote: > > On Mon, 14 Aug 2023 at 10:35, Martin Husemann wrote: > > > > On Mon, Aug 14, 2023 at 09:23:37AM +0100, Chavdar Ivanov wrote: > > > Hi, > > > ERROR: nbctfmerge: Input file adiantum_selftest.o was partially built > > > from C sources, but no

Re: i386 -current build failure

On Mon, 14 Aug 2023 at 10:35, Martin Husemann wrote: > > On Mon, Aug 14, 2023 at 09:23:37AM +0100, Chavdar Ivanov wrote: > > Hi, > > ERROR: nbctfmerge: Input file adiantum_selftest.o was partially built > > from C sources, but no CTF data was present > > Can you reproduce it after removing that

Re: i386 -current build failure

On Mon, Aug 14, 2023 at 09:23:37AM +0100, Chavdar Ivanov wrote: > Hi, > ERROR: nbctfmerge: Input file adiantum_selftest.o was partially built > from C sources, but no CTF data was present Can you reproduce it after removing that .o file (or the whole kernel build directory)? This symptom often

i386 -current build failure

Hi, Does anybody else get the following while building i396 -current: --- # link INSTALL_XEN3PAE_DOMU/netbsd /dumps/sysbuild/i386/tools/bin/i486--netbsdelf-ld -Map netbsd.map --cref -T netbsd.ldscript -Ttext 0xc010 -e start -X -o netbsd ${SYSTEM_OBJ:[@]:Nswapnetbsd.o} ${EXTRA_OBJ}

Re: -current build failure

On Mon, Jun 05, 2023 at 03:01:37AM +1000, Luke Mewburn wrote: > I managed to reproduced this just building the tools with -V MKLLVM=yes. > I've reverted tools/Makefile.host revision 1.35 and it seems to fix the > tools build for me. > > Does this resolve the issue for you? Yes. Now I just have

Re: -current build failure

On 23-06-05 03:01, I wrote: | BTW: I don't know why replacing | NOINFO= # defined | NOLINT= # defined | NOMAN= # defined | MKREPRO=no # Native toolchain might be unable to do it | .include | | with | .include | | where

Re: -current build failure

On 23-06-04 14:40, Thomas Klausner wrote: | Hi! | | I just tried updating my -current but the build failed: | | build.sh -j 32 -x -V MKDEBUG=yes -V MKDEBUGLIB=yes -V MKLLVM=yes -V NOGCCERROR=yes -T /usr/obj/tools.gcc -m amd64 -O /usr/obj/src.amd64 -D /usr/obj/amd64.gcc.20230604 -R

Re: -current build failure

On Sun, Jun 04, 2023 at 02:40:16PM +0200, Thomas Klausner wrote: > Hi! > > I just tried updating my -current but the build failed: > > build.sh -j 32 -x -V MKDEBUG=yes -V MKDEBUGLIB=yes -V MKLLVM=yes -V > NOGCCERROR=yes -T /usr/obj/tools.gcc -m amd64 -O /usr/obj/src.amd64 -D >

-current build failure

Hi! I just tried updating my -current but the build failed: build.sh -j 32 -x -V MKDEBUG=yes -V MKDEBUGLIB=yes -V MKLLVM=yes -V NOGCCERROR=yes -T /usr/obj/tools.gcc -m amd64 -O /usr/obj/src.amd64 -D /usr/obj/amd64.gcc.20230604 -R /usr/obj/amd64.gcc.20230604.release distribution ---

Re: -current build failure?

On 30 December 2022 14:26:09 (+00:00), Martin Husemann wrote: > On Fri, Dec 30, 2022 at 01:04:46PM +, Chavdar Ivanov wrote: > > Hi, > > > > I am getting again a failure in binutils.old, after having cleaned four days > > ago the entire obj: > > binutils.old is the wrong directory,

Re: -current build failure?

On Fri, Dec 30, 2022 at 01:04:46PM +, Chavdar Ivanov wrote: > Hi, > > I am getting again a failure in binutils.old, after having cleaned four days > ago the entire obj: binutils.old is the wrong directory, your build should use binutils now. You need to clean the tools/binutils obj dir.

-current build failure?

Hi, I am getting again a failure in binutils.old, after having cleaned four days ago the entire obj: ... CC archive.lo In file included from /home/sysbuild/src/tools/binutils/../../external/gpl3/binutils.old/dist/bfd/archive.c:134:

re: amd64 -current build failure

matthew green writes: > > manual xkeyboard-config.7 matches @.*@, probably missing updates > > *** [xkeyboard-config.7] Error code 1 > > hmm, i thought i commited this fix for this.. but nope, i > only had it sitting in my tree. > > please try again with >

re: amd64 -current build failure

> manual xkeyboard-config.7 matches @.*@, probably missing updates > *** [xkeyboard-config.7] Error code 1 hmm, i thought i commited this fix for this.. but nope, i only had it sitting in my tree. please try again with src/external/mit/xorg/lib/xkeyboard-config/Makefile 1.14 .mrg.

amd64 -current build failure

Hi, I am getting, three times in a row: ... --- xkeyboard-config.pc --- if /home/sysbuild/amd64/tools/bin/nbsed -e '/tab(@)/,/^\.TE/d' -e '/^\.IN /d' xkeyboard-config.pc.tmp | /home/sysbuild/amd64/tools/bin/nbgrep -E '@([^ ]+)@'; then echo "pkg-config xkeyboard-config.pc matches @.*@,

Re: -current build failure

On Wed, Sep 30, 2020 at 08:24:10AM +0100, Chavdar Ivanov wrote: > --- install-tests --- > x86_64--netbsd-install: > /home/sysbuild/amd64/destdir/usr/tests/net/if_vether/Atffile.inst.dY8rCE: > mkstemp: No such file or directory Fixed a short while ago. Thomas --- Begin Message --- Module Name:

-current build failure

Hi, I am getting: --- install-tests --- --- /home/sysbuild/amd64/destdir/usr/tests/net/if_vether/Atffile --- # install /home/sysbuild/amd64/destdir/usr/tests/net/if_vether/Atffile /home/sysbuild/amd64/tools/bin/x86_64--netbsd-install -U -M /home/sysbuild/amd64/destdir/METALOG -D

Re: -current build failure

Hi, Builds now. On Sun, 9 Aug 2020 at 10:38, Chavdar Ivanov wrote: > > Hi, > > With sources just updated, I am getting: > > # link INSTALL_XEN3_DOMU/netbsd > ld -Map netbsd.map --cref -T netbsd.ldscript -Ttext 0x8020 > -e start -X -o netbsd ${SYSTEM_OBJ:[@]:Nswapnetbsd.o}

-current build failure

Hi, With sources just updated, I am getting: # link INSTALL_XEN3_DOMU/netbsd ld -Map netbsd.map --cref -T netbsd.ldscript -Ttext 0x8020 -e start -X -o netbsd ${SYSTEM_OBJ:[@]:Nswapnetbsd.o} ${EXTRA_OBJ} vers.o swapnetbsd.o ld: netbsd32_mod.o: in function

Re: early tools -current build failure

Ok, thanks. On Sun, 19 Jul 2020 at 13:51, Martin Husemann wrote: > On Sun, Jul 19, 2020 at 01:42:30PM +0100, Chavdar Ivanov wrote: > > Any ideas? Perhaps I've missed something new in the BUILDING file? > > there is nothing particular in these two lines of the bsd.nls.mk: > > make(1) is broken

Re: early tools -current build failure

On Sun, Jul 19, 2020 at 01:42:30PM +0100, Chavdar Ivanov wrote: > Any ideas? Perhaps I've missed something new in the BUILDING file? > there is nothing particular in these two lines of the bsd.nls.mk: make(1) is broken right now. Martin

early tools -current build failure

Hi, My attempt to build -current amd64 failed twice today; after the first failure I moved aside the obj and tools directory and did 'make cleandir', essentially starting from scratch; it failed identically: ... build.sh command:./build.sh -D/home/sysbuild/amd64/destdir

Re: -current build failure

On Wed, May 27, 2020 at 06:54:47PM +0100, Chavdar Ivanov wrote: > Hi, > > With sources updated about an hour ago I get: > . > --- kern-XEN3_DOM0 --- > /home/sysbuild/amd64/tools/bin/x86_64--netbsd-ld: pintr.o: in function > `xen_pic_to_gsi': > pintr.c:(.text+0x78): undefined reference to

Re: -current build failure - flist

Date:Sun, 5 Apr 2020 00:41:20 +0100 From:Chavdar Ivanov Message-ID: | It appears a flist hasn't been updated after the bfd upgrade: That has since been fixed (by Christos). kre

-current build failure - flist

Hi, It appears a flist hasn't been updated after the bfd upgrade: === 8 extra files in DESTDIR = Files in DESTDIR but missing from flist. File is obsolete or flist is out of date ? -- ./usr/lib/i386/libbfd.so.16 ./usr/lib/i386/libbfd.so.16.0

Re: amd64 -current build failure

I had to wipe the tools directory as well before I finally went through the 9.99.26 build. I also used NJOBS=1, but don't know if this had anything to do with it. On Tue, 17 Dec 2019 at 19:23, Chavdar Ivanov wrote: > > On Tue, 17 Dec 2019 at 16:27, Paul Goyette wrote: > > > > On Tue, 17 Dec

Re: amd64 -current build failure

On Tue, 17 Dec 2019, Chavdar Ivanov wrote: I am still getting the same errors, my CVS log is empty... You might have to run a full build. I was trying an update build which failed, but a full build seems to work. On Tue, 17 Dec 2019 at 15:12, Paul Goyette wrote: Christos just fixed

Re: amd64 -current build failure

I am still getting the same errors, my CVS log is empty... On Tue, 17 Dec 2019 at 15:12, Paul Goyette wrote: > > Christos just fixed the lzma stuff... > > On Tue, 17 Dec 2019, Chavdar Ivanov wrote: > > > Looks like it; the lzma/bz2 undefined references still there though, > > 10 minutes ago. > >

Re: amd64 -current build failure

Christos just fixed the lzma stuff... On Tue, 17 Dec 2019, Chavdar Ivanov wrote: Looks like it; the lzma/bz2 undefined references still there though, 10 minutes ago. On Tue, 17 Dec 2019 at 13:18, Andrew Doran wrote: Hi, On Tue, Dec 17, 2019 at 09:49:58AM +, Chavdar Ivanov wrote:

Re: amd64 -current build failure

Looks like it; the lzma/bz2 undefined references still there though, 10 minutes ago. On Tue, 17 Dec 2019 at 13:18, Andrew Doran wrote: > > Hi, > > On Tue, Dec 17, 2019 at 09:49:58AM +, Chavdar Ivanov wrote: > > > Last two days I haven't been able to build amd64 -current: > > ... > >

Re: amd64 -current build failure

Hi, On Tue, Dec 17, 2019 at 09:49:58AM +, Chavdar Ivanov wrote: > Last two days I haven't been able to build amd64 -current: > ... > /home/sysbuild/amd64/tools/lib/gcc/x86_64--netbsd/8.3.0/../../../../x86_64--netbsd/bin/ld: > /home/sysbuild/amd64/destdir/usr/lib/librump.so: undefined

Re: amd64 -current build failure

Hi, And the next build: ... /home/sysbuild/amd64/tools/lib/gcc/x86_64--netbsd/8.3.0/../../../../x86_64--netbsd/bin/ld: /home/sysbuild/amd64/destdir/usr/lib/libmagic.so : undefined reference to `lzma_code' /home/sysbuild/amd64/tools/lib/gcc/x86_64--netbsd/8.3.0/../../../../x86_64--netbsd/bin/ld:

amd64 -current build failure

Hi, Last two days I haven't been able to build amd64 -current: ... /home/sysbuild/amd64/tools/lib/gcc/x86_64--netbsd/8.3.0/../../../../x86_64--netbsd/bin/ld: /home/sysbuild/amd64/destdir/usr/lib/librump.so: undefined reference to `rumpns_cpuctl_ioctl' collect2: error: ld returned 1 exit status

Re: -current build failure in compiler_rt/dist/lib/msan/msan_interceptors.cc

On Wed, Oct 23, 2019 at 08:52:32PM +0200, Kamil Rytarowski wrote: > On 23.10.2019 10:46, Kamil Rytarowski wrote: > > On 23.10.2019 06:33, Thomas Klausner wrote: > >> Hi! > >> > >> Yesterday evening's current with: > >> > >> build.sh -j 32 -x -V MKDEBUG=yes -V MKDEBUGLIB=yes -V MKLLVM=yes -T > >>

Re[2]: -current build failure in compiler_rt/dist/lib/msan/msan_interceptors.cc

-- Inviato da Libero Mail per Android mercoledì, 23 ottobre 2019, 10:46AM +02:00 da Kamil Rytarowski n...@gmx.com : >On 23.10.2019 06:33, Thomas Klausner wrote: > Hi! > > Yesterday evening's current with: > > build.sh -j 32 -x -V MKDEBUG=yes -V MKDEBUGLIB=yes -V MKLLVM=yes -T >

Re: -current build failure in compiler_rt/dist/lib/msan/msan_interceptors.cc

On 23.10.2019 10:46, Kamil Rytarowski wrote: > On 23.10.2019 06:33, Thomas Klausner wrote: >> Hi! >> >> Yesterday evening's current with: >> >> build.sh -j 32 -x -V MKDEBUG=yes -V MKDEBUGLIB=yes -V MKLLVM=yes -T >> /usr/obj/tools.gcc -m amd64 -O /usr/obj/src.amd64 -D >>

Re: -current build failure in compiler_rt/dist/lib/msan/msan_interceptors.cc

On 23.10.2019 06:33, Thomas Klausner wrote: > Hi! > > Yesterday evening's current with: > > build.sh -j 32 -x -V MKDEBUG=yes -V MKDEBUGLIB=yes -V MKLLVM=yes -T > /usr/obj/tools.gcc -m amd64 -O /usr/obj/src.amd64 -D > /usr/obj/amd64.gcc.20191022 -R /usr/obj/amd64.gcc.20191022.release >

-current build failure in compiler_rt/dist/lib/msan/msan_interceptors.cc

Hi! Yesterday evening's current with: build.sh -j 32 -x -V MKDEBUG=yes -V MKDEBUGLIB=yes -V MKLLVM=yes -T /usr/obj/tools.gcc -m amd64 -O /usr/obj/src.amd64 -D /usr/obj/amd64.gcc.20191022 -R /usr/obj/amd64.gcc.20191022.release distribution gives me: --- msan_interceptors.o --- In file

Re: Current build failure on AMD64

2019-01-29 09:59 időpontban Martin Husemann ezt írta: On Tue, Jan 29, 2019 at 09:30:13AM +0100, Fekete Zoltán wrote: Hi There, My current's build breaks with the message below for 2 weeks now. Could you please help to resolve?

Re: Current build failure on AMD64

On Tue, Jan 29, 2019 at 09:30:13AM +0100, Fekete Zoltán wrote: > Hi There, > > My current's build breaks with the message below for 2 weeks now. Could you > please help to resolve? > > /usr/tools/lib/gcc/x86_64--netbsd/6.5.0/../../../../x86_64--netbsd/bin/ld: >

Current build failure on AMD64

Hi There, My current's build breaks with the message below for 2 weeks now. Could you please help to resolve? /usr/tools/lib/gcc/x86_64--netbsd/6.5.0/../../../../x86_64--netbsd/bin/ld: libgcc_s_pic.a(enable-execute-stack.pico): file class ELFCLASS64 incompatible with ELFCLASS32

current build failure (gcc)

Hi, I get a different error than the build bot: nbgmake[1]: Entering directory `/usr/obj/tools/gcc/build/gcc' c++ -c -O -DIN_GCC -DCROSS_DIRECTORY_STRUCTURE -fno-exceptions -fno-rtti -fasynchronous-unwind-tables -W -Wall -Wno-narrowing -Wwrite-strings -Wcast-qual

Re: -current build failure of evbearm-el,Re: -current build failure of evbearm-el

Hi, From: Kamil Rytarowski , Date: Sun, 8 Jan 2017 02:23:34 +0100 > > > On 07.01.2017 12:17, Ryo ONODERA wrote: >> Hi, >> >> Recent NetBSD/evbearm-el-current build fails as follows. >> A build of NetBSD/amd64-current from same tree is fine. >> >> --- proc_bkpt.po --- >> In file

Re: -current build failure of evbearm-el

On 07.01.2017 12:17, Ryo ONODERA wrote: > Hi, > > Recent NetBSD/evbearm-el-current build fails as follows. > A build of NetBSD/amd64-current from same tree is fine. > > --- proc_bkpt.po --- > In file included from > /usr/world/7.99/evbearm-el/destdir/usr/include/sys/siginfo > .h:35:0, >

-current build failure of evbearm-el

Hi, Recent NetBSD/evbearm-el-current build fails as follows. A build of NetBSD/amd64-current from same tree is fine. --- proc_bkpt.po --- In file included from /usr/world/7.99/evbearm-el/destdir/usr/include/sys/siginfo .h:35:0, from

Re: current build failure automated messages

On July 20, Paul Goyette wrote: > For me, I'd be interested in another message that detailed changes in > the sets of Pass/Fail ATF tests. The "New test failures" and "Tests No > Longer Failing" lines are useful for me. As you may have noticed, email is now sent to current-users when an ATF

Re: current build failure automated messages

> Please make it thread properly to the original failure... Should be threaded now. -- Andreas Gustafsson, g...@gson.org

Re: current build failure automated messages

Joerg Sonnenberger wrote: > Please make it thread properly to the original failure... I'll see what I can do about that. -- Andreas Gustafsson, g...@gson.org

Re: current build failure automated messages

On Sun, Jul 31, 2016 at 12:26:58PM +0300, Andreas Gustafsson wrote: > As you may have noticed, the build server now sends email to > current-users not only when the i386 build breaks, but also > when it has been fixed, with the subject line > > Automated report: NetBSD-current/i386 build

Re: current build failure automated messages

As you may have noticed, the build server now sends email to current-users not only when the i386 build breaks, but also when it has been fixed, with the subject line Automated report: NetBSD-current/i386 build success -- Andreas Gustafsson, g...@gson.org

Re: current build failure automated messages

Paul Goyette wrote: > For me, I'd be interested in another message that detailed changes in > the sets of Pass/Fail ATF tests. The "New test failures" and "Tests No > Longer Failing" lines are useful for me. The "new test failures" part I have already implemented some time ago. I have been

Re: current build failure automated messages

Greg Troxel wrote: > I would like to see not only a build-ok message (on transition from fail > to pass), I have now implemented this, and it's being tested on my personal testbed before I deploy it on the TNF one. > but also a fail message on every fresh build during the > failure time, I

Re: current build failure automated messages

On Tue, 19 Jul 2016, Greg Troxel wrote: Andreas Gustafsson writes: I can appreciate that - different people have different preferences and workflows. I'd like to hear the opinions of other developers - if there is a consensus that "build has been fixed" email notifications

Re: current build failure automated messages

Andreas Gustafsson writes: > I can appreciate that - different people have different preferences > and workflows. I'd like to hear the opinions of other developers - > if there is a consensus that "build has been fixed" email notifications > would be useful, I can certainly add

Re: current build failure automated messages

Date:Tue, 19 Jul 2016 12:40:34 +0300 From:Andreas Gustafsson Message-ID: <22413.62866.53313.424...@guava.gson.org> | You don't have to screen scrape the HTML reports - you can get the | underlying data by anonymous rsync, as described in | |

Re: current build failure automated messages

Robert Elz wrote: > | If the page says "Build: OK" at the end, the issue has > | been fixed. At least for me, this is less work overall than it would > | be to handle twice the number of emails. > > I actually cannot imagine that being possible for me, one more e-mail to > delete every few

Re: current build failure automated messages

Date:Sat, 16 Jul 2016 12:15:41 +0300 From:Andreas Gustafsson Message-ID: <22409.64317.493648.115...@guava.gson.org> | It would not be hard to implement, but I'm not sure it would be useful | enough to justify doubling the number of messages to the

Re: current build failure automated messages

Robert Elz wrote: > From time to time there are messages to current-users about > build failures (the messages are generally useful even if sometimes > the content - just what failed - can be most obscure ... but that's > not the point of this message.) > > I was wondering if it would be possible

current build failure automated messages

>From time to time there are messages to current-users about build failures (the messages are generally useful even if sometimes the content - just what failed - can be most obscure ... but that's not the point of this message.) I was wondering if it would be possible to also send "build now

Re: -current build failure: table has too many members

On Wed, Oct 14, 2015 at 11:54:41PM +0200, Thomas Klausner wrote: > I haven't seen this one before, but just now it popped up: > > > --- glapi_gentable.po --- > ERROR: glapi_gentable.c: sou _glapi_table has too many members: 1155 > 1023 > Removing glapi_gentable.po > *** [glapi_gentable.po] Error

-current build failure: table has too many members

I haven't seen this one before, but just now it popped up: --- glapi_gentable.po --- ERROR: glapi_gentable.c: sou _glapi_table has too many members: 1155 > 1023 Removing glapi_gentable.po *** [glapi_gentable.po] Error code 1 nbmake[6]: stopped in /archive/foreign/src/external/mit/xorg/lib/libGL

Re: NetBSD/evbearmv7hf-el -current build failure

Hi, From: Martin Husemann mar...@duskware.de, Date: Thu, 2 Jul 2015 09:48:53 +0200 On Thu, Jul 02, 2015 at 04:03:19AM +0900, Ryo ONODERA wrote: Hi, I have gotten the following error. I did something wrong? Can you try removing $OBJDIR/compat/arm/oabi and then retry the build.sh? I have

Re: amd64 -current build failure

Glad to hear it wasn't something stupid I have done... I see that - it has been going through the build today - not yet finished. Thanks, Chavdar On Wed, 13 May 2015 at 13:26 Christos Zoulas chris...@astron.com wrote: In article CAG0OUxj83ke25NM2O6MnWpbKbF77y09ET=

Re: amd64 -current build failure

In article CAG0OUxjTbSQZF48uDHkheM5ZEgQoPqnBPXcxRs=tjuzbeaj...@mail.gmail.com, Chavdar Ivanov ci4...@gmail.com wrote: -=-=-=-=-=- Glad to hear it wasn't something stupid I have done... I see that - it has been going through the build today - not yet finished. If there is any consolation, my

amd64 -current build failure

Hi, My overnight build of -current (only amd64 on this machine) failed due to lack of disk space. The day before there was more than 200GB free on the filesystem in question. I found the following file at the end: ... -- total 473048080 -rw-r--r-- 1 sysbuild sysbuild 68521 May 11

Re: amd64 -current build failure

In article CAG0OUxj83ke25NM2O6MnWpbKbF77y09ET=0ae1osn8w25b0...@mail.gmail.com, Chavdar Ivanov ci4...@gmail.com wrote: Hi, My overnight build of -current (only amd64 on this machine) failed due to lack of disk space. The day before there was more than 200GB free on the filesystem in question. I

Re: xz -current build failure

On 4/17/15 1:17 PM, bch wrote: includes === lib/../external/mit/expat/lib/libexpat includes === lib/../external/public-domain/sqlite/lib includes === lib/../external/public-domain/xz/lib #create lib/pub-lzma.h rm -f pub-lzma.h /usr/src/obj/tooldir.NetBSD-7.99.9-amd64/bin/nbcat

xz -current build failure

includes === lib/../external/mit/expat/lib/libexpat includes === lib/../external/public-domain/sqlite/lib includes === lib/../external/public-domain/xz/lib #create lib/pub-lzma.h rm -f pub-lzma.h /usr/src/obj/tooldir.NetBSD-7.99.9-amd64/bin/nbcat

Re: -current build failure

On 8 March 2015 at 04:22, Christos Zoulas chris...@astron.com wrote: In article CABfrOT9xEj5GzGVxva-=hvtoyXbx4ZtY5f=l8fvmq-y8fvd...@mail.gmail.com, bch brad.har...@gmail.com wrote: === 10 extra files in DESTDIR = Files in DESTDIR but missing from flist. File is obsolete or flist

Re: -current build failure

On 8 March 2015 at 15:31, Christos Zoulas chris...@astron.com wrote: In article CAK4o1Wy1FtqSek+MX9TO_DwWsjTNjN=1toj-0ujhdmytrzl...@mail.gmail.com, Justin Cormack jus...@specialbusservice.com wrote: sys/rump/kern/lib/libsys_linux is not building either: Pooka has stashed more syscall build

Re: -current build failure

In article CAK4o1Wy1FtqSek+MX9TO_DwWsjTNjN=1toj-0ujhdmytrzl...@mail.gmail.com, Justin Cormack jus...@specialbusservice.com wrote: sys/rump/kern/lib/libsys_linux is not building either: Pooka has stashed more syscall build stuff... Fixed. christos

Re: -current build failure

In article CABfrOT9xEj5GzGVxva-=hvtoyXbx4ZtY5f=l8fvmq-y8fvd...@mail.gmail.com, bch brad.har...@gmail.com wrote: === 10 extra files in DESTDIR = Files in DESTDIR but missing from flist. File is obsolete or flist is out of date ? --

-current build failure

=== 10 extra files in DESTDIR = Files in DESTDIR but missing from flist. File is obsolete or flist is out of date ? -- ./stand/amd64-xen/7.99.6/modules/dtrace_syscall_linux