Re: make universe fails with MAKEOBJDIRPREFIX [cross builds part: sh: ./make_keys: Exec format error for init_keytry.h]

[Mark Millard]

Quoting:

> --- lib/ncurses/ncurses__L ---
> ./make_keys keys.list > init_keytry.h
. . .
> --- lib/ncurses/ncurses__L ---
> sh: ./make_keys: Exec format error
> *** [init_keytry.h] Error code 126


Since the reworking of the build handling in recent (many) months "sh: 
./make_keys: Exec format error" is a long standing problem for buildworld for 
cross builds. The native part of the build execution is trying to execute the 
cross-build target's make_keys (that was likely left from a prior cross-build 
and now doing incremental-build activity). lib/ncurses/ncurses__L is not the 
only place that this can happen. There is past list exchanges for this issue 
with other examples.

I rebuild after cleanworld when this happens in order to force a full rebuild 
instead of an incremental one --but I only build one cross build target at a 
time, not universe. I've never had such an after-cleanworld rebuild fail: only 
some later incremental builds.

Luckily in my experience so far most incremental builds do not go back through 
those areas (such as lib/ncurses/ncurses__L ) and so do not try to execute 
make_keys (stated in terms of this example). So the incremental builds for me 
are usually effective --but sometimes lib/ncurses/ncurses__L is rebuilt.

It has been a fairly long time since my 11.0 related activities (tracking 
stable/11 now) have run into this but likely lib/ncurses/ncurses__L (and the 
like) simply have not rebuilt in my cross builds. I've no head (CURRENT) 
activities going on at this point.

===
Mark Millard
markmi at dsl-only.net

___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

make universe fails with MAKEOBJDIRPREFIX

[Eric van Gyzen]

"make universe" consistently fails in buildworld when I set MAKEOBJDIRPREFIX.
I'm running head r306046 on amd64 and building head r306380.  There are only
comments in /etc/make.conf.  My complete command is:

make universe JFLAG=-j16 MAKEOBJDIRPREFIX=/work/universe \
> /usr/obj/build-logs/universe.log 2>&1  init_keytry.h
--- lib/libpam/libpam__L ---
cc -isystem /work/universe/mips.mips/usr/src/tmp/usr/include -L/work/universe/mi
ps.mips/usr/src/tmp/usr/lib -B/work/universe/mips.mips/usr/src/tmp/usr/lib --sys
root=/work/universe/mips.mips/usr/src/tmp -B/work/universe/mips.mips/usr/src/tmp
/usr/bin -fpic -DPIC -g -O -pipe -I/usr/src/lib/libpam/libpam/../../../contrib/o
penpam/include -DLIB_MAJ=6 -DHAVE_DLFUNC=1 -DHAVE_FDLOPEN=1 -DHAVE_FPURGE=1 -DHA
VE_STRLCAT=1 -DHAVE_STRLCPY=1 -G0   -DOPENPAM_DEBUG -MD  -MF.depend.openpam_strl
cpy.pico -MTopenpam_strlcpy.pico -std=iso9899:1999 -Wsystem-headers -Werror -Wal
l -Wno-format-y2k -W -Wno-unused-parameter -Wstrict-prototypes -Wmissing-prototy
pes -Wpointer-arith -Wreturn-type -Wcast-qual -Wwrite-strings -Wswitch -Wshadow
-Wunused-parameter -Wcast-align -Wchar-subscripts -Winline -Wnested-externs -Wre
dundant-decls -Wold-style-definition -Wno-pointer-sign -c /usr/src/lib/libpa
m/libpam/../../../contrib/openpam/lib/libpam/openpam_strlcpy.c -o openpam_strlcp
y.pico
--- lib/libthr__L ---
--- thr_detach.o ---
--- lib/ncurses/ncurses__L ---
sh: ./make_keys: Exec format error
*** [init_keytry.h] Error code 126

make[5]: stopped in /usr/src/lib/ncurses/ncurses
--- lib/libthr__L ---
cc -isystem /work/universe/mips.mips/usr/src/tmp/usr/include -L/work/universe/mi
ps.mips/usr/src/tmp/usr/lib -B/work/universe/mips.mips/usr/src/tmp/usr/lib --sys
root=/work/universe/mips.mips/usr/src/tmp -B/work/universe/mips.mips/usr/src/tmp
/usr/bin  -O -pipe -G0   -DPTHREAD_KERNEL -I/usr/src/lib/libthr/../libc/include
-I/usr/src/lib/libthr/thread  -I/usr/src/lib/libthr/../../include -I/usr/src/lib
/libthr/arch/mips/include -I/usr/src/lib/libthr/sys -I/usr/src/lib/libthr/../../
libexec/rtld-elf -I/usr/src/lib/libthr/../../libexec/rtld-elf/mips -I/usr/src/li
b/libthr/../libthread_db -Winline -fexceptions -D_PTHREAD_FORCED_UNWIND -D_PTHRE
ADS_INVARIANTS -MD  -MF.depend.thr_detach.o -MTthr_detach.o -std=gnu99 -Wsystem-
headers -Werror -Wall -Wno-format-y2k -W -Wno-unused-parameter -Wstrict-prototyp
es -Wmissing-prototypes -Wpointer-arith -Wno-uninitialized -Wno-pointer-sign
 -c /usr/src/lib/libthr/thread/thr_detach.c -o thr_detach.o
