Re: bin/178819: bmake w/ WRKDIRPEFIX=/tmp breaks Ports Collection

2013-09-05 Thread Simon J. Gerraty
On Thu, 5 Sep 2013 21:39:42 +0200, Tijl Coosemans writes: >fmake does set it. It goes something like this: > >1) the port makefiles are all named Makefile so fmake sets > MAKEFILE=Makefile. With bmake this is sometimes an absolute path. IIRC it will be an absolute path anytime .OBJDIR!=.CURDIR

Re: bin/178819: bmake w/ WRKDIRPEFIX=/tmp breaks Ports Collection

2013-09-05 Thread Simon J. Gerraty
On Thu, 5 Sep 2013 17:59:36 +, Alexey Dokuchaev writes: >Yes, I've seen the fresh import; will test it tomorrow. I'm not sure what >is the problem, but "ports should be able to control the value of MAKEFILE >as desired" looks strange. MAKEFILE is one of the standard bsd.port.mk's bmake trea

Re: bin/178819: bmake w/ WRKDIRPEFIX=/tmp breaks Ports Collection

2013-09-05 Thread Simon J. Gerraty
With the new version of bmake (20130904), ports should be able to control the value of MAKEFILE as desired. ___ freebsd-bugs@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-un

Re: conf/181116: CURRENT build always uses bmake, even though WITHOUT_BMAKE is specified

2013-08-07 Thread Simon J. Gerraty
The following reply was made to PR conf/181116; it has been noted by GNATS. From: "Simon J. Gerraty" To: Garrett Cooper Cc: "freebsd-gnats-sub...@freebsd.org" , "freebsd-bugs@FreeBSD.org" Subject: Re: conf/181116: CURRENT build always uses bmake, even thou

Re: conf/181116: CURRENT build always uses bmake, even though WITHOUT_BMAKE is specified

