John E. Hein | 1 Jul 01:36 2004
Picon

bin/68534: make(1) - ${.MAKEFLAGS} does not contain cmd line args


>Number:         68534
>Category:       bin
>Synopsis:       make(1) - ${.MAKEFLAGS} does not contain cmd line args
>Confidential:   no
>Severity:       non-critical
>Priority:       medium
>Responsible:    freebsd-bugs
>State:          open
>Quarter:        
>Keywords:       
>Date-Required:
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Wed Jun 30 23:40:16 GMT 2004
>Closed-Date:
>Last-Modified:
>Originator:     John E. Hein
>Release:        FreeBSD 4.10-RELEASE i386
>Organization:
Timing Solutions
>Environment:
System: FreeBSD gromit.timing.com 4.10-RELEASE FreeBSD 4.10-RELEASE #1: Wed Jun 23 10:12:32 MDT 2004
jhein <at> gromit.timing.com:/usr/pub/jhein/obj/usr/pub/jhein/src/sys/GROMIT i386

	at least 4.3, 4.10 and 5.2-CURRENT (as of May 2004)

>Description:
	MAKEFLAGS env variable & .MAKEFLAGS make variable does not contain
    command line args as specified in make(1).
(Continue reading)

Giorgos Keramidas | 1 Jul 02:40 2004
Picon

Re: bin/68534: make(1) - ${.MAKEFLAGS} does not contain cmd line args

The following reply was made to PR bin/68534; it has been noted by GNATS.

From: Giorgos Keramidas <keramida <at> ceid.upatras.gr>
To: "John E. Hein" <jhein <at> timing.com>
Cc: bug-followup <at> freebsd.org
Subject: Re: bin/68534: make(1) - ${.MAKEFLAGS} does not contain cmd line args
Date: Thu, 1 Jul 2004 03:37:25 +0300

 On 2004-06-30 17:36, "John E. Hein" <jhein <at> timing.com> wrote:
 > MAKEFLAGS env variable & .MAKEFLAGS make variable does not contain command
 > line args as specified in make(1).

 This is not a bug.

 The keyword is "may".  If you set .MAKEFLAGS in your Makefile or MAKEFLAGS in
 the environment than make(1) *will* *pass* these to child processes (as the
 value of MAKEFLAGS in the environment).

 Not setting MAKEFLAGS is not an error, but does not imply that something
 related to make's invocation will get passed in the environment.

 Here's an an example:

 : giorgos <at> gothmog:/tmp/maketest$ cat Makefile
 : SUBDIR= alpha
 :
 : .MAKEFLAGS=     WITHOUT_X11=YES
 :
 : all:
 :          <at> echo "MFLAGS     : ${MFLAGS}"
(Continue reading)

David Bear | 1 Jul 02:56 2004
Picon

kern/68536: segfault during make buildworld after cvsup


>Number:         68536
>Category:       kern
>Synopsis:       segfault during make buildworld after cvsup
>Confidential:   no
>Severity:       critical
>Priority:       medium
>Responsible:    freebsd-bugs
>State:          open
>Quarter:        
>Keywords:       
>Date-Required:
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Thu Jul 01 01:00:43 GMT 2004
>Closed-Date:
>Last-Modified:
>Originator:     David Bear
>Release:        4.10
>Organization:
ASU
>Environment:
dbsrv1# uname -a
FreeBSD dbsrv1.pp.asu.edu 4.10-RELEASE FreeBSD 4.10-RELEASE #0: Tue Jun 29 16:47:57 MST 2004    
root <at> dbsrv1.pp.asu.edu:/usr/src/sys/compile/DBSRV1  i386

>Description:
    I had successfully configure and built and installed my own kernel. There was nothing fancy it. I just
removed references to hardware that I know I will never have -- mostly certain scsi/raid cards and nics.
After using the new kernel, I did a cvsupdate to update to RELENG-4 to assure all kernel level security
(Continue reading)

John E Hein | 1 Jul 03:10 2004
Picon

Re: bin/68534: make(1) - ${.MAKEFLAGS} does not contain cmd line args

The following reply was made to PR bin/68534; it has been noted by GNATS.

