pflow(4) in 9.0 ?
Hello, Will pflow(4) be available on 9.0 ? There is a if_pflow.h in pf's code but no manual page. Thanks, regards. ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
update from old current (october) to 9.0 beta fails in installworld
Hello, Looks like I've broke my soekris net5501 while doing installworld (built with clang) === libexec/rtld-elf (install) chflags noschg /usr/libexec/ld-elf.so.1 install -s -o root -g wheel -m 555 -C -b -fschg -S ld-elf.so.1 /libexec install -o root -g wheel -m 444 rtld.1.gz /usr/share/man/man1 *** Signal 4 Stop in /usr/src/libexec/rtld-elf. *** Error code 1 # ls Instruction interdite(core dumped) (instruction interdite = illegal/forbidden instruction) Are there known issues for updating (I didn't follow the single user step to install the world, as usual, because the box is only reachable via ssh) ? Thanks for 9.0, looks nice. Regards. ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
9.0 RC1/Clang / illegal instruction (Signal 4) in gengtype while building cc_tools on i586.
Hello,
On my Soekris net5501 (AMD Geode i586 CPU) clang make buildworld fails
on an illegal instruction nopw %cs:0x0(%eax,%eax,1).
# make buildworld
...
ranlib libiberty.a
clang -O2 -pipe -I. -DGCCVER=\4.2\ -DIN_GCC -DHAVE_CONFIG_H -DPREFIX=\/usr\
-I/usr/obj/usr/src/gnu/usr.bin/cc/cc_tools/../cc_tools
-I/usr/src/gnu/usr.bin/cc/cc_tools/../cc_tools
-I/usr/src/gnu/usr.bin/cc/cc_tools/../../../../contrib/gcc
-I/usr/src/gnu/usr.bin/cc/cc_tools/../../../../contrib/gcc/config
-I/usr/src/gnu/usr.bin/cc/cc_tools/../../../../contrib/gcclibs/include
-I/usr/src/gnu/usr.bin/cc/cc_tools/../../../../contrib/gcclibs/libcpp/include
-I/usr/src/gnu/usr.bin/cc/cc_tools/../../../../contrib/gcclibs/libdecnumber -g
-DGENERATOR_FILE -DHAVE_CONFIG_H -std=gnu89
-I/usr/obj/usr/src/tmp/legacy/usr/include
-L/usr/obj/usr/src/tmp/legacy/usr/lib -o gengtype gengtype.o
gengtype-yacc+%DIKED.o gengtype-lex.o errors.o libiberty.a
clang: warning: argument unused during compilation: '-g'
clang: warning: argument unused during compilation: '-std=gnu89'
./gengtype
*** Signal 4
Stop in /usr/src/gnu/usr.bin/cc/cc_tools.
*** Error code 1
# cd /usr/obj/usr/src/gnu/usr.bin/cc/cc_tools
# gdb ./gengtype
(gdb) r
Starting program: /usr/obj/usr/src/gnu/usr.bin/cc/cc_tools/gengtype
Program received signal SIGILL, Illegal instruction.
0x08048b24 in do_typedef (s=0x80532bf CUMULATIVE_ARGS, pos=0x805e1a4)
at /usr/src/gnu/usr.bin/cc/cc_tools/../../../../contrib/gcc/gengtype.c:103
103 {
(gdb) disas 0x08048b24
Dump of assembler code for function do_typedef:
0x08048b10 do_typedef+0: push %ebp
0x08048b11 do_typedef+1: mov%esp,%ebp
0x08048b13 do_typedef+3: push %ebx
0x08048b14 do_typedef+4: push %edi
0x08048b15 do_typedef+5: push %esi
0x08048b16 do_typedef+6: sub$0xc,%esp
0x08048b19 do_typedef+9: mov$0x805e1d4,%edi
0x08048b1e do_typedef+14: mov0x10(%ebp),%esi
0x08048b21 do_typedef+17: mov0x8(%ebp),%ebx
0x08048b24 do_typedef+20: nopw %cs:0x0(%eax,%eax,1)
/etc/make.conf for clang (same as the wiki)
.if !defined(CC) || ${CC} == cc
CC=clang
.endif
.if !defined(CXX) || ${CXX} == c++
CXX=clang++
.endif
.if !defined(CPP) || ${CPP} == cpp
CPP=clang -E
.endif
# Don't die on warnings
NO_WERROR=
WERROR=
# Don't forget this when using Jails!
#NO_FSCHG=
--
Help will be welcome.
Thanks regards.
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: 9.0 RC1/Clang / illegal instruction (Signal 4) in gengtype while building cc_tools on i586.
Le Sat, 22 Oct 2011 20:51:29 +0200, Patrick Lamaiziere patf...@davenulle.org a écrit : On my Soekris net5501 (AMD Geode i586 CPU) clang make buildworld fails on an illegal instruction nopw %cs:0x0(%eax,%eax,1). I've found a test program from Roman Divacky to check the CPU as clang (http://lev.vlakno.cz/~rdivacky/Host.cpp) It returns cpu = pentium, looks good. ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: 9.0 RC1/Clang / illegal instruction (Signal 4) in gengtype while building cc_tools on i586.
Le Sun, 23 Oct 2011 12:11:05 +0200, Roman Divacky rdiva...@freebsd.org a écrit : Long nops are supported only on specific CPUs. Unconditional use of them is a plain bug, like unconditional use of cmovXX. Yes, it's a bug, I filed http://llvm.org/bugs/show_bug.cgi?id=11212 upstream. Patric, as a temporary workaround please add -no-integrated-as to your CFLAGS, that will make clang use gnu as instead of its own intergrated assembler, thus avoiding this problem. Unless you think that it will be helpful to test with the workaround, I would prefer to test patches from llvm (it takes days to build FreeBSD on a net5501...). This proves it is useful to test with uncommon hardware, and I would like to check the crypto engine, hifn(4) and glxsb(4) built with llvm (that worked fine around january). Thanks a lot, regards. ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: [Freebsd 9] [amd64] [USB] [HPLIP] what's the (new) right way to manage hplip usb-plugged printers, running Freebsd 9
Le Sat, 29 Oct 2011 21:58:53 +0200, Jilles Tjoelker jil...@stack.nl a écrit : On Sat, Oct 29, 2011 at 04:10:46PM +0200, David Marec wrote: So, what's should be the news groupuser's rights required by HPLIP/cups on FreeBSD 9 ? And, how to handle them with devd ? Use devfs rules. Pasting from http://www.stack.nl/~jilles/unix/freebsd-devfs.txt Create or edit /etc/devfs.rules and put something like this in it: [devfsrules_mybox=10] add path 'fd0*' mode 660 The problem is that the printer appears as ugenXXX.Y, but other usb devices (disk, usb-key, ...) also have an entry in /dev/ugen/ You really don't want to allow the users to access these devices, but *only* the printer. This is why we use a devd rule that test the type of the device. I don't think we can do this with devfs. And the ugen number differs if the usb port is not always the same. Regards. ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: pkgng suggestion: renaming /usr/sbin/pkg to /usr/sbin/pkg-bootstrap
Le Fri, 24 Aug 2012 00:27:13 +0200, Baptiste Daroussin b...@freebsd.org a écrit : Hello, So, opinions? There may still be time to fix it for 9.1 if we can decide quickly. I do personnally have no opinion on this, I have hesitated long between both before choosing /usr/sbin/pkg. I'm interested in other's opinion. I was hit by this: install poudriere, forgot to install pkgng (yes it is documented...). Run poudriere bulk, it will be stuck waiting an user input (it does not output anything too) and it closes the poudriere jail juste after a key is pressed. I've spent sometime to understand why pkg was waiting on the tty wchan... So yes this is confusing IMO. Regards. ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: Clang as default compiler November 4th
Le Mon, 10 Sep 2012 16:12:07 -0500, Brooks Davis bro...@freebsd.org a écrit : Hello, For the past several years we've been working towards migrating from GCC to Clang/LLVM as our default compiler. We intend to ship FreeBSD 10.0 with Clang as the default compiler on i386 and amd64 platforms. To this end, we will make WITH_CLANG_IS_CC the default on i386 and amd64 platforms on November 4th. Last time I've checked on 9.X [mid August, FreeBSD clang version 3.1 (branches/release_31 156863) 20120523], Clang still produces invalid code (some nopl (%eax)) for the AMD Geode LX (i586 CPU found on some ALIX board or Soekris NET5501). I don't know if this is also a concern with older CPU (Pentium 2/1) ? http://llvm.org/bugs/show_bug.cgi?id=11212 http://lists.freebsd.org/pipermail/freebsd-current/2011-October/028588.html http://www.freebsd.org/cgi/query-pr.cgi?pr=bin/168253 What does the mean to you? Well, I will not be able to run FreeBSD from scratch on my soekris :-) Best regards. ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: r245741 (clang as cc) can not build binaries for GEODE processor
Le Fri, 22 Feb 2013 16:45:58 +0400, Lev Serebryakov l...@freebsd.org a écrit : Hello, Hello, Daniel. You wrote 22 февраля 2013 г., 16:04:11: DN I'm not familiar with NanoBSD, but does it do the package builds DN for you - or do you do those by hand? DN If it's the latter, I don't quite understand how the compiler is DN supposed to know the target CPUTYPE? It is latter, but IMHO, _without_ any CPUTYPE set, system compiler should generate generic enough binaries to run on all supported CPUs of target platform (i386 in this case). Clang should work now if march=geode (see: http://llvm.org/bugs/show_bug.cgi?id=11212 ) But I agree that by default on i386, the code should work on i386... Looks like this is not true anymore (= i686 ?). Regards. ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: [Call for Tests] PAT issue on Apple hardware
Le Mon, 15 Nov 2010 20:36:42 -0500, Jung-uk Kim j...@freebsd.org a écrit : Often times I hear complaints like my Mac hangs after upgrading to 8.1 or snapshot CD hangs on my brand new Mac. I know some of these complaints started happening when we switched to new PAT layout. It is so puzzling because it never happened on non-Apple hardware, AFAIK. I really like to fix this problem but I cannot afford a Mac. :-P Thanks. If you are one of those lucky people, please test the attached patch and report your hardware model and any improvement or regression. Shall we test if the model is not listed in the patch and already works fine? (I'm using a MacBookPro3,1 on FreeBSD 8.1) if (strncmp(sysenv, MacBook5,1, 10) strncmp(sysenv, MacBookPro5,5, strncmp(sysenv, Macmini3,1, 10) strncmp(sysenv, iMac9,1, 7) == 0) Regards. ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: Cleanup for cryptographic algorithms vs. compiler optimizations
Le Sun, 13 Jun 2010 23:35:12 +0200, Bernd Walter ti...@cicely7.cicely.de a écrit : Go back to the originating mail. Crypto code wasn't aware of this problem and this is a way more obviuous optimization than function exchange. And I do believe that the programmers were clever people. Alarming, isn't it? The removal of dead store by gcc is recent. There was a discussion about this problem on the linux crypto mailing list, see: http://www.mail-archive.com/linux-cry...@vger.kernel.org/msg04229.html If i remember well, they have introduced a secure_memset() function or something like that, but I do not find this piece of code any more. Regards. ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