2013-08-07 Thread Simon J. Gerraty
On Wed, 7 Aug 2013 11:24:15 -0700, Garrett Cooper writes: >Ah, but src.conf controls WITH* (and the option is documented in the manage,= > along with all the others). You accidentally broke POLA :(. The real issue is that the option handling needs an overhaul. The processing of options should be

Re: conf/181116: CURRENT build always uses bmake, even though WITHOUT_BMAKE is specified

2013-08-07 Thread Simon J. Gerraty
The following reply was made to PR conf/181116; it has been noted by GNATS. From: "Simon J. Gerraty" To: Garrett Cooper Cc: "freebsd-gnats-sub...@freebsd.org" , "freebsd-bugs@FreeBSD.org" Subject: Re: conf/181116: CURRENT build always uses bmake, even thou

Re: conf/181116: CURRENT build always uses bmake, even though WITHOUT_BMAKE is specified

2013-08-07 Thread Simon J. Gerraty
Also the synopsis is somewhat missleading. It only doesn't work when WITHOUT_BMAKE is specified in src.conf which src/Makefile does not honor - so would apply to any WITH[OUT]_ knob. But the larger question is why you are wanting to use fmake Thanks --sjg _

Re: conf/181116: CURRENT build always uses bmake, even though WITHOUT_BMAKE is specified

2013-08-07 Thread Simon J. Gerraty
The following reply was made to PR conf/181116; it has been noted by GNATS. From: "Simon J. Gerraty" To: Garrett Cooper Cc: "freebsd-gnats-sub...@freebsd.org" , "freebsd-bugs@FreeBSD.org" Subject: Re: conf/181116: CURRENT build always uses bmake, even thou

Re: conf/181116: CURRENT build always uses bmake, even though WITHOUT_BMAKE is specified

2013-08-07 Thread Simon J. Gerraty
src/Makefile does not read bsd.own.mk so does not see src.conf it does however see make.conf More importantly, is this a "test" or is there a percieved need to continue building with fmake? If so why? I was aiming to get rid of WITH[OUT]_BMAKE soon - in time for 10.0 _

Re: kern/120270: [crypto] [patch] AES-192 and AES-256 support for HW-accellerators ie. Hifn 795x / and OpenSSL engine 0.9.8e to _default_ use Cryptodev

2013-06-03 Thread simon
Synopsis: [crypto] [patch] AES-192 and AES-256 support for HW-accellerators ie. Hifn 795x / and OpenSSL engine 0.9.8e to _default_ use Cryptodev Responsible-Changed-From-To: simon->freebsd-bugs Responsible-Changed-By: simon Responsible-Changed-When: Mon Jun 3 13:51:31 UTC 2013 Responsi

Re: ports/72202: ports-mgmt/portaudit warns about the CVS server vulnerability which has already been fixed.

2013-06-03 Thread simon
Synopsis: ports-mgmt/portaudit warns about the CVS server vulnerability which has already been fixed. Responsible-Changed-From-To: simon->freebsd-bugs Responsible-Changed-By: simon Responsible-Changed-When: Mon Jun 3 13:52:16 UTC 2013 Responsible-Changed-Why: Send PRs which I'm unlikely

Re: kern/142198: SSLv3 failure with irc/xchat on FreeBSD 8.0

2013-06-03 Thread simon
Synopsis: SSLv3 failure with irc/xchat on FreeBSD 8.0 Responsible-Changed-From-To: simon->freebsd-bugs Responsible-Changed-By: simon Responsible-Changed-When: Mon Jun 3 13:50:12 UTC 2013 Responsible-Changed-Why: Send PRs which I'm unlikely to look at back to the pool. http://www.freebsd

Re: conf/177845: WITH_BMAKE does not work on CURRENT

2013-04-15 Thread Simon J. Gerraty
On Mon, 15 Apr 2013 00:43:46 -0400, Glen Barber writes: >Currently, FreeBSD's make(1). But my src.conf has not changed (as far >as build options) in several months. Thanks - fwiw a buildworld with FreeBSD's make(1) and all the options you mentioned (plus WITH_BMAKE of course) finished successful

Re: conf/177845: WITH_BMAKE does not work on CURRENT

2013-04-14 Thread Simon J. Gerraty
On Mon, 15 Apr 2013 00:30:39 -0400, Glen Barber writes: >Possible. For what it is worth, the only WITH_* entries in my src.conf >are: > > WITH_BIND_UTILS=3Dyes > WITH_BSD_GREP=3D yes > WITH_BSD_PATCH=3D yes > WITH_IDEA=3D yes > WITH_MAIL=3D yes >

Re: conf/177845: WITH_BMAKE does not work on CURRENT

2013-04-14 Thread Simon J. Gerraty
>This looks exactly like the same problem I reported to you in private Yes it does. As noted; the error is the result of bmake passing its -J flag onto an invokation of the old make. The prevelance of makefiles which have bare invocations of 'make' mean that's a reasonable possibility when /usr/b

Re: conf/177845: WITH_BMAKE does not work on CURRENT

2013-04-14 Thread Simon J. Gerraty
FWIW the buildworld I just did (with freebsd make as /usr/bin/make) finished ok (tree updated to r249461), and lots of previous builds used bmake as /usr/bin/make. I'll rebuild this same tree that way... Yep, that complete ok too. > I'm rebuilding world right now so it might be due to a

Re: conf/177845: WITH_BMAKE does not work on CURRENT

2013-04-13 Thread Simon J. Gerraty
On Sat, 13 Apr 2013 22:54:41 -0700, Garrett Cooper writes: >The tree is synched up to the latest head version. I'm suspecting it = >might be something to do with the changes made over the past 2 weeks in = >terms of /Makefile, but I could be wrong. I'll look into this further = >when I can.. I've

Re: Fwd: conf/177845: WITH_BMAKE does not work on CURRENT

2013-04-13 Thread Simon J. Gerraty
On Sat, 13 Apr 2013 21:26:17 -0700, Garrett Cooper writes: > The summary could be a bit better. Basically "buildworld with = >bmake installed as make does not work with WITH_BMAKE specified on = >CURRENT on next compile". >HTH, Hmm, I've been building current with buildworld and bmake as ma

misc/175298: net/tightvnc fails with clang

2013-01-14 Thread Simon
Required: >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Mon Jan 14 18:50:00 UTC 2013 >Closed-Date: >Last-Modified: >Originator: Simon >Release:9.1-RELEASE >Organization: >Environment: FreeBSD x 9.1-RELEASE FreeBSD 9

Re: misc/172440: [patch] [build] fix broken CTFCONVERT_CMD call

2012-10-24 Thread Simon J. Gerraty
On Wed, 24 Oct 2012 11:54:30 +0400, Andrey Chernov writes: >so only bmake case left unfixed. It's fixed in bmake-20121010 which I need to import. ___ freebsd-bugs@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubsc

Re: kern/103022: [headers] /usr/include/crypto/rijndael.h is wrong

2012-10-17 Thread simon
Synopsis: [headers] /usr/include/crypto/rijndael.h is wrong Responsible-Changed-From-To: secteam->freebsd-bugs Responsible-Changed-By: simon Responsible-Changed-When: Thu Oct 18 03:24:25 UTC 2012 Responsible-Changed-Why: This is not a security issue, should be handled like a normal bug. h

Re: misc/172440: [patch] [build] fix broken CTFCONVERT_CMD call

2012-10-07 Thread Simon J. Gerraty
e shouldn't be >changing things arbitrarily without talking with Simon first. Yes, thanks. Patch below should be sufficient. Oddly, I've done a number of recent buildworlds with bmake and WITH_CTF and the only issue I saw was: make: "/b/sjg/work/fbsd-head/src/share/mk/bsd.own.mk

Re: bin/160295: [patch] ypserv:

2012-08-20 Thread Dylan Alex Simon
The following reply was made to PR bin/160295; it has been noted by GNATS. From: Dylan Alex Simon To: bug-follo...@freebsd.org Cc: Subject: Re: bin/160295: [patch] ypserv: Date: Mon, 20 Aug 2012 22:10:38 -0400 Someone has done a rewrite to this exact section of code without fixing this bug

Re: bin/160295: ypserv -P [bin/109494] breaks tcp

2011-08-30 Thread Dylan Alex Simon
The following reply was made to PR bin/160295; it has been noted by GNATS. From: Dylan Alex Simon To: bug-follo...@freebsd.org Cc: Subject: Re: bin/160295: ypserv -P [bin/109494] breaks tcp Date: Tue, 30 Aug 2011 12:15:19 -0400 --6TrnltStXW4iwmi0 Content-Type: text/plain; charset=us-ascii

bin/160295: ypserv -P [bin/109494] breaks tcp

2011-08-29 Thread Dylan Simon
Required: >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Mon Aug 29 19:30:15 UTC 2011 >Closed-Date: >Last-Modified: >Originator: Dylan Simon >Release:7.4 >Organization: NYU >Environment: FreeBSD lust.cns.nyu.edu 7.4-RELEASE-p2 Free

misc/157980: FreeBSD-update doesn't recognize already installed 7.4-p2-update after installing Bind from ports

2011-06-18 Thread Simon van der Meer
gt;State: open >Quarter: >Keywords: >Date-Required: >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Sat Jun 18 08:30:13 UTC 2011 >Closed-Date: >Last-Modified: >Originator: Simon van der Meer >Release:7.4-p2 >Or

kern/155040: [patch] Linux recvfrom doesn't handle proto family

2011-02-25 Thread Simon Walton
ords: >Date-Required: >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Fri Feb 25 19:50:07 UTC 2011 >Closed-Date: >Last-Modified: >Originator: Simon Walton >Release:8.1 >Organization: Matte World Digital >Environment: FreeBSD

Re: kern/150367: [isp] Possible QLogic fiber channel regression in 8.1-RELEASE (and above) [regression]

2011-01-19 Thread Simon Walton
The following reply was made to PR kern/150367; it has been noted by GNATS. From: Simon Walton To: bug-follo...@freebsd.org Cc: Subject: Re: kern/150367: [isp] Possible QLogic fiber channel regression in 8.1-RELEASE (and above) [regression] Date: Wed, 19 Jan 2011 10:04:20 -0800 I have

Re: bin/151321: mount_nfs won't recognize readahead

2010-10-26 Thread Simon Walton
The following reply was made to PR bin/151321; it has been noted by GNATS. From: Simon Walton To: freebsd-gnats-sub...@freebsd.org, freebsd-bugs@FreeBSD.org Cc: Subject: Re: bin/151321: mount_nfs won't recognize readahead Date: Tue, 26 Oct 2010 09:50:51 -0700 Thanks. The patch works

Re: bin/151321: mount_nfs won't recognize readahead

2010-10-26 Thread Simon Walton
Thanks. The patch works fine - both the -a and -o readahead forms of the option mount the filesys. For completeness I guess the mount_nfs warning should say "use -o readahead=" instead of "use -o readhead=". Simon ___ freebsd-bugs

bin/151321: mount_nfs won't recognize readahead

2010-10-08 Thread Simon Walton
Date-Required: >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Fri Oct 08 19:10:04 UTC 2010 >Closed-Date: >Last-Modified: >Originator: Simon Walton >Release:8.1 >Organization: >Environment: FreeBSD mongo 8.1-RELEASE FreeBSD 8.1-RELEA

Re: kern/130726: [ata] DMA errors accessing multiple SATA channels

2010-03-14 Thread Dylan Alex Simon
The following reply was made to PR kern/130726; it has been noted by GNATS. From: Dylan Alex Simon To: Alexander Motin Cc: bug-follo...@freebsd.org Subject: Re: kern/130726: [ata] DMA errors accessing multiple SATA channels Date: Sun, 14 Mar 2010 15:30:36 -0400 A newer RELENG_8 build, or HEAD