Re: android bsd connectivity tools etc ?
On 08/13/14 19:47, Julian H. Stacey wrote: Hi, Any tips for Android / FreeBSD BSD tools for connectivity etc ? I just got a Samsung Galaxy Note 3, with Android 4.4.2 kernel 3.4.0 [...] Any URLs, tips, comments welcome, Thanks Cheers, Julian audio/gmtp from ports does the job for me (Samsung Galaxy S2, Kyocera Event). -- George ___ 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: RFT vidcontrol for vt(4)
On 05/12/14 11:25, Nathan Whitehorn wrote: [...] Is there any reason not to have kbdmux be mandatory at this point? [...] Does this mean mandatory in the sense that the kbdmux driver always gets built and loaded, or that the kbdmux driver must always be in operation (treating all keyboard-like devices as a single unified source of keystrokes)? I could live with the first, but there are definitely times that I want multiple independent keyboards on a system to be considered unrelated to one another. -- George ___ 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: Hello fdclose
On 03/21/14 20:51, Dag-Erling Smørgrav wrote: Warner Losh i...@bsdimp.com writes: It does serve a useful purpose, though, which is why it has endured. If you were to have a man page that said ‘Putc(3) returns …’ then the automated tools (and web links) that find Putc.3 wouldn’t be able to since it doesn’t exist. Moreover - if FreeBSD were written in Pascal, it might not matter, but in C, _exit(2) and _Exit(3) are two different functions. (I'm sure there are other examples without a leading underscore) (eww, starting a sentence with a non-alphabetic character would be even worse...) DES Etc., etc., etc. Wouldn't it be more productive to spend this effort on recasting the sentence in question so that it doesn't start with a word that starts with a small letter? -- George ___ 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: cron(8) improvement
On 11/09/13 21:23, Allan Jude wrote: On 2013-11-09 21:13, Adrian Chadd wrote: On 9 November 2013 17:58, Allan Jude free...@allanjude.com wrote: Well, if the rc.conf config is specific to the daemon being installed by the package, then the existing /etc/rc.conf.d/ system works fine, it just falls down a little on xorg configuring hald, unless you just make the xorg package create /etc/rc.conf.d/hald and /etc/rc.conf.d/dbus If I install hal/dbus, why wouldn't they themselves populate /etc/rc.conf.d/hald and /etc/rc.conf.d/dbus ? If there are hal/dbus options that need configuring by other packages, then sure, you'll need to add some other things too. ahh, right, why didn't I think of that I like the simplicity of rc.conf, and I would much rather not involve an sqlite database, I am not sure how that could possibly be faster then sourcing an extra shell script. Don't focus on that. The sqlite example is just that - an example - showing what kind of operations you would want to implement to _allow_ you to do that. I'm not advocating for doing it in freebsd-base. The point I'm making is this: * when populating rc.conf.d/, don't just do 'cp' in a post-install script * when populating the cron daemon entries in rc.cron.d, don't just 'cp' in a post-install script. -adrian If the cron daemon is just scanning /etc/cron.d/* and treating it as if those lines had been appended to /etc/crontab I don't see why you couldn't just cp in the post-install. I think it would be better if you didn't have to 'register' a change. For this whole thread, please s,/etc/rc.d,/usr/local/etc/rc.d,g -- George ___ 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: make buildworld
On 10/22/13 20:55, Mateusz Guzik wrote: On Tue, Oct 22, 2013 at 07:49:21PM -0500, Saul A. Peebsen wrote: OK, here's a bit of history of this box. Never wanted to run CURRENT, but had no choice, STABLE wouldn't boot. So I followed all the advice how to disable all debugging features. Now I'm trying to build latest 10 and I'm getting the error below. What's wrong? cc -O2 -pipe -march=core2 -I/usr/src/lib/libc/include -I/usr/src/lib/libc/../../include -I/usr/src/lib/libc/amd64 -DNLS -D__DBINTERFACE_PRIVATE -I/usr/src/lib/libc/../../contrib/gdtoa -I/usr/src/lib/libc/../../contrib/libc-vis -DINET6 -I/usr/obj/usr/src/lib/libc -I/usr/src/lib/libc/resolv -D_ACL_PRIVATE -DPOSIX_MISTAKE -I/usr/src/lib/libc/../../contrib/jemalloc/include -DMALLOC_PRODUCTION -I/usr/src/lib/libc/../../contrib/tzcode/stdtime -I/usr/src/lib/libc/stdtime -I/usr/src/lib/libc/locale -DBROKEN_DES -DPORTMAP -DDES_BUILTIN -I/usr/src/lib/libc/rpc -DYP -DNS_CACHING -DSYMBOL_VERSIONING -std=gnu99 -Qunused-arguments -fstack-protector -Wsystem-headers -Werror -Wall -Wno-format-y2k -Wno-uninitialized -Wno-pointer-sign -Wno-empty-body -Wno-string-plus-int -Wno-tautological-compare -Wno-unused-value -Wno-parentheses-equality -Wno-unused-function -Wno-conversion -Wno-switch -Wno-switch-enum -Wno-knr-promoted-parameter -c jemalloc_jemalloc.c -o jemalloc_jemalloc.o In file included from jemalloc_jemalloc.c:2: In file included from /usr/src/lib/libc/../../contrib/jemalloc/include/jemalloc/internal/jemalloc_internal.h:64: In file included from /usr/src/lib/libc/../../contrib/jemalloc/include/jemalloc/internal/../jemalloc.h:18: /usr/src/lib/libc/../../contrib/jemalloc/include/jemalloc/internal/../jemalloc_FreeBSD.h:7:9: error: 'MALLOC_PRODUCTION' macro redefined [-Werror] #define MALLOC_PRODUCTION ^ command line:6:9: note: previous definition is here #define MALLOC_PRODUCTION 1 ^ 1 error generated. *** Error code 1 Presumably you have MALLOC_PRODUCTION set in src.conf or make.conf, remove it. Ran into this myself. More specifically, you have MALLOC_PRODUCTION set to something other than the null string. jemalloc_FreeBSD.h, however, says #define MALLOC_PRODUCTION. This is okay if you have MALLOC_PRODUCTION= in src.conf/make.conf, and this is okay if you don't have MALLOC_PRODUCTION in those files, but if you have it set to foo, or y, or even no, you will get this compile error. -- George ___ 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: rcs
On 10/09/13 03:20, Hans Ottevanger wrote: On 10/08/13 04:31, Lyndon Nerenberg wrote: Okay folks, can we make a call about keeping the RCS tools in the base? The proponents wanting to remove RCS need to speak up and make their technical case. Technically it is quite simple: I need RCS to start versioning config files, even before starting any customization. I know about several others who do the same (and have not yet defected to Linux). I would like to see RCS to be put back into the tree for 10.0. If it really -has- to be victimized by the current anti-GPL crusade, it could be replaced by OpenRCS in 11. And as a long time hard-core user I would appreciate if this kind of changes were performed only after at least -some- public discussion. The way this change was sneaked in (though apparently with approval of core@), reminds me more of a Secret Society than of an Open Source project. Regards, Hans ___ 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 +1, enthusiastically. -- George ___ 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: [Heads Up] RCS removed from base
On 10/07/13 20:28, John-Mark Gurney wrote: Julian Elischer wrote this message on Tue, Oct 08, 2013 at 08:01 +0800: not a big thing but I believe that a lot of poeple use ci/co on /etc becasue it is just there +1 Folks, this is just plain a major violation of the Principle of Least Amazement. RCS is ideal for keeping track of my configuration files in /etc. What do we gain by removing it? Roughly 640 kilobytes of executable code and 60 kilobytes of compressed man pages. Had the community that hangs our on this mailing list heard about this when it could still have been described as a proposal, as opposed to a fait accompli, I would have described it as the epitome of a Half Baked Idea. -- George ___ 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: ulpt can't attach Lexmark E120
On 08/25/13 04:44, Hans Petter Selasky wrote: On 08/24/13 20:21, George Mitchell wrote: Setting hw.usb.dwc_otg.debug to any value greater than 0 generates an unending stream of debug output and effectively locks up the chip scrolling the output on the display. Perhaps there are some specific debug messages I could put in ... -- George Hi, Can you try this patch: http://svnweb.freebsd.org/changeset/base/254828 --HPS ___ 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 Finally my RPi build system is working again and I can happily report that my Lexmark printer attaches successfully! Thank you! (And I note the patch has been checked into the repository.) -- George ___ 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: ulpt can't attach Lexmark E120
On 08/25/13 19:20, George Mitchell wrote: On 08/25/13 04:44, Hans Petter Selasky wrote: On 08/24/13 20:21, George Mitchell wrote: Setting hw.usb.dwc_otg.debug to any value greater than 0 generates an unending stream of debug output and effectively locks up the chip scrolling the output on the display. Perhaps there are some specific debug messages I could put in ... -- George Hi, Can you try this patch: http://svnweb.freebsd.org/changeset/base/254828 --HPS ___ [...] I started trying to do too many things at once, and as a result it's going to take me a little while to try this patch out. My apologies! -- George Now that I have put my RPi build environment back together, I hope to try your patch tonight. Sorry for the delay! -- George ___ 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: ulpt can't attach Lexmark E120
On 08/25/13 04:44, Hans Petter Selasky wrote: On 08/24/13 20:21, George Mitchell wrote: Setting hw.usb.dwc_otg.debug to any value greater than 0 generates an unending stream of debug output and effectively locks up the chip scrolling the output on the display. Perhaps there are some specific debug messages I could put in ... -- George Hi, Can you try this patch: http://svnweb.freebsd.org/changeset/base/254828 --HPS ___ 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 Sorry, no more progress yet. My RPi build system is generating emptyimages for some reason, so I will start over with it. -- George ___ 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: ulpt can't attach Lexmark E120
On 08/25/13 04:44, Hans Petter Selasky wrote: On 08/24/13 20:21, George Mitchell wrote: Setting hw.usb.dwc_otg.debug to any value greater than 0 generates an unending stream of debug output and effectively locks up the chip scrolling the output on the display. Perhaps there are some specific debug messages I could put in ... -- George Hi, Can you try this patch: http://svnweb.freebsd.org/changeset/base/254828 --HPS ___ [...] I started trying to do too many things at once, and as a result it's going to take me a little while to try this patch out. My apologies! -- George ___ 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: ulpt can't attach Lexmark E120
On 08/24/13 02:14, Hans Petter Selasky wrote: On 08/24/13 02:44, George Mitchell wrote: On 08/23/13 07:11, George Mitchell wrote: On 08/23/13 02:18, Hans Petter Selasky wrote: On 08/23/13 02:29, George Mitchell wrote: On 08/22/13 07:34, Hans Petter Selasky wrote: Give that the printer works fine with the same code on my amd64 machines, does this suggest we have a byte-ordering problem in the driver? -- George Hi, I looked at the code and your debug prints, and it looks like the usbd_transfer_setup() function is to blame. To get further debugging here, you need to enable hw.usb.debug=15 and hw.usb.dwcotg.debug=15 or something like that. error = usbd_transfer_setup(uaa-device, iface_index, sc-sc_xfer, ulpt_config, ULPT_N_TRANSFER, sc, sc-sc_mtx); I think this should be trivial to fix one the cause is found. --HPS Setting hw.usb.dwc_otg.debug to any value greater than 0 generates an unending stream of debug output and effectively locks up the chip scrolling the output on the display. Perhaps there are some specific debug messages I could put in ... -- George ___ 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: ulpt can't attach Lexmark E120
On 08/23/13 02:18, Hans Petter Selasky wrote: On 08/23/13 02:29, George Mitchell wrote: On 08/22/13 07:34, Hans Petter Selasky wrote: Here's the result: [...] (at which point if I type control-c to stop usbdump, the system gets a fatal kernel mode translation fault, but that's another story.) Hope this helps. -- George I would expect to see some messages ERR != 0 when you plug the device. Can you show both usbdump output and dmesg output which belongs together? --HPS Not sure exactly how I would get the usbdump output and log output interspersed in the correct order, and the fact that the pi panics when I type control-C at usbdump doesn't help. Subjectively, the ulpt0 attach returned 12 seemed to occur a fraction of a second later than the others. But I'll see what I can come up with this evening. -- George ___ 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: ulpt can't attach Lexmark E120
On 08/23/13 07:11, George Mitchell wrote: On 08/23/13 02:18, Hans Petter Selasky wrote: On 08/23/13 02:29, George Mitchell wrote: On 08/22/13 07:34, Hans Petter Selasky wrote: Here's the result: [...] (at which point if I type control-c to stop usbdump, the system gets a fatal kernel mode translation fault, but that's another story.) Hope this helps. -- George I would expect to see some messages ERR != 0 when you plug the device. Can you show both usbdump output and dmesg output which belongs together? --HPS Not sure exactly how I would get the usbdump output and log output interspersed in the correct order, and the fact that the pi panics when I type control-C at usbdump doesn't help. Subjectively, the ulpt0 attach returned 12 seemed to occur a fraction of a second later than the others. But I'll see what I can come up with this evening. -- George Well, what I ended up doing is turning on ulpt debugging and then piping usbdump into logger, yielding the attachment. But I'm not 100% sure that the output is in the proper sequence. Give that the printer works fine with the same code on my amd64 machines, does this suggest we have a byte-ordering problem in the driver? -- George Aug 24 00:10:24 pi kernel: ugen0.5: Lexmark International at usbus0 Aug 24 00:10:24 pi kernel: ulpt_probe: Aug 24 00:10:24 pi kernel: ulpt_probe: Aug 24 00:10:24 pi kernel: ulpt_attach: sc=0xc2d46a00 Aug 24 00:10:24 pi kernel: ulpt0: Lexmark International Lexmark E120n, class 0/0, rev 2.00/1.00, addr 5 on usbus0 Aug 24 00:10:24 pi kernel: ulpt_attach: setting alternate config number: 0 Aug 24 00:10:24 pi kernel: ulpt_attach: error=USB_ERR_INVAL Aug 24 00:10:24 pi kernel: ulpt_detach: sc=0xc2d46a00 Aug 24 00:10:24 pi kernel: device_attach: ulpt0 attach returned 12 Aug 24 00:10:24 pi george: 00:08:02.619534 usbus0.5 SUBM-CTRL-EP=,SPD=FULL,NFR=1,SLEN=8,IVAL=0 Aug 24 00:10:24 pi george: 00:08:02.620189 usbus0.5 DONE-CTRL-EP=,SPD=FULL,NFR=1,SLEN=0,IVAL=0,ERR=0 Aug 24 00:10:24 pi george: 00:08:02.620282 usbus0.5 SUBM-CTRL-EP=,SPD=FULL,NFR=1,SLEN=0,IVAL=0 Aug 24 00:10:24 pi george: 00:08:02.621186 usbus0.5 DONE-CTRL-EP=,SPD=FULL,NFR=1,SLEN=0,IVAL=0,ERR=0 Aug 24 00:10:24 pi george: 00:08:02.638617 usbus0.5 SUBM-CTRL-EP=0080,SPD=FULL,NFR=2,SLEN=8,IVAL=0 Aug 24 00:10:24 pi george: 00:08:02.640299 usbus0.5 DONE-CTRL-EP=0080,SPD=FULL,NFR=2,SLEN=8,IVAL=0,ERR=0 Aug 24 00:10:24 pi george: 00:08:02.640802 usbus0.5 SUBM-CTRL-EP=0080,SPD=FULL,NFR=2,SLEN=8,IVAL=0 Aug 24 00:10:24 pi george: 00:08:02.643668 usbus0.5 DONE-CTRL-EP=0080,SPD=FULL,NFR=2,SLEN=20,IVAL=0,ERR=0 Aug 24 00:10:24 pi george: 00:08:02.643831 usbus0.5 SUBM-CTRL-EP=0080,SPD=FULL,NFR=2,SLEN=8,IVAL=0 Aug 24 00:10:24 pi george: 00:08:02.646289 usbus0.5 DONE-CTRL-EP=0080,SPD=FULL,NFR=2,SLEN=4,IVAL=0,ERR=0 Aug 24 00:10:24 pi george: 00:08:02.646389 usbus0.5 SUBM-CTRL-EP=0080,SPD=FULL,NFR=2,SLEN=8,IVAL=0 Aug 24 00:10:24 pi george: 00:08:02.648294 usbus0.5 DONE-CTRL-EP=0080,SPD=FULL,NFR=2,SLEN=4,IVAL=0,ERR=0 Aug 24 00:10:24 pi george: 00:08:02.648404 usbus0.5 SUBM-CTRL-EP=0080,SPD=FULL,NFR=2,SLEN=8,IVAL=0 Aug 24 00:10:24 pi george: 00:08:02.650283 usbus0.5 DONE-CTRL-EP=0080,SPD=FULL,NFR=2,SLEN=4,IVAL=0,ERR=0 Aug 24 00:10:24 pi george: 00:08:02.650380 usbus0.5 SUBM-CTRL-EP=0080,SPD=FULL,NFR=2,SLEN=8,IVAL=0 Aug 24 00:10:24 pi george: 00:08:02.658667 usbus0.5 DONE-CTRL-EP=0080,SPD=FULL,NFR=2,SLEN=16,IVAL=0,ERR=0 Aug 24 00:10:24 pi george: 00:08:02.658783 usbus0.5 SUBM-CTRL-EP=0080,SPD=FULL,NFR=2,SLEN=8,IVAL=0 Aug 24 00:10:24 pi george: 00:08:02.661289 usbus0.5 DONE-CTRL-EP=0080,SPD=FULL,NFR=2,SLEN=4,IVAL=0,ERR=0 Aug 24 00:10:24 pi george: 00:08:02.661386 usbus0.5 SUBM-CTRL-EP=0080,SPD=FULL,NFR=2,SLEN=8,IVAL=0 Aug 24 00:10:24 pi george: 00:08:02.664291 usbus0.5 DONE-CTRL-EP=0080,SPD=FULL,NFR=2,SLEN=44,IVAL=0,ERR=0 Aug 24 00:10:24 pi george: 00:08:02.664404 usbus0.5 SUBM-CTRL-EP=0080,SPD=FULL,NFR=2,SLEN=8,IVAL=0 Aug 24 00:10:24 pi george: 00:08:02.666289 usbus0.5 DONE-CTRL-EP=0080,SPD=FULL,NFR=2,SLEN=4,IVAL=0,ERR=0 Aug 24 00:10:24 pi george: 00:08:02.666387 usbus0.5 SUBM-CTRL-EP=0080,SPD=FULL,NFR=2,SLEN=8,IVAL=0 Aug 24 00:10:24 pi george: 00:08:02.668663 usbus0.5 DONE-CTRL-EP=0080,SPD=FULL,NFR=2,SLEN=28,IVAL=0,ERR=0 Aug 24 00:10:24 pi george: 00:08:02.668850 usbus0.5 SUBM-CTRL-EP=0080,SPD=FULL,NFR=2,SLEN=8,IVAL=0 Aug 24 00:10:24 pi george: 00:08:02.671284 usbus0.5 DONE-CTRL-EP=0080,SPD=FULL,NFR=2,SLEN=12,IVAL=0,ERR=0 Aug 24 00:10:24 pi george: 00:08:02.671411 usbus0.5 SUBM-CTRL-EP=0080,SPD=FULL,NFR=2,SLEN=8,IVAL=0 Aug 24 00:10:24 pi george: 00:08:02.678038 usbus0.5 DONE-CTRL-EP=0080,SPD=FULL,NFR=2,SLEN=32,IVAL=0,ERR=0 Aug 24 00:10:24 pi george: 00:08:02.678144 usbus0.5 SUBM-CTRL-EP
Re: Re: ulpt can't attach Lexmark E120
As I was saying a few minutes ago ... On 01/27/13 17:32, George Mitchell wrote: On 01/27/13 14:07, Hans Petter Selasky wrote: [...] I need output when hw.usb.ulpt.debug=15 to say exactly. Could you ask the provider of the binaries to compile having USB_DEBUG set, also for the modules. --HPS I'm working on getting a debug build ... Thanks for your help so far. I notice that there seem to be only trivial differences between the 9.1 release ulpt and the 10.0 current ulpt driver. -- George (This is on a Raspberry Pi.) It took me a bit longer than anticipated, but here is the output, from an image built over last weekend: Aug 22 11:15:09 pi kernel: ugen0.5: Lexmark International at usbus0 Aug 22 11:15:09 pi kernel: ulpt_probe: Aug 22 11:15:09 pi kernel: ulpt_probe: Aug 22 11:15:09 pi kernel: ulpt_attach: sc=0xc2d43800 Aug 22 11:15:09 pi kernel: ulpt0: Lexmark International Lexmark E120n, class 0/0, rev 2.00/1.00, addr 5 on usbus0 Aug 22 11:15:09 pi kernel: ulpt_attach: setting alternate config number: 0 Aug 22 11:15:09 pi kernel: ulpt_attach: error=USB_ERR_INVAL Aug 22 11:15:09 pi kernel: ulpt_detach: sc=0xc2d43800 Aug 22 11:15:09 pi kernel: device_attach: ulpt0 attach returned 12 ___ 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: ulpt can't attach Lexmark E120
On 08/22/13 07:34, Hans Petter Selasky wrote: On 08/22/13 13:24, George Mitchell wrote: As I was saying a few minutes ago ... On 01/27/13 17:32, George Mitchell wrote: On 01/27/13 14:07, Hans Petter Selasky wrote: [...] I need output when hw.usb.ulpt.debug=15 to say exactly. Could you ask the provider of the binaries to compile having USB_DEBUG set, also for the modules. --HPS I'm working on getting a debug build ... Thanks for your help so far. I notice that there seem to be only trivial differences between the 9.1 release ulpt and the 10.0 current ulpt driver. -- George (This is on a Raspberry Pi.) It took me a bit longer than anticipated, but here is the output, from an image built over last weekend: Hi, Could you run: usbdump -i usbusX -f Y -s 65536 To get a dump of the USB activity when you plug the device? The message in question is not important, and might be changed to not cancel the ulpt attach routine. --HPS ___ 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 Here's the result: root@pi:/ # usbdump -i usbus0 -f 4 -s 65536 00:26:01.592494 usbus0.4 SUBM-CTRL-EP=,SPD=FULL,NFR=1,SLEN=8,IVAL=0 00:26:01.593117 usbus0.4 DONE-CTRL-EP=,SPD=FULL,NFR=1,SLEN=0,IVAL=0,ERR=0 00:26:01.593209 usbus0.4 SUBM-CTRL-EP=,SPD=FULL,NFR=1,SLEN=0,IVAL=0 00:26:01.594146 usbus0.4 DONE-CTRL-EP=,SPD=FULL,NFR=1,SLEN=0,IVAL=0,ERR=0 00:26:01.611621 usbus0.4 SUBM-CTRL-EP=0080,SPD=FULL,NFR=2,SLEN=8,IVAL=0 00:26:01.614223 usbus0.4 DONE-CTRL-EP=0080,SPD=FULL,NFR=2,SLEN=8,IVAL=0,ERR=0 00:26:01.614730 usbus0.4 SUBM-CTRL-EP=0080,SPD=FULL,NFR=2,SLEN=8,IVAL=0 00:26:01.617595 usbus0.4 DONE-CTRL-EP=0080,SPD=FULL,NFR=2,SLEN=20,IVAL=0,ERR=0 00:26:01.617758 usbus0.4 SUBM-CTRL-EP=0080,SPD=FULL,NFR=2,SLEN=8,IVAL=0 00:26:01.620216 usbus0.4 DONE-CTRL-EP=0080,SPD=FULL,NFR=2,SLEN=4,IVAL=0,ERR=0 00:26:01.620313 usbus0.4 SUBM-CTRL-EP=0080,SPD=FULL,NFR=2,SLEN=8,IVAL=0 00:26:01.622219 usbus0.4 DONE-CTRL-EP=0080,SPD=FULL,NFR=2,SLEN=4,IVAL=0,ERR=0 00:26:01.622326 usbus0.4 SUBM-CTRL-EP=0080,SPD=FULL,NFR=2,SLEN=8,IVAL=0 00:26:01.624208 usbus0.4 DONE-CTRL-EP=0080,SPD=FULL,NFR=2,SLEN=4,IVAL=0,ERR=0 00:26:01.624305 usbus0.4 SUBM-CTRL-EP=0080,SPD=FULL,NFR=2,SLEN=8,IVAL=0 00:26:01.631722 usbus0.4 DONE-CTRL-EP=0080,SPD=FULL,NFR=2,SLEN=16,IVAL=0,ERR=0 00:26:01.631925 usbus0.4 SUBM-CTRL-EP=0080,SPD=FULL,NFR=2,SLEN=8,IVAL=0 00:26:01.634217 usbus0.4 DONE-CTRL-EP=0080,SPD=FULL,NFR=2,SLEN=4,IVAL=0,ERR=0 00:26:01.634315 usbus0.4 SUBM-CTRL-EP=0080,SPD=FULL,NFR=2,SLEN=8,IVAL=0 00:26:01.637220 usbus0.4 DONE-CTRL-EP=0080,SPD=FULL,NFR=2,SLEN=44,IVAL=0,ERR=0 00:26:01.637334 usbus0.4 SUBM-CTRL-EP=0080,SPD=FULL,NFR=2,SLEN=8,IVAL=0 00:26:01.639214 usbus0.4 DONE-CTRL-EP=0080,SPD=FULL,NFR=2,SLEN=4,IVAL=0,ERR=0 00:26:01.639312 usbus0.4 SUBM-CTRL-EP=0080,SPD=FULL,NFR=2,SLEN=8,IVAL=0 00:26:01.641585 usbus0.4 DONE-CTRL-EP=0080,SPD=FULL,NFR=2,SLEN=28,IVAL=0,ERR=0 00:26:01.641769 usbus0.4 SUBM-CTRL-EP=0080,SPD=FULL,NFR=2,SLEN=8,IVAL=0 00:26:01.644209 usbus0.4 DONE-CTRL-EP=0080,SPD=FULL,NFR=2,SLEN=12,IVAL=0,ERR=0 00:26:01.644316 usbus0.4 SUBM-CTRL-EP=0080,SPD=FULL,NFR=2,SLEN=8,IVAL=0 00:26:01.651213 usbus0.4 DONE-CTRL-EP=0080,SPD=FULL,NFR=2,SLEN=32,IVAL=0,ERR=0 00:26:01.651316 usbus0.4 SUBM-CTRL-EP=0080,SPD=FULL,NFR=2,SLEN=8,IVAL=0 00:26:01.653219 usbus0.4 DONE-CTRL-EP=0080,SPD=FULL,NFR=2,SLEN=4,IVAL=0,ERR=0 00:26:01.653321 usbus0.4 SUBM-CTRL-EP=,SPD=FULL,NFR=1,SLEN=8,IVAL=0 00:26:01.654584 usbus0.4 DONE-CTRL-EP=,SPD=FULL,NFR=1,SLEN=0,IVAL=0,ERR=0 (at which point if I type control-c to stop usbdump, the system gets a fatal kernel mode translation fault, but that's another story.) Hope this helps. -- George ___ 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: After a source upgrade from 8.3-RELEASE to r249432 (HEAD)
On 04/15/13 20:57, Mark Johnston wrote: On Mon, Apr 15, 2013 at 03:58:26PM -0400, George Mitchell wrote: It was pretty successful. All my 8.3 packages are still running very happily, though at some point I imagine I will have to update and recompile them. But ... When I press ENTER in the boot0 screen, I get the hyphen that will start spinning after a timeout and begin loading boot1 (which, as far as I know, I have not updated). boot1 (I think) presents me with a prompt that does not respond to key presses on the keyboard. It times out and continues loading anyway. At this stage, I am always presented with a manual mountroot: prompt, and I have to type ufs:/dev/ada0s1a to get any further. I ran into this too. It was caused by a problem in r249408 and is fixed as of r249436. Updating your kernel to something beyond r249435 should make this go away. -Mark Thanks! I have a compile going and I'll check the result later today. -- George ___ 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: After a source upgrade from 8.3-RELEASE to r249432 (HEAD)
On 04/15/13 20:57, Mark Johnston wrote: On Mon, Apr 15, 2013 at 03:58:26PM -0400, George Mitchell wrote: It was pretty successful. All my 8.3 packages are still running very happily, though at some point I imagine I will have to update and recompile them. But ... When I press ENTER in the boot0 screen, I get the hyphen that will start spinning after a timeout and begin loading boot1 (which, as far as I know, I have not updated). boot1 (I think) presents me with a prompt that does not respond to key presses on the keyboard. It times out and continues loading anyway. At this stage, I am always presented with a manual mountroot: prompt, and I have to type ufs:/dev/ada0s1a to get any further. I ran into this too. It was caused by a problem in r249408 and is fixed as of r249436. Updating your kernel to something beyond r249435 should make this go away. -Mark Yes, r249436 fixes the mountroot problem. -- George ___ 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
After a source upgrade from 8.3-RELEASE to r249432 (HEAD)
It was pretty successful. All my 8.3 packages are still running very happily, though at some point I imagine I will have to update and recompile them. But ... When I press ENTER in the boot0 screen, I get the hyphen that will start spinning after a timeout and begin loading boot1 (which, as far as I know, I have not updated). boot1 (I think) presents me with a prompt that does not respond to key presses on the keyboard. It times out and continues loading anyway. At this stage, I am always presented with a manual mountroot: prompt, and I have to type ufs:/dev/ada0s1a to get any further. Does this just mean I should update the boot code? Presumably fdisk -B won't change anything. Should I just do bsdlabel -B? (It's an MBR disk.) Aside from this glitch, I'm very happy with how smoothly the update went. And I wouldn't be complaining, except that I'm tired of having to type ufs:/dev/ada0s1a every time I boot. -- George Mitchell ___ 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: After a source upgrade from 8.3-RELEASE to r249432 (HEAD)
On 04/15/13 18:09, Sean Bruno wrote: On Mon, 2013-04-15 at 15:58 -0400, George Mitchell wrote: that does not respond to key presses on the keyboard. It times out and continues loading anyway. At this stage, I am always presented with a manual mountroot: prompt, and I have to type ufs:/dev/ada0s1a to get any further. Hrm ... is /dev/ada0s1a the default root disk in your /etc/fstab ? Sean Yes: # DeviceMountpoint FStype Options Dump Pass# /dev/ada0s1bnoneswapsw 0 0 /dev/ada0s1a/ ufs rw 1 1 [...] ___ 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: After a source upgrade from 8.3-RELEASE to r249432 (HEAD)
On 04/15/13 18:52, Kimmo Paasiala wrote: On Tue, Apr 16, 2013 at 1:44 AM, George Mitchell george+free...@m5p.com wrote: On 04/15/13 18:09, Sean Bruno wrote: On Mon, 2013-04-15 at 15:58 -0400, George Mitchell wrote: that does not respond to key presses on the keyboard. It times out and continues loading anyway. At this stage, I am always presented with a manual mountroot: prompt, and I have to type ufs:/dev/ada0s1a to get any further. Hrm ... is /dev/ada0s1a the default root disk in your /etc/fstab ? Sean Yes: # DeviceMountpoint FStype Options Dump Pass# /dev/ada0s1bnoneswapsw 0 0 /dev/ada0s1a/ ufs rw 1 1 [...] Change the order so that the root device is the first in /etc/fstab. -Kimmo ___ 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 I tried that and there was no change. I still get the mountroot: prompt and have to type ufs:/dev/ada0s1a. -- George ___ 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: devel/gobject-introspection failure on ARM
On 01/28/13 05:55, Koop Mast wrote: On Sun, 2013-01-27 at 10:57 -0500, George Mitchell wrote: System: Raspberry Pi uname: r245840M (Alie Tan's image from 25 January) ports: svnversion 308518 Build dies with message sizeof(ArrayTypeBlob) is expected to be 8 but is 12. (Complete build log attached.) I made a naive attempt to fix it by rearranging the order of the structure members, but obviously I don't understand structure packing on the ARM and it didn't help. It also didn't get rid of the huge number of cast increases required alignment of target type warnings. I note we're at version 0.10.8 of this package, but upstream is at 1.34.2. (It requires glib 2.34.1, though, and we're only at 2.28.8). What's the best way to proceed? -- George Mitchell I'm currently in the process of making a patch [1] for the ports tree for glib 2.34.3 and gobject-introspection 1.34.1.1. If you want to give this a shot on ARM. Please note that the patch is WIP. Not all ports have been tested yet. -Koop [1] http://people.freebsd.org/~kwm/glib-2.34_1.diff Thanks! I'll try this if I have time later today. -- George ___ 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
devel/gobject-introspection failure on ARM
System: Raspberry Pi uname: r245840M (Alie Tan's image from 25 January) ports: svnversion 308518 Build dies with message sizeof(ArrayTypeBlob) is expected to be 8 but is 12. (Complete build log attached.) I made a naive attempt to fix it by rearranging the order of the structure members, but obviously I don't understand structure packing on the ARM and it didn't help. It also didn't get rid of the huge number of cast increases required alignment of target type warnings. I note we're at version 0.10.8 of this package, but upstream is at 1.34.2. (It requires glib 2.34.1, though, and we're only at 2.28.8). What's the best way to proceed? -- George Mitchell typescript.xz Description: Binary data ___ 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
ulpt can't attach Lexmark E120
System: Raspberry Pi uname: r245840M (Alie Tan's image from 25 January) By comparison, this Lexmark E120 printer attaches and prints with no difficulty on FreeBSD-9.1-RELEASE, but on CURRENT, it says: ugen0.5: Lexmark International at usbus0 ulpt1: Lexmark International Lexmark E120n, class 0/0, rev 2.00/1.00, addr 5 on usbus0 device_attach: ulpt1 attach returned 12 Also, an HP CM1015 attaches without a problem. What should I try next? -- George Mitchell ___ 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: ulpt can't attach Lexmark E120
On 01/27/13 11:33, Hans Petter Selasky wrote: On Sunday 27 January 2013 17:14:55 George Mitchell wrote: System: Raspberry Pi uname: r245840M (Alie Tan's image from 25 January) By comparison, this Lexmark E120 printer attaches and prints with no difficulty on FreeBSD-9.1-RELEASE, but on CURRENT, it says: ugen0.5: Lexmark International at usbus0 ulpt1: Lexmark International Lexmark E120n, class 0/0, rev 2.00/1.00, addr 5 on usbus0 device_attach: ulpt1 attach returned 12 Also, an HP CM1015 attaches without a problem. What should I try next? Also try to set: sysctl hw.usb.ulpt.debug=15 It's a non-debug build of ulpt, so that doesn't exist: sysctl: unknown oid 'hw.usb.ulpt.debug': No such file or directory before attaching. Also try to attach one printer alone. --HPS After unplugging the HP: root@pi:/home/george # usbconfig ugen0.1: OTG Root HUB DWCOTG at usbus0, cfg=0 md=HOST spd=HIGH (480Mbps) pwr=SAVE ugen0.2: product 0x9512 vendor 0x0424 at usbus0, cfg=0 md=HOST spd=HIGH (480Mbps) pwr=SAVE ugen0.3: product 0xec00 vendor 0x0424 at usbus0, cfg=0 md=HOST spd=HIGH (480Mbps) pwr=ON ugen0.4: Lexmark E120n Lexmark International at usbus0, cfg=0 md=HOST spd=FULL (12Mbps) pwr=ON I attached the usbdump output, though there seem to be quite a few packets not connected with ulpt burying the interesting packets in the noise. -- George ulpt.usbdump.xz Description: Binary data ___ 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: ulpt can't attach Lexmark E120
On 01/27/13 13:15, Hans Petter Selasky wrote: [...] Hi, I don't see any errors in the usbdump trace you sent. So we can at least rule that out. Hint: You can filter traffic using the -f option for usbdump. What does: usbconfig dump_device_desc dump_curr_config_desc output? Can you also get same output from working system? --HPS Attachment 1 from Raspberry Pi. Attachment 2 from 9.1-RELEASE on amd64. -- George [...] ugen0.4: Lexmark E120n Lexmark International at usbus0, cfg=0 md=HOST spd=FULL (12Mbps) pwr=ON bLength = 0x0012 bDescriptorType = 0x0001 bcdUSB = 0x0200 bDeviceClass = 0x bDeviceSubClass = 0x bDeviceProtocol = 0x bMaxPacketSize0 = 0x0010 idVendor = 0x043d idProduct = 0x00cc bcdDevice = 0x0100 iManufacturer = 0x0001 Lexmark International iProduct = 0x0002 Lexmark E120n iSerialNumber = 0x0003 9947W2Z bNumConfigurations = 0x0001 Configuration index 0 bLength = 0x0009 bDescriptorType = 0x0002 wTotalLength = 0x0020 bNumInterfaces = 0x0001 bConfigurationValue = 0x0001 iConfiguration = 0x no string bmAttributes = 0x00c0 bMaxPower = 0x0001 Interface 0 bLength = 0x0009 bDescriptorType = 0x0004 bInterfaceNumber = 0x bAlternateSetting = 0x bNumEndpoints = 0x0002 bInterfaceClass = 0x0007 bInterfaceSubClass = 0x0001 bInterfaceProtocol = 0x0002 iInterface = 0x no string Endpoint 0 bLength = 0x0007 bDescriptorType = 0x0005 bEndpointAddress = 0x0001 OUT bmAttributes = 0x0002 BULK wMaxPacketSize = 0x0040 bInterval = 0x bRefresh = 0x bSynchAddress = 0x Endpoint 1 bLength = 0x0007 bDescriptorType = 0x0005 bEndpointAddress = 0x0088 IN bmAttributes = 0x0002 BULK wMaxPacketSize = 0x0020 bInterval = 0x bRefresh = 0x bSynchAddress = 0x [...] ugen0.2: Lexmark E120n Lexmark International at usbus0, cfg=0 md=HOST spd=FULL (12Mbps) pwr=ON bLength = 0x0012 bDescriptorType = 0x0001 bcdUSB = 0x0200 bDeviceClass = 0x bDeviceSubClass = 0x bDeviceProtocol = 0x bMaxPacketSize0 = 0x0010 idVendor = 0x043d idProduct = 0x00cc bcdDevice = 0x0100 iManufacturer = 0x0001 Lexmark International iProduct = 0x0002 Lexmark E120n iSerialNumber = 0x0003 9947W2Z bNumConfigurations = 0x0001 Configuration index 0 bLength = 0x0009 bDescriptorType = 0x0002 wTotalLength = 0x0020 bNumInterfaces = 0x0001 bConfigurationValue = 0x0001 iConfiguration = 0x no string bmAttributes = 0x00c0 bMaxPower = 0x0001 Interface 0 bLength = 0x0009 bDescriptorType = 0x0004 bInterfaceNumber = 0x bAlternateSetting = 0x bNumEndpoints = 0x0002 bInterfaceClass = 0x0007 bInterfaceSubClass = 0x0001 bInterfaceProtocol = 0x0002 iInterface = 0x no string Endpoint 0 bLength = 0x0007 bDescriptorType = 0x0005 bEndpointAddress = 0x0001 OUT bmAttributes = 0x0002 BULK wMaxPacketSize = 0x0040 bInterval = 0x bRefresh = 0x bSynchAddress = 0x Endpoint 1 bLength = 0x0007 bDescriptorType = 0x0005 bEndpointAddress = 0x0088 IN bmAttributes = 0x0002 BULK wMaxPacketSize = 0x0020 bInterval = 0x bRefresh = 0x bSynchAddress = 0x ___ 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: ulpt can't attach Lexmark E120
On 01/27/13 14:07, Hans Petter Selasky wrote: On Sunday 27 January 2013 19:24:01 George Mitchell wrote: On 01/27/13 13:15, Hans Petter Selasky wrote: [...] Hi, I don't see any errors in the usbdump trace you sent. So we can at least rule that out. Hint: You can filter traffic using the -f option for usbdump. What does: usbconfig dump_device_desc dump_curr_config_desc output? Can you also get same output from working system? --HPS Attachment 1 from Raspberry Pi. Attachment 2 from 9.1-RELEASE on amd64. -- George Hi, These look identical. I suspect it is a problem to allocate memory for the USB transfers. I need output when hw.usb.ulpt.debug=15 to say exactly. Could you ask the provider of the binaries to compile having USB_DEBUG set, also for the modules. --HPS I'm working on getting a debug build ... Thanks for your help so far. I notice that there seem to be only trivial differences between the 9.1 release ulpt and the 10.0 current ulpt driver. -- George ___ 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: Circular port dependency
On 01/11/13 19:41, George Mitchell wrote:
On 01/11/13 03:22, Gleb Kurtsou wrote:
On (10/01/2013 20:21), George Mitchell wrote:
I grabbed the ports tree as of 308518, the RELEASE_9_1_0 tag.
devel/libtool won't build, because it requires autom4te during the
configure phase. So I put BUILD_DEPENDS= autom4te:devel/autoconf
in the Makefile. But autoconf depends on gmake, which depends on
gettext, which depends on libiconv, which depends on libtool.
What to do?
[...]
It turns out that my problem was due to compiling on the Raspberry
Pi, a machine that is slow enough that this post-configure target in
the port's top-level Makefile:
post-configure:
@${FIND} ${WRKSRC} -type f | ${XARGS} ${TOUCH} -f
could end up setting the last write time for config.status earlier than
the last write time for configure, thereby triggering this make rule in
the port's own Makefile:
$(top_builddir)/config.status: $(top_srcdir)/configure
$(CONFIG_STATUS_DEPENDENCIES)
$(SHELL) ./config.status --recheck
It's this --recheck that would cause the build to try to run autom4ke,
leading to the circular dependency. So the correct fix is as attached,
guaranteeing that the config.status modification time will always be
later.
I'm not entirely sure why the post-configure rule is there in the first
place, and svnweb.freebsd.org refuses to show me anything in
ports/head/devel below liglogging. I was trying to look at the log
for ports/devel/Makefile to see how the post-configure rule got there,
because simply removing it also appears to make the build succeed. But
I assume it's there for some reason, and this fix seems to be less
antagonistic than removing the whole rule.-- George
--- Makefile.orig 2013-01-10 19:56:02.0 -0500
+++ Makefile2013-01-19 09:44:24.0 -0500
@@ -34,6 +34,6 @@
${WRKSRC}/configure ${WRKSRC}/libltdl/configure
post-configure:
- @${FIND} ${WRKSRC} -type f | ${XARGS} ${TOUCH} -f
+ @${FIND} ${WRKSRC} -type f -name config.status | ${XARGS} ${TOUCH} -f
.include bsd.port.mk
___
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
ctfconvert again
So I updated my FreeBSD machine to 9.1-RELEASE in the hope of getting past the ctfconvert problem that causes a build of 10-CURRENT to say: ERROR: ctfconvert: failed to initialize DWARF: Unimplemented code at [dwarf_init_attr(400)] while compiling every kernel source file. Then I checked out head as of 245422 into a different partition and tried make buildworld (ran okay) and make buildkernel (failed with the same error as before). Do I have to build an early version of head before I can build the current version of head? -- George Mitchell ___ 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: ctfconvert again
On 01/14/13 18:57, George Mitchell wrote: So I updated my FreeBSD machine to 9.1-RELEASE in the hope of getting past the ctfconvert problem that causes a build of 10-CURRENT to say: ERROR: ctfconvert: failed to initialize DWARF: Unimplemented code at [dwarf_init_attr(400)] while compiling every kernel source file. Then I checked out head as of 245422 into a different partition and tried make buildworld (ran okay) and make buildkernel (failed with the same error as before). I should mention this is an amd64 build, in case that matters. Do I have to build an early version of head before I can build the current version of head? -- George Mitchell ___ 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 ___ 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: ctfconvert again
On 01/14/13 19:21, Steven Hartland wrote: - Original Message - From: George Mitchell george+free...@m5p.com To: freebsd-current@freebsd.org Sent: Monday, January 14, 2013 11:57 PM Subject: ctfconvert again So I updated my FreeBSD machine to 9.1-RELEASE in the hope of getting past the ctfconvert problem that causes a build of 10-CURRENT to say: ERROR: ctfconvert: failed to initialize DWARF: Unimplemented code at [dwarf_init_attr(400)] while compiling every kernel source file. Then I checked out head as of 245422 into a different partition and tried make buildworld (ran okay) and make buildkernel (failed with the same error as before). Do I have to build an early version of head before I can build the current version of head? -- George Mitchell I believe the location of ctfconvert which is used is broken so unless your system has a version of ctfconvert which includes the attr fix you will always get this :( The reason I believe this is:- make buildenv Entering world for amd64:amd64 # which ctfconvert /usr/bin/ctfconvert # which cc /usr/obj/usr/home/smh/freebsd/base/head/tmp/usr/bin/cc So where I believe ctfconvert should be being picked up from the toolchain its not. I've had a quick dig in the Makefile's but I don't know them well at all and so couldn't find an easy fix :( The workaround I'm using is: make -DNO_CTF buildkernel Works like a charm; thanks! -- George Mitchell If someone who better knows the make system could suggest a patch so that ctfconvert (and potentially other tools) are build and detected in the toolchain that would be most appreciated. Regards Steve This e.mail is private and confidential between Multiplay (UK) Ltd. and the person or entity to whom it is addressed. In the event of misdirection, the recipient is prohibited from using, copying, printing or otherwise disseminating it or any information contained in it. In the event of misdirection, illegible or incomplete transmission please telephone +44 845 868 1337 or return the E.mail to postmas...@multiplay.co.uk. ___ 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: Circular port dependency
On 01/11/13 03:22, Gleb Kurtsou wrote: On (10/01/2013 20:21), George Mitchell wrote: I grabbed the ports tree as of 308518, the RELEASE_9_1_0 tag. devel/libtool won't build, because it requires autom4te during the configure phase. So I put BUILD_DEPENDS= autom4te:devel/autoconf in the Makefile. But autoconf depends on gmake, which depends on gettext, which depends on libiconv, which depends on libtool. What to do? Build devel/gmake defining WITHOUT_NLS: # cd /usr/ports/devel/gmake make -DWITHOUT_NLS all install Why would anybody want NLS support in make in a first place? I'm running on a CURRENT build on my Raspberry Pi. -- George Mitchell ___ 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 It turns out the circular dependency is the side effect of the FreeBSD 10 autotools fix. Upon discovering that acinclude.m4 has been modified, the port decides it needs to run autom4te. I worked around the problem with make -DWITHOUT_FBSD10_FIX, with no apparent ill effects. Perhaps the devel/libtool Makefile should always define WITHOUT_FBSD10_FIX. -- George Mitchell ___ 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
Circular port dependency
I grabbed the ports tree as of 308518, the RELEASE_9_1_0 tag. devel/libtool won't build, because it requires autom4te during the configure phase. So I put BUILD_DEPENDS= autom4te:devel/autoconf in the Makefile. But autoconf depends on gmake, which depends on gettext, which depends on libiconv, which depends on libtool. What to do? I'm running on a CURRENT build on my Raspberry Pi. -- George Mitchell ___ 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
Failed to initialize dwarf?
I checked out head Sunday and now my attempt at building a kernel says: ERROR: ctfconvert: failed to initialize DWARF: Unimplemented code at [dwarf_init_attr(400)] on every module it compiles (though it seems happy enough to keep compiling). Should I just ignore this?-- George Mitchell ___ 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: Failed to initialize dwarf?
On 12/18/12 07:15, Dimitry Andric wrote: On 2012-12-18 12:30, George Mitchell wrote: I checked out head Sunday and now my attempt at building a kernel says: ERROR: ctfconvert: failed to initialize DWARF: Unimplemented code at [dwarf_init_attr(400)] on every module it compiles (though it seems happy enough to keep compiling). Should I just ignore this?-- George Mitchell This problem was fixed in libdwarf in r239872; did you run make buildworld before make buildkernel? Yes. svnversion . says I have 244356. I'll try again. -- George ___ 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 ___ 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 umass problem
On 09/18/12 13:47, Hans Petter Selasky wrote: On Sunday 15 January 2012 20:36:09 Hans Petter Selasky wrote: On Sunday 15 January 2012 18:35:59 George Mitchell wrote: I have a USB compact flash reader-writer which is normally connected to my computer all the time but rarely contains a compact flash card. Here is a snippet from a verbose dmesg with FreeBSD 9.0-RC3: [...] Hi, Can you try 9-stable or apply this patch: http://svn.freebsd.org/changeset/base/240662 --HPS Probably not before Saturday, but thanks for the patch! -- George ___ 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