--- lib/ncurses/ncurses__L ---
1 error

make[5]: stopped in /usr/src/lib/ncurses/ncurses
*** [lib/ncurses/ncurses__L] Error code 2
==
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: IPFW: shape and status in CURRENT

[O. Hartmann]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Am Thu, 29 Sep 2016 21:02:16 +0200
"O. Hartmann"  schrieb:

> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA256
> 
> 
> Since a couple of months now, I use IPFW on several projects. I use IPFW 
> again after a
> long term hiatus since ~ 2003. Before I used pf. The reasons are mannyfold 
> and one
> reason is very dogmatic - it is the FreeBSD's native firewall and several 
> performance
> diagrams shown in the net tells me a significant performance benefit in case 
> being
> setup optimal over pf. pf in FreeBSD lacks behind the OpenBSD's development.
> 
> Since last year I try to setup IPFW only on all of our systems. So I do also 
> at home
> and at some places, where we have to use NAT via PPPoE/modem. And here the 
> struggle
> begins. While most setups of a firewall on a router/gateway with several NICs 
> directly
> attached to the internet with on interface, the outbound interface, the same 
> starts to
> be a horrible story when it comes to NAT.
> 
> The handbook offers some simple examples, but in most cases, I see the 
> supposed to be
> outdated external natd daemon still in favour over in-kernel NAT! This is 
> also the
> case with the manpage for ipfw(8). I miss a more recent example of setting up 
> NAT with
> in-kernel NAT and the caveats of one-pass and none-one-pass and some hints 
> how the IP
> packet's header gets rewritten when being translated by NAT and reinjected 
> into the
> pipeline. For me, as a non-source-code-expert-and-simple-system's 
> administrator, it is
> sometimes hard to understand how IPFW works. And the problems reported do 
> tell me that
> I'm not alone.
> 
> The handbook has some examples. One of them contains a traversal of 37/TCP, 
> timeserver.
> It is a long time since I saw this kind of setup, most time synchronisation 
> methods use
> NTP and 123/UDP. The example also seems a bit outdated.
> 
> Manpage firewall(7) lacks also of an modern in-kernel NAT example - it still 
> referes to
> the natd. Also, there is a kind of anti-spoof rule shown that leaves the 
> impression that
> this page is quite antique. Doesn't IPFW has a antispoof rule, or even 
> "verrepath" as
> the manpage ipfw(8) states?
> 
> Somehow I miss some more detailed explanations what happens with check-state, 
> since this
> causes much trouble, even in combination with NAT.
> 
> Well, as said, I'm no expert, maybe I'm simply too blunt to understand, but 
> again, it
> seems I'm not alone. People switched to pf and even Apple moved from ipfw to 
> pf. That
> leaves the question here: what is the status of the development of IPFW in 
> FreeBSD? is
> it maintained-only or is there development going on? Are there plans for 
> refurbished,
> more up to time man pages and examples?
> 
> Thanks in advance and for your patience reading my bad English.
> 
> Oliver

[...]

Looking at firewall(7) and trying to simply fowllow the example, one will 
discover that
rules

 add 01500 deny all from not 10.0.1.0/24 in via fxp1
 add 01500 deny all from not 10.0.2.0/24 in via fxp2
 add 01501 deny all from 10.0.1.0/24 in via fxp0
 add 01501 deny all from 10.0.2.0/24 in via fxp0

will produce a "missing to" error in recent IPFW (it is the case in my 
installation of
CURRENT, hope it does not differ from yours)
-BEGIN PGP SIGNATURE-
Version: GnuPG v2

