Re: Unable to 'make config' ports under FreeBSD current
>> Are you sure the portsnap process finished successfully? It appears to >> be trying to use the FreeBSD 9.x/10.x syntax for adding the dependencies >> of dialog4ports, rather than the 11.x method. >> > > Nope the opposite :) > > dialog4ports uses bsd.prog.mk, somehow his make ends up using the one from > the > source tree rather than the one from /usr/share/mk. The one from the > sourcetree > is having src.libnames.mk which is not supposed to be used > > Larry do you have any variable ENV or /etc/make.conf that defines MAKESYSPATH > to > /usr/src/share/mk? Thanks. That was it. I need to do some digging. For some reason I added following to my .shrc file. MAKESYSPATH=.../usr/src/share/mk Removing it fixes the issue. I can't remember what this fixed for me. Back to the drawing board to do some experimenting to see. Larry ___ 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"
Unable to 'make config' ports under FreeBSD current
I recently installed FreebSD current using a snapshot ISO. I then used svnlite to bring FreeBSD source up to date. I then used portsnap fetch extract to bring my ports tree up todate. I was surprised I got errors doing 'make config' for a port. I assumed it was a transitory problem. I have brought my system and ports up to date several times over the last few weeks, but the issue remains. The fix to the Makefile for the port to fix the issue is pretty simple. I figured I would soon see other people complainging about the issue. Since nobody has, I wonder if it is something in my environment. Is anybody else having this issue? uname -a shows I am running FreeBSD snake32.gta.com 11.0-ALPHA6 FreeBSD 11.0-ALPHA6 #0 r302305: Fri Jul 1 03:45:06 EDT 2016 r...@snake32.gta.com:/usr/obj/usr/src/sys/GENERIC-NODEBUG i386 make config ===> Building/installing dialog4ports as it is required for the config dialog ===> Cleaning for dialog4ports-0.1.5_2 ===> License BSD2CLAUSE accepted by the user ===> dialog4ports-0.1.5_2 depends on file: /usr/local/sbin/pkg - found ===> Fetching all distfiles required by dialog4ports-0.1.5_2 for building ===> Extracting for dialog4ports-0.1.5_2 => SHA256 Checksum OK for dialog4ports-0.1.5.tar.gz. ===> Patching for dialog4ports-0.1.5_2 ===> Configuring for dialog4ports-0.1.5_2 ===> Building for dialog4ports-0.1.5_2 make[3]: "/usr/src/share/mk/src.libnames.mk" line 390: /usr/ports/ports-mgmt/dialog4ports/work/dialog4ports-0.1.5: These libraries should be LIBADD+=foo rather than DPADD/LDADD+=-lfoo: ncursesw m dialog ===> Compilation failed unexpectedly. Try to set MAKE_JOBS_UNSAFE=yes and rebuild before reporting the failure to the maintainer. *** Error code 1 Stop. make[2]: stopped in /usr/ports/ports-mgmt/dialog4ports *** Error code 1 Stop. make[1]: stopped in /usr/ports/ports-mgmt/dialog4ports ===> Options unchanged -- -------- Larry Baird Global Technology Associates, Inc. 1992-2012| http://www.gta.com Celebrating Twenty Years of Software Innovation | Orlando, FL Email: l...@gta.com | TEL 407-380-0220 ___ 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"
Strange coredumps with virtualized i386 FreeBSD 10
Does anybody else have issues with running i386 FreeBSD 10 under Virtual Box? I have been running a number of different versions of FreeBSD under Virtual Box for some time without any issues. Last week I installed amd64 FreeBSD 10 rc1 without any issue. Yesterday I decided to try i386 FreeBSD 10 rc1. Install seemed to go ok. After initial boot I tried to update ports using portsnap. I got a message about corrupted zip file. I initially thought something was wrong with portsnap. Nothing I tried seemed to fix the issue, so I moved on. I tried to build subversion. I got coredumps from cc and was unable to build any ports. I decided something must have gone wrong with the install. I reinstalled and got the same results. I then downloaded and installed i386 FreeBSD 10 rc2. I had the same issues. So I then installed FreeBSD 10 rc1 amd64. No issues, everything seemed to behave as expected. I then installed FreeBSD 9.2 i386. No issues. I then used subversion and mergemaster to upgrade to FreeBSD 10 stable. After doing upgrade, I once again get coredumps from cc. In case it matters Virtual box is version 4.3.4 running under Windows 7 64 bit. Anybody else having issues with i386 FreeBSD 10? -- Larry Baird Global Technology Associates, Inc. 1992-2012| http://www.gta.com Celebrating Twenty Years of Software Innovation | Orlando, FL Email: l...@gta.com | TEL 407-380-0220 ___ 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: Strange coredumps with virtualized i386 FreeBSD 10
Gleb, On Thu, Dec 19, 2013 at 09:51:16AM -0500, Larry Baird wrote: L Does anybody else have issues with running i386 FreeBSD 10 under Virtual Box? L I have been running a number of different versions of FreeBSD under Virtual L Box for some time without any issues. Last week I installed amd64 FreeBSD L 10 rc1 without any issue. Yesterday I decided to try i386 FreeBSD 10 rc1. L Install seemed to go ok. After initial boot I tried to update ports using L portsnap. I got a message about corrupted zip file. I initially thought L something was wrong with portsnap. Nothing I tried seemed to fix the issue, L so I moved on. I tried to build subversion. I got coredumps from cc and was L unable to build any ports. I decided something must have gone wrong with the L install. I reinstalled and got the same results. I then downloaded and L installed i386 FreeBSD 10 rc2. I had the same issues. So I then installed L FreeBSD 10 rc1 amd64. No issues, everything seemed to behave as expected. L I then installed FreeBSD 9.2 i386. No issues. I then used subversion and L mergemaster to upgrade to FreeBSD 10 stable. After doing upgrade, I once L again get coredumps from cc. L L In case it matters Virtual box is version 4.3.4 running under Windows 7 64 bit. L L Anybody else having issues with i386 FreeBSD 10? Can you please set vfs.unmapped_buf_allowed=0 in boot loader and try to reproduce the problem? This seemed to fix the issue. I can now use portsnap and I have successfully compiled serveral ports. Is unmapped_buf_allowed a virtualization issue or an i386 issue? Thank you for your help, Larry -- Larry Baird Global Technology Associates, Inc. 1992-2012| http://www.gta.com Celebrating Twenty Years of Software Innovation | Orlando, FL Email: l...@gta.com | TEL 407-380-0220 ___ 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: Panics after AHCI timeouts
In article 111926.10138.25387@localhost you wrote: On Wed, Oct 26, 2011 at 2:27 AM, Alexander Kabaev kab...@gmail.com wrote: I do see timeouts on one of my Samsung ST3750330A disks and they definitely do not cause any panics. The weird part in my case is that disk then immediately reappears as online and mirror zpool can be rebuilt by just onlining the disk with 'zpool online pool disk' command. It seems to be happening once system has accumulated some uptime. If rebooted, it keeps running for a week or two with no issues, but then timeouts start to happen more or less reliably every single 24 hours. Does it correlate with high disk activity, i.e. with periodic(8)? On my machine, I have a feeling that timeouts occur more often at that point, than normally... and that they also occur when multiple processes access the disk simultaneously. I have seen a panic once last week under 9 stable. I had multiple virtual boxes running different FreeBSD versions. Each virtual host was building kernels with -j4. The host became very slow and the FreeBSD 9 virtual host paniced. I have not been able to to duplicate the panic. Larry -- Larry Baird| http://www.gta.com Global Technology Associates, Inc. | Orlando, FL Email: l...@gta.com | TEL 407-380-0220, FAX 407-380-6080 ___ 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: USB da(4) quirks deprecated
In article [EMAIL PROTECTED] you wrote: On Fri, 2003-08-08 at 03:13, Nate Lawson wrote: On Fri, 8 Aug 2003, Andrew Thompson wrote: Hi Nate, I have just purchased a usb pendrive/mp3 player and I am having a bit of trouble. I built a fresh kernel today as I saw you have been working with the da quirks. When I insert the drive I get: umass0: SigmaTel, Inc. USBMSC Audio Player, rev 1.10/0.01, addr 3 umass0: Get Max Lun not supported (IOERROR) da0 at umass-sim0 bus 0 target 0 lun 0 da0: SigmaTel MSCN 0001 Removable Direct Access SCSI-4 device da0: 1.000MB/s transfers da0: 125MB (256001 512 byte sectors: 64H 32S/T 125C) umass0: BBB reset failed, IOERROR umass0: BBB bulk-in clear stall failed, IOERROR umass0: BBB bulk-out clear stall failed, IOERROR umass0: BBB reset failed, IOERROR umass0: BBB bulk-in clear stall failed, IOERROR umass0: BBB bulk-out clear stall failed, IOERROR and so on I recently had a USB compact flash adapter that was giving me very similar errors. The problem turned out to be my USB hub. Have you tried connecting with out a hub? Larry -- Larry Baird| http://www.gta.com Global Technology Associates, Inc. | Orlando, FL Email: [EMAIL PROTECTED] | TEL 407-380-0220, FAX 407-380-6080 ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Death sentence to KLD screen savers? Comments?
In standard FreeBSD the moving of screen savers to userland may not be a big deal. In Embedded applications it is nice to be able to create very lightweight (read size) screen savers. Hopefully this new mechanism will still allow this. (-; Larry -- Larry Baird| http://www.gnatbox.com Global Technology Associates, Inc. | Orlando, FL Email: [EMAIL PROTECTED] | TEL 407-380-0220, FAX 407-380-6080 To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
FBSD4.0-20000307 install floppies and VAIO PCG-Z505HS
Ran into an odd problem tring to install the 3/7 release of 4.0 onto my VAIO PCG-Z505HS. The install hung while probing for plug and play devices. I had the BIOS set to non plug and play OS. So just for grins I turned plug and play OS on in the bios and tried again. Installed without a hitch. Of course I had to then go back into the BIOS and turn off plug and play OS to get by USB devices working after the install. (-: Any thoughts? Larry -- Larry Baird| HTTP://www.gnatbox.com Global Technology Associates, Inc. | Orlando, FL Email: [EMAIL PROTECTED] | TEL 407-380-0220, FAX 407-380-6080 To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