From: John E Hein <jhein <at> timing.com>
To: Giorgos Keramidas <keramida <at> ceid.upatras.gr>
Cc: bug-followup <at> freebsd.org
Subject: Re: bin/68534: make(1) - ${.MAKEFLAGS} does not contain cmd line args
Date: Wed, 30 Jun 2004 19:06:22 -0600

 Giorgos Keramidas wrote at 03:37 +0300 on Jul  1, 2004:
  > The keyword is "may".  If you set .MAKEFLAGS in your Makefile or MAKEFLAGS in
  > the environment than make(1) *will* *pass* these to child processes (as the
  > value of MAKEFLAGS in the environment).

 I am aware of that feature, but that has nothing to do with passing
 along elements of the command line as the man page mentions.

 First, let me quote the section.

      .MAKEFLAGS
                 The environment variable MAKEFLAGS may contain anything that
                 may be specified on make's command line.  Its contents are
                 stored in make's .MAKEFLAGS variable.  Anything specified on
                 make's command line is appended to the .MAKEFLAGS variable
                 which is then entered into the environment as MAKEFLAGS for
                 all programs which make executes.

 I see the 'may'.  But the 3rd sentence seems more definitive.  At the
 least it's misleading.  But I still don't see any way to get anything
 specified on the command line into MAKEFLAGS (or .MAKEFLAGS).

(Continue reading)

John E Hein | 1 Jul 03:30 2004
Picon

Re: bin/68534: make(1) - ${.MAKEFLAGS} does not contain cmd line args

The following reply was made to PR bin/68534; it has been noted by GNATS.

From: John E Hein <jhein <at> timing.com>
To: Giorgos Keramidas <keramida <at> ceid.upatras.gr>
Cc: bug-followup <at> freebsd.org
Subject: Re: bin/68534: make(1) - ${.MAKEFLAGS} does not contain cmd line args
Date: Wed, 30 Jun 2004 19:22:20 -0600

 This is interesting env var precedence weirdness...

 $ cat Makefile
 FOO?=0
 X?=0
 .PHONY: x
 x:
 	 <at> echo MAKEFLAGS: ${MAKEFLAGS}
 	 <at> echo .MAKEFLAGS: ${.MAKEFLAGS}
 	 <at> echo FOO: ${FOO}
 .if $X != 1
 	make X=1
 .endif

 $ env FOO=1 MAKEFLAGS=FOO=3 make FOO=2
 MAKEFLAGS: FOO=3
 .MAKEFLAGS:
 FOO: 2
 make X=1
 MAKEFLAGS: FOO=3
 .MAKEFLAGS:
 FOO: 3
(Continue reading)

Stephen Hurd | 1 Jul 03:40 2004
Picon

Re: kern/50827: [PATCH] no sane record locking on *nix. (Moretypes needed)

The following reply was made to PR kern/50827; it has been noted by GNATS.

From: Stephen Hurd <shurd <at> sasktel.net>
To: freebsd-gnats-submit <at> FreeBSD.org, shurd <at> sasktel.net
Cc:  
Subject: Re: kern/50827: [PATCH] no sane record locking on *nix.  (More types
 needed)
Date: Wed, 30 Jun 2004 19:37:17 -0600

 Actually, I meant that the following patch works on 5.2.1  :-)

 --- sanelock.patch begins here ---
 diff -c /sys/kern.old/kern_descrip.c /sys/kern/kern_descrip.c
 *** /sys/kern.old/kern_descrip.c        Thu Jun 24 17:25:47 2004
 --- /sys/kern/kern_descrip.c    Thu Jun 24 18:22:09 2004
 ***************
 *** 380,385 ****
 --- 380,411 ----
                         error = VOP_ADVLOCK(vp, (caddr_t)p->p_leader,
 F_UNLCK,                            flp, F_POSIX);
                         break;
 +               case F_SANEWRLCKNO:
 +                       flg |= F_NOOVRLP;
 +               case F_SANEWRLCK:
 +                       flp->l_type=F_WRLCK;
 +                       flg &= ~F_POSIX;
 +                       flg |= F_FLOCK;
 +                       fp->f_flag |= FHASLOCK;
 +                       error = VOP_ADVLOCK(vp, (caddr_t)fp, F_SETLK,
 +                           flp, flg);
(Continue reading)

Vadim Mikhailov | 1 Jul 04:00 2004

Re: kern/68351: bge0 watchdog timeout on 5.2.1 and -current, 5.1 is ok