iQEcBAEBCAAGBQJX7pyyAAoJEOgBcD7A/5N8I44IAK10SPfEeSH+JGGOBeExMLUt
HSP6lZHtzvprl6t2HaJzqOhl/Xu2jAKbBBjcdLcCZ5kP6qGsKvR1fySuz/0l42dO
rtnQMqwuuDEIsvA8LScTkPkDK7VtCUpD8xJEQ4jnCfhtk4qoGAZAV9+JlNdr3l1d
LNee2rAi9jhO5JcI3JRLLQIIOla+YMQKcMOwzLHGYfxuTFbp2qyQNSQpIFc3HilH
tX3owVeJw9yNmTrC3VYOt1NwdknrolEHOG3KeWdpEtNu7UA+31dkcom+qy1JTpuN
/KvkOGykVaPoUEO2CYjO2cFBB7bm3rk8UXoEr4doCVex05dl97ElP0W168dC1fk=
=BSxQ
-END PGP SIGNATURE-
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

aibs(4) / atk0110 support for newer systems

[Andriy Gapon]

I've written a patch for aibs(4) (also known as ASUS AI Booster and ATK0110)
that adds support for discovering and querying sensors using newer GGRP ("get
group"?) and GITM ("get item"?) methods:
https://people.freebsd.org/~avg/aibs-ggrp-gitm.diff

If you are using the driver could you please test that the patch does not break
it for you?
If you have an ASUS motherboard where aibs does not find sensors could you
please check if there is any improvement with the patch?
Testing the patch should be as easy as building, installing and loading aibs
module (found in sys/modules/acpi/aibs).  Well, also don't forget to apply the
patch with patch -p1 :-)

-- 
Andriy Gapon
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

FreeBSD 11.0 i386 buildworld failure

[Robert Burmeister]

FreeBSD 11.0 i386 Stable

I successfully upgraded from FreeBSD 10.3 to 11.0 Stable on 23 September 2016.
Upon refreshing and rebuilding world to catch the 28 September 2016 Release 
update,
buildworld failed using the same build options that had worked for the 22 Sept 
code.
Tail:

--- all_subdir_usr.bin ---
--- all_subdir_usr.bin/kdump ---
--- .depend ---
echo kdump.full: /usr/obj/usr/src/tmp/usr/lib/libc.a 
/usr/obj/usr/src/tmp/usr/lib/libsysdecode.a 
/usr/obj/usr/src/tmp/usr/lib/libcasper.a 
/usr/obj/usr/src/tmp/usr/lib/libcap_grp.a 
/usr/obj/usr/src/tmp/usr/lib/libcap_pwd.a >> .depend

--- kdump_subr.o ---
clang -O2 -fno-strict-aliasing -pipe -march=core2  
-I/usr/src/usr.bin/kdump/../ktrace -I/usr/src/usr.bin/kdump 
-I/usr/src/usr.bin/kdump/../.. -I. -DHAVE_LIBCASPER -g -MD  
-MF.depend.kdump_subr.o -MTkdump_subr.o -std=gnu99 -fstack-protector-strong 
-Wsystem-headers -Wall -Wno-format-y2k -W -Wno-unused-parameter 
-Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Wreturn-type 
-Wcast-qual -Wwrite-strings -Wswitch -Wshadow -Wunused-parameter -Wcast-align 
-Wchar-subscripts -Winline -Wnested-externs -Wredundant-decls 
-Wold-style-definition -Wno-pointer-sign -Wmissing-variable-declarations 
-Wthread-safety -Wno-empty-body -Wno-string-plus-int 
-Wno-unused-const-variable  -Qunused-arguments  -c kdump_subr.c -o kdump_subr.o

--- all_subdir_usr.bin/drill ---
/usr/src/usr.bin/drill/../../contrib/ldns/drill/error.c:74:1: warning: no 
previous prototype for function 'verbose' [-Wmissing-prototypes]

verbose(const char *fmt, ...)
^
/usr/src/usr.bin/drill/../../contrib/ldns/drill/error.c:88:1: warning: no 
previous prototype for function 'vverbose' [-Wmissing-prototypes]

vverbose(const char *fmt, ...)
^
/usr/src/usr.bin/drill/../../contrib/ldns/drill/error.c:108:1: warning: no 
previous prototype for function 'debug' [-Wmissing-prototypes]

debug(const char *fmt, ...)
^
3 warnings generated.
--- all_subdir_usr.sbin ---
--- ops_cdfs.o ---
clang -O2 -fno-strict-aliasing -pipe -march=core2  
-I/usr/src/usr.sbin/amd/amd/../../../contrib/amd/amd  
-I/usr/obj/usr/src/tmp/usr/include/rpcsvc -I. -I/usr/src/usr.sbin/amd/amd 
-I/usr/src/usr.sbin/amd/amd/../include 
-I/usr/obj/usr/src/usr.sbin/amd/amd/../include 
-I/usr/src/usr.sbin/amd/amd/../../../contrib/amd/include 
-I/usr/src/usr.sbin/amd/amd/../../../contrib/amd -DHAVE_CONFIG_H 
-DHOST_CPU=\"i386\" -DHOST_ARCH=\"i386\" -g -MD  -MF.depend.ops_cdfs.o 
-MTops_cdfs.o -std=gnu99 -fstack-protector-strong -Wsystem-headers -Werror 
-Wno-pointer-sign -Wno-empty-body -Wno-string-plus-int 
-Wno-unused-const-variable -Wno-tautological-compare -Wno-unused-value 
-Wno-parentheses-equality -Wno-unused-function -Wno-enum-conversion 
-Wno-unused-local-typedef -Wno-switch -Wno-switch-enum 
-Wno-knr-promoted-parameter -Wno-parentheses  -Qunused-arguments  -c 
/usr/src/usr.sbin/amd/amd/../../../contrib/amd/amd/ops_cdfs.c -o ops_cdfs.o