The following reply was made to PR kern/68351; it has been noted by GNATS.

From: Vadim Mikhailov <freebsd-bugs <at> mikhailov.org>
To: John Baldwin <jhb <at> FreeBSD.org>
Cc: current <at> FreeBSD.org, freebsd-gnats-submit <at> FreeBSD.org,
	freebsd-bugs <at> mikhailov.org
Subject: Re: kern/68351: bge0 watchdog timeout on 5.2.1 and -current, 5.1
 is ok
Date: Wed, 30 Jun 2004 18:57:39 -0700

 On Tuesday, 6/29/2004 8:58 AM, John Baldwin wrote:
 > On Monday 28 June 2004 01:32 pm, Vadim Mikhailov wrote:
 >>  I have a Dell PowerEdge 1750 server with 2 Xeon 3.0 GHZ CPUs,
  >> 4 GB RAM and 2 onboard gigabit ethernet ports:
 >>
 >> bge0: <Broadcom BCM5704C Dual Gigabit Ethernet, ASIC rev.
 >> This setup works more or less ok under FreeBSD 5.1-RELEASE-p8
  >> (GENERIC kernel with SMP enabled), but once a month or two
  >> machine reboots under load, so I want to upgrade it to
  >> 5.2.1-RELEASE.
 >> But when I boot 5.2.1-RELEASE or later kernel (-current) on
  >> this box, network adapter locks up.
 >> I see these messages on console and in the logs:
 >>
 >>Jun 25 15:25:22 vortex kernel: bge0: watchdog timeout -- resetting
 >>
 >>  If I do "ifconfig bge0 down up", network becomes available
  >> for few seconds and then machine is not pingable again.
  >>  I ran "systat -v" and have noticed that ping stops working
  >> exactly when I see any interrupt coming to mpt or ahc
(Continue reading)

Mark Linimon | 1 Jul 05:14 2004
Picon

Re: misc/56206: src/sys/sys/cdefs.h uses PreProcessor variables that aren't defined, causing noisy warnings.

Synopsis: src/sys/sys/cdefs.h uses PreProcessor variables that aren't defined, causing noisy warnings.

State-Changed-From-To: open->closed
State-Changed-By: linimon
State-Changed-When: Thu Jul 1 03:13:38 GMT 2004
State-Changed-Why: 
The discussion that ensued in the responses to this PR seem to indicate
that the current behavior is intentional, so this can not be considered
a bug.

http://www.freebsd.org/cgi/query-pr.cgi?pr=56206
_______________________________________________
freebsd-bugs <at> freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-bugs
To unsubscribe, send any mail to "freebsd-bugs-unsubscribe <at> freebsd.org"

Mark Linimon | 1 Jul 07:24 2004
Picon

Re: junk/68526: software

Synopsis: software

State-Changed-From-To: open->closed
State-Changed-By: linimon
State-Changed-When: Thu Jul 1 05:23:49 GMT 2004
State-Changed-Why: 
spam.

Responsible-Changed-From-To: gnats-admin-≥freebsd-bugs
Responsible-Changed-By: linimon
Responsible-Changed-When: Thu Jul 1 05:23:49 GMT 2004
Responsible-Changed-Why: 

http://www.freebsd.org/cgi/query-pr.cgi?pr=68526
_______________________________________________
freebsd-bugs <at> freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-bugs
To unsubscribe, send any mail to "freebsd-bugs-unsubscribe <at> freebsd.org"

Mark Linimon | 1 Jul 07:25 2004
Picon

Re: junk/68537: Warehouse Storage/Crossdock - Your Total Logistics Solution

Synopsis: Warehouse Storage/Crossdock - Your Total Logistics Solution

State-Changed-From-To: open->closed
State-Changed-By: linimon
State-Changed-When: Thu Jul 1 05:24:50 GMT 2004
State-Changed-Why: 
spam.

Responsible-Changed-From-To: gnats-admin-≥freebsd-bugs
Responsible-Changed-By: linimon
Responsible-Changed-When: Thu Jul 1 05:24:50 GMT 2004
Responsible-Changed-Why: 

http://www.freebsd.org/cgi/query-pr.cgi?pr=68537
_______________________________________________
freebsd-bugs <at> freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-bugs
To unsubscribe, send any mail to "freebsd-bugs-unsubscribe <at> freebsd.org"


Gmane