--- all_subdir_usr.bin ---
--- all_subdir_usr.bin/kdump ---
kdump_subr.c:1424:7: error: use of undeclared identifier 'TRAP_CAP'
--- all_subdir_usr.bin/drill ---
--- root.o ---
--- all_subdir_usr.bin/kdump ---
case TRAP_CAP:
 ^
--- all_subdir_usr.bin/drill ---
clang -O2 -fno-strict-aliasing -pipe 
-I/usr/src/usr.bin/drill/../../contrib/ldns -march=core2  -g -MD  
-MF.depend.root.o -MTroot.o -std=gnu99 -fstack-protector-strong 
-Wsystem-headers -Wall -Wno-format-y2k -W -Wno-unused-parameter 
-Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Wreturn-type 
-Wcast-qual -Wwrite-strings -Wswitch -Wshadow -Wunused-parameter -Wcast-align 
-Wchar-subscripts -Winline -Wnested-externs -Wredundant-decls 
-Wold-style-definition -Wno-pointer-sign -Wmissing-variable-declarations 
-Wthread-safety -Wno-empty-body -Wno-string-plus-int 
-Wno-unused-const-variable  -Qunused-arguments  -c 
/usr/src/usr.bin/drill/../../contrib/ldns/drill/root.c -o root.o

--- all_subdir_usr.bin/kdump ---
1 error generated.
*** [kdump_subr.o] Error code 1

make[4]: stopped in /usr/src/usr.bin/kdump
1 error

make[4]: stopped in /usr/src/usr.bin/kdump
*** [all_subdir_usr.bin/kdump] Error code 2

make[3]: stopped in /usr/src/usr.bin
--- all_subdir_usr.sbin ---
A failure has been detected in another branch of the parallel make

make[5]: stopped in /usr/src/usr.sbin/amd/amd
*** [all_subdir_usr.sbin/amd/amd] Error code 2

make[4]: stopped in /usr/src/usr.sbin/amd
1 error

make[4]: stopped in /usr/src/usr.sbin/amd
*** [all_subdir_usr.sbin/amd] Error code 2

make[3]: stopped in /usr/src/usr.sbin
1 error

make[3]: stopped in /usr/src/usr.sbin
*** [all_subdir_usr.sbin] Error code 2

make[2]: stopped in /usr/src
--- all_subdir_usr.bin ---
--- all_subdir_usr.bin/drill ---
A failure has been detected in another branch of the parallel make

make[4]: stopped in /usr/src/usr.bin/drill
*** [all_subdir_usr.bin/drill] Error code 2

make[3]: stopped in /usr/src/usr.bin
--- all_subdir_usr.bin/clang ---
--- all_subdir_usr.bin/clang/clang-tblgen ---
A failure has been detected 

Re: [patch] Improving the 'zpool labelclear' command

[Ganael LAPLANCHE]

On Thu, 29 Sep 2016 14:13:52 -0400, Ultima wrote

> > In case you are interested, I have posted a patch to improve the 'zpool
> > labelclear' command here :
> >
> > https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=204622
> >
> > - force ('-f') will now allow to erase labels, even if they are broken
> > (restoring the behaviour of our previous -FreeBSD- version of
labelclear)
> > - You can select which label you want to erase (beginning, end or
> > specific index)
> > - You can use a 'minimal' mode which will invalidate a label by changing
> > only a single byte. This is useful to minimize the chances to
> > overwrite/destroy a FS that would have been created over the label, but
> > still leaving the label visible.
>
> This patch looks good its too bad the core hasn't looked at it 
> yet. Ill do some testing and report any issues found. Some 
> points you bring up in the bug are quite valid. Thanks for 
> working on this! =]

Thanks. Yes, it would be nice if a src committer could take a look at it.

Any feedback welcome :)

--
Ganael LAPLANCHE 
http://www.martymac.org | http://contribs.martymac.org
FreeBSD: martymac , http://www.FreeBSD.org
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"