From owner-freebsd-current@FreeBSD.ORG Sun Jul 13 01:13:07 2003 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id CBE6037B401; Sun, 13 Jul 2003 01:13:07 -0700 (PDT) Received: from cueball.rtp.FreeBSD.org (cueball.rtp.FreeBSD.org [192.58.184.37]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0C26B43FA3; Sun, 13 Jul 2003 01:13:07 -0700 (PDT) (envelope-from des+tinderbox@freebsd.org) Received: from cueball.rtp.FreeBSD.org (localhost [127.0.0.1]) h6D8D6s8072249; Sun, 13 Jul 2003 04:13:06 -0400 (EDT) (envelope-from des+tinderbox@freebsd.org) Received: (from des@localhost) by cueball.rtp.FreeBSD.org (8.12.9/8.12.9/Submit) id h6D8D6xe072248; Sun, 13 Jul 2003 08:13:06 GMT Date: Sun, 13 Jul 2003 08:13:06 GMT Message-Id: <200307130813.h6D8D6xe072248@cueball.rtp.FreeBSD.org> X-Authentication-Warning: cueball.rtp.FreeBSD.org: des set sender to Tinderbox using -f Sender: Tinderbox From: Tinderbox To: current@freebsd.org, i386@freebsd.org Precedence: bulk Subject: [-CURRENT tinderbox] failure on i386/pc98 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 13 Jul 2003 08:13:08 -0000 TB --- 2003-07-13 07:14:14 - starting CURRENT tinderbox run for i386/pc98 TB --- 2003-07-13 07:14:14 - checking out the source tree TB --- cd /home/des/tinderbox/CURRENT/i386/pc98 TB --- /usr/bin/cvs -f -R -q -d/home/ncvs update -Pd -A src TB --- 2003-07-13 07:19:12 - building world TB --- cd /home/des/tinderbox/CURRENT/i386/pc98/src TB --- /usr/bin/make -B buildworld >>> Building an up-to-date make(1) >>> Rebuilding the temporary build tree >>> stage 1: legacy release compatibility shims >>> stage 1: bootstrap tools >>> stage 2: cleaning up the object tree >>> stage 2: rebuilding the object tree >>> stage 2: build tools >>> stage 3: cross tools >>> stage 4: populating /home/des/tinderbox/CURRENT/i386/pc98/obj/pc98/vol/vol0/users/des/tinderbox/CURRENT/i386/pc98/src/i386/usr/include >>> stage 4: building libraries >>> stage 4: make dependencies >>> stage 4: building everything.. [...] objcopy -S -O binary boot0.5.out boot0.5.bin cat boot0.5.bin /dev/zero | dd of=boot0.5 bs=1 count=7168 7168+0 records in 7168+0 records out 7168 bytes transferred in 0.222433 secs (32225 bytes/sec) ===> sys/boot/pc98/boot2 cc -elf -Os -mrtd -ffreestanding -fno-builtin -fno-guess-branch-probability -D_KERNEL -DPC98 -DBOOTWAIT=5000 -DTIMEOUT= -DBOOTSEG=0x1000 -DBOOTSTACK=0xFFF0 -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -std=c99 -I/vol/vol0/users/des/tinderbox/CURRENT/i386/pc98/src/sys/boot/pc98/boot2/../../.. -I. -DCOMCONSOLE=0x238 -DCOMCONSOLE_CLK=16 -DCOMCONSOLE_MODE=0x0c -DCOMSPEED=9600 -mno-align-long-strings -mpreferred-stack-boundary=2 -ffreestanding -ffreestanding -mpreferred-stack-boundary=2 -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -std=c99 -c /vol/vol0/users/des/tinderbox/CURRENT/i386/pc98/src/sys/boot/pc98/boot2/start.S /vol/vol0/users/des/tinderbox/CURRENT/i386/pc98/src/sys/boot/pc98/boot2/start.S:474:16: pasting "disklabel" and ":" does not give a valid preprocessing token *** Error code 1 Stop in /vol/vol0/users/des/tinderbox/CURRENT/i386/pc98/src/sys/boot/pc98/boot2. *** Error code 1 Stop in /vol/vol0/users/des/tinderbox/CURRENT/i386/pc98/src/sys/boot/pc98. *** Error code 1 Stop in /vol/vol0/users/des/tinderbox/CURRENT/i386/pc98/src/sys/boot. *** Error code 1 Stop in /vol/vol0/users/des/tinderbox/CURRENT/i386/pc98/src/sys. *** Error code 1 Stop in /vol/vol0/users/des/tinderbox/CURRENT/i386/pc98/src. *** Error code 1 Stop in /vol/vol0/users/des/tinderbox/CURRENT/i386/pc98/src. *** Error code 1 Stop in /vol/vol0/users/des/tinderbox/CURRENT/i386/pc98/src. TB --- 2003-07-13 08:13:06 - /usr/bin/make returned exit code 1 TB --- 2003-07-13 08:13:06 - ERROR: failed to build world TB --- 2003-07-13 08:13:06 - tinderbox aborted From owner-freebsd-current@FreeBSD.ORG Sun Jul 13 01:43:34 2003 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 937B337B401 for ; Sun, 13 Jul 2003 01:43:34 -0700 (PDT) Received: from smtp.des.no (37.80-203-228.nextgentel.com [80.203.228.37]) by mx1.FreeBSD.org (Postfix) with ESMTP id 02DBA43F75 for ; Sun, 13 Jul 2003 01:43:34 -0700 (PDT) (envelope-from des@des.no) Received: by smtp.des.no (Pony Express, from userid 2602) id E67BE95958; Sun, 13 Jul 2003 10:43:32 +0200 (CEST) Date: Sun, 13 Jul 2003 10:43:32 +0200 From: Dag-Erling Smorgrav To: Dominic Marks Message-ID: <20030713084332.GB86012@des.no> References: <20030706224753.GA12877@cus.org.uk> <20030710082642.GA17776@cus.org.uk> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <20030710082642.GA17776@cus.org.uk> User-Agent: Mutt/1.4.1i cc: freebsd-current@freebsd.org Subject: Re: OpenPAM dynamic module loading not working ? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 13 Jul 2003 08:43:34 -0000 On Thu, Jul 10, 2003 at 09:26:42AM +0100, Dominic Marks wrote: > On 10/07/2003 08:46, Dag-Erling Sm?rgrav wrote: > > Dominic Marks writes: > > > Jul 7 22:10:40 bacon dovecot-auth: in openpam_load_module(): no pam_pgsql.so found > > > Jul 7 22:10:40 bacon dovecot-auth: PAM: pam_start(example) failed: failed to load module > > > > The module probably lacks dependency information. I'll try to figure > > it out later today. > > I rebuilt OpenPAM with debugging info and looked at what was happening. > It turned out that it was not able to resolve pam_get_pass from the > module pam_get_pass() doesn't exist in -CURRENT, it should use pam_get_authtok() instead. DES -- Dag-Erling Smørgrav - des@des.no From owner-freebsd-current@FreeBSD.ORG Sun Jul 13 01:47:50 2003 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1CA3C37B401 for ; Sun, 13 Jul 2003 01:47:50 -0700 (PDT) Received: from hotmail.com (bay8-f104.bay8.hotmail.com [64.4.27.104]) by mx1.FreeBSD.org (Postfix) with ESMTP id A7CF143F3F for ; Sun, 13 Jul 2003 01:47:49 -0700 (PDT) (envelope-from evantd@hotmail.com) Received: from mail pickup service by hotmail.com with Microsoft SMTPSVC; Sun, 13 Jul 2003 01:47:49 -0700 Received: from 12.229.123.246 by by8fd.bay8.hotmail.msn.com with HTTP; Sun, 13 Jul 2003 08:47:49 GMT X-Originating-IP: [12.229.123.246] X-Originating-Email: [evantd@hotmail.com] From: "Evan Dower" To: mchopra@engmail.uwaterloo.ca, current@freebsd.org Date: Sun, 13 Jul 2003 01:47:49 -0700 Mime-Version: 1.0 Content-Type: text/plain; format=flowed Message-ID: X-OriginalArrivalTime: 13 Jul 2003 08:47:49.0604 (UTC) FILETIME=[70731240:01C3491B] Subject: Re: NVidia driver stability? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 13 Jul 2003 08:47:50 -0000 That may have done it. Now that I recompiled nvidia-driver only WITH_NVIDIA_HACKS, doing glxinfo several times no longer wreaks havoc. Since something seems to be screwy with my network driver (rtl8139) when the kernel is compiled without optimizations, I recompiled with them and so far all is well. At the moment, I have my AGP rate knocked down from 4x to 2x in BIOS. If all continues to go well, I'll bump it back up and report what I find. E >From: Munish Chopra > >On 2003-07-12 14:46 +0000, Evan Dower wrote: > > After following all the instructions at > > http://www.soulwax.net/nvidia/faq.shtml _very_ carefully and compiling > > nvidia-driver WITH_FREEBSD_AGP, WITH_NVIDIA_HACKS, and with >FORCE_AGP_RATE, > > my system was dramatically slower and substantially _less_ stable. (I >had > > to switch to another computer to write this email). Interestingly, >whenever > > I compile the kernel without optimizations, network activity becomes >_very_ > > slow. > > E > > aka Evan Dower > > Undergraduate, Computer Science > > University of Washington > > > >Did you try using the NVIDIA AGP interface? > >The majority of mail I get indicates that the NVIDIA AGP stuff works >better than the FreeBSD one. > >I'm not sure about your network problems, perhaps you should look at the >driver for clues. > >-- >Munish Chopra >_______________________________________________ >freebsd-current@freebsd.org mailing list >http://lists.freebsd.org/mailman/listinfo/freebsd-current >To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" _________________________________________________________________ The new MSN 8: advanced junk mail protection and 2 months FREE* http://join.msn.com/?page=features/junkmail From owner-freebsd-current@FreeBSD.ORG Sun Jul 13 01:52:35 2003 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 91E2037B401 for ; Sun, 13 Jul 2003 01:52:35 -0700 (PDT) Received: from opiate.soulwax.net (CPE0030ab0ef2bb-CM000039ae486b.cpe.net.cable.rogers.com [63.138.84.149]) by mx1.FreeBSD.org (Postfix) with ESMTP id D4C2543FB1 for ; Sun, 13 Jul 2003 01:52:34 -0700 (PDT) (envelope-from munish@opiate.soulwax.net) Received: by opiate.soulwax.net (Postfix, from userid 1001) id 121F42B; Sun, 13 Jul 2003 04:52:34 -0400 (EDT) Date: Sun, 13 Jul 2003 04:52:34 -0400 From: Munish Chopra To: Evan Dower Message-ID: <20030713085233.GA83251@opiate.soulwax.net> Mail-Followup-To: Evan Dower , current@freebsd.org References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: cc: current@freebsd.org Subject: Re: NVidia driver stability? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 13 Jul 2003 08:52:35 -0000 On 2003-07-13 01:47 +0000, Evan Dower wrote: > That may have done it. Now that I recompiled nvidia-driver only > WITH_NVIDIA_HACKS, doing glxinfo several times no longer wreaks havoc. > Since something seems to be screwy with my network driver (rtl8139) when > the kernel is compiled without optimizations, I recompiled with them and so > far all is well. At the moment, I have my AGP rate knocked down from 4x to > 2x in BIOS. If all continues to go well, I'll bump it back up and report > what I find. > E > Bill Paul recently checked in some changes to the rtl8139 code, you might want to check the CVS logs for that. Bumping up the AGP rate should be safe in 99% of cases. Good luck. -- Munish Chopra From owner-freebsd-current@FreeBSD.ORG Sun Jul 13 02:11:17 2003 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 67B7837B48D for ; Sun, 13 Jul 2003 02:11:16 -0700 (PDT) Received: from cus.org.uk (host213-106-240-81.no-dns-yet.ntli.net [213.106.240.81]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1643743F3F for ; Sun, 13 Jul 2003 02:11:15 -0700 (PDT) (envelope-from dom@cus.org.uk) Received: from cus.org.uk (localhost.cus.org.uk [127.0.0.1]) by cus.org.uk (8.12.6/8.12.6) with ESMTP id h6D9B95h002070; Sun, 13 Jul 2003 10:11:09 +0100 (BST) (envelope-from dom@cus.org.uk) Received: (from dom@localhost) by cus.org.uk (8.12.6/8.12.6/Submit) id h6D9B9q3002069; Sun, 13 Jul 2003 10:11:09 +0100 (BST) Date: Sun, 13 Jul 2003 10:11:09 +0100 From: Dominic Marks To: Dag-Erling Smorgrav Message-ID: <20030713091109.GA93839@cus.org.uk> References: <20030706224753.GA12877@cus.org.uk> <20030710082642.GA17776@cus.org.uk> <20030713084332.GB86012@des.no> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20030713084332.GB86012@des.no> User-Agent: Mutt/1.4i cc: freebsd-current@freebsd.org Subject: Re: OpenPAM dynamic module loading not working ? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 13 Jul 2003 09:11:17 -0000 On 13/07/2003 10:43, Dag-Erling Smorgrav wrote: > On Thu, Jul 10, 2003 at 09:26:42AM +0100, Dominic Marks wrote: > > On 10/07/2003 08:46, Dag-Erling Sm?rgrav wrote: > > > Dominic Marks writes: > > > > Jul 7 22:10:40 bacon dovecot-auth: in openpam_load_module(): no pam_pgsql.so found > > > > Jul 7 22:10:40 bacon dovecot-auth: PAM: pam_start(example) failed: failed to load module > > > > > > The module probably lacks dependency information. I'll try to figure > > > it out later today. > > > > I rebuilt OpenPAM with debugging info and looked at what was happening. > > It turned out that it was not able to resolve pam_get_pass from the > > module > > pam_get_pass() doesn't exist in -CURRENT, it should use pam_get_authtok() > instead. Ok, can you explain why it was trying to find the pam_get_pass symbol which was removed from the module (by a port patch) and not mentioned in OpenPAM? I assume OpenPAM is looking in the module, catching a stray reference to it and then slipping up from here? > DES > -- > Dag-Erling Sm?rgrav - des@des.no > _______________________________________________ > freebsd-current@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" Thanks, -- Dominic From owner-freebsd-current@FreeBSD.ORG Sun Jul 13 02:28:45 2003 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1BF6137B401 for ; Sun, 13 Jul 2003 02:28:45 -0700 (PDT) Received: from serio.al.rim.or.jp (serio.al.rim.or.jp [202.247.191.123]) by mx1.FreeBSD.org (Postfix) with ESMTP id AE57543FE5 for ; Sun, 13 Jul 2003 02:28:43 -0700 (PDT) (envelope-from matoba@st.rim.or.jp) Received: from mail6.rim.or.jp by serio.al.rim.or.jp (3.7W/HMX-13) id SAA10527; Sun, 13 Jul 2003 18:28:41 +0900 (JST) Received: from localhost (ntkngw062092.kngw.nt.adsl.ppp.infoweb.ne.jp [219.104.198.92]) by mail6.rim.or.jp (8.9.3/3.7W) id SAA01848; Sun, 13 Jul 2003 18:28:41 +0900 (JST) Date: Sun, 13 Jul 2003 18:28:35 +0900 (JST) Message-Id: <20030713.182835.730549724.matoba@st.rim.or.jp> To: acpi-jp@jp.FreeBSD.org From: MATOBA Hirozumi In-Reply-To: <20030711230155.Q9479@root.org> References: <20030711230155.Q9479@root.org> Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit cc: current@freebsd.org Subject: Re: [acpi-jp 2412] PATCH - acpi 0619 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 13 Jul 2003 09:28:45 -0000 On Fri, 11 Jul 2003 23:07:08 -0700, Nate Lawson wrote: | I've prepared a new diff of the 0619 drop of acpica along with the | appropriate changes to support code: | | * Use ACPI_BUFFER as the type for AcpiGetObjectInfo | * Remove AcpiEnableEvent/AcpiClearEvent for ACPI_EVENT_FIXED (power/sleep | buttons) as they are no longer needed | * Change calls to use the new GPE functions | * Add AcpiOs*Lock functions | * Import 0619 + local FreeBSD changes + dsmthdat.c patch (from | kochi@netbsd.org) | | Please test and let me know how this works for you. It works fine on my | IBM T23. | | http://www.root.org/~nate/freebsd/acpi-0619.diff.gz I tested this patch on IBM ThinkPad A22e, but repeated messages ACPI-0340: *** Error: Could not release ACPI Global Lock, AE_BAD_PARAMETER appeared again (like as 2-3 weeks ago). It seems that the change of from version 1.1.1.16 to 1.1.1.17 in src/sys/contrib/dev/acpica/hwregs.c is overwritten by this patch (so partially back to the status of 1.1.1.16). -- matoba@st.rim.or.jp From owner-freebsd-current@FreeBSD.ORG Sun Jul 13 03:06:30 2003 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C0FEA37B409 for ; Sun, 13 Jul 2003 03:06:30 -0700 (PDT) Received: from carebears.mine.nu (ti400720a080-1314.bb.online.no [80.212.165.34]) by mx1.FreeBSD.org (Postfix) with ESMTP id CCA6D43F75 for ; Sun, 13 Jul 2003 03:06:26 -0700 (PDT) (envelope-from chgu@carebears.mine.nu) Received: from carebears.mine.nu (localhost.carebears.net [127.0.0.1]) by carebears.mine.nu (Postfix) with SMTP id B4F98A1098 for ; Sun, 13 Jul 2003 12:05:20 +0200 (CEST) Received: from 80.212.165.34 (SquirrelMail authenticated user chgu) by carebears.mine.nu with HTTP; Sun, 13 Jul 2003 12:05:20 +0200 (CEST) Message-ID: <65243.80.212.165.34.1058090720.squirrel@carebears.mine.nu> Date: Sun, 13 Jul 2003 12:05:20 +0200 (CEST) From: "Christer Gundersen" To: freebsd-current@freebsd.org User-Agent: SquirrelMail/1.4.0 MIME-Version: 1.0 Content-Type: text/plain;charset=iso-8859-1 X-Priority: 3 Importance: Normal Subject: 5.1 RELEASE bugs? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 13 Jul 2003 10:06:31 -0000 Hi! I was installing 5.1 yesterday, i and think i discoverd some small bugs. COPTFLAGS is not respected when buling modules, just the kernel. when builings modules it seems to like CFLAGS better. With 'CPUTYPE=p4' and '-march=pentium4' in make.conf, when compiling something it seems to use 'cc -march=pentium3 -march=pentium4 ls.c' the word 'pentium3' dont exist in make.conf. (yes, the machine is a Pentium4) -- Med vennlig hilsen / Best regards Christer Gundersen / dizzy tun3Z http://dtz.cjb.net - http://carebears.mine.nu From owner-freebsd-current@FreeBSD.ORG Sun Jul 13 03:13:53 2003 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 08E8C37B401 for ; Sun, 13 Jul 2003 03:13:52 -0700 (PDT) Received: from ns.waishi.jp (ns.waishi.jp [61.199.233.194]) by mx1.FreeBSD.org (Postfix) with ESMTP id A966943F3F for ; Sun, 13 Jul 2003 03:13:51 -0700 (PDT) (envelope-from yosimoto@waishi.jp) Received: from ns.waishi.jp (ns.waishi.jp [61.199.233.194]) by ns.waishi.jp (Postfix) with SMTP id 9B1CC22F20; Sun, 13 Jul 2003 19:13:50 +0900 (JST) Date: Sun, 13 Jul 2003 19:13:50 +0900 From: Shin-ichi YOSHIMOTO To: "Christer Gundersen" Message-Id: <20030713191350.54402dc8.yosimoto@waishi.jp> In-Reply-To: <65243.80.212.165.34.1058090720.squirrel@carebears.mine.nu> References: <65243.80.212.165.34.1058090720.squirrel@carebears.mine.nu> Organization: WAISHI.JP X-Mailer: Sylpheed version 0.9.3 (GTK+ 1.2.10; i386-portbld-freebsd4.8) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit cc: freebsd-current@freebsd.org Subject: Re: 5.1 RELEASE bugs? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 13 Jul 2003 10:13:53 -0000 Subject: 5.1 RELEASE bugs?, On Sun, 13 Jul 2003 12:05:20 +0200 (CEST), Christer Gundersen wrote: > the word 'pentium3' dont exist in make.conf. see /usr/src/share/mk/bsd.cpu.mk -- Shin-ichi YOSHIMOTO http://diary.waishi.jp/~yosimoto/diary/ From owner-freebsd-current@FreeBSD.ORG Sun Jul 13 04:11:03 2003 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id DA2CC37B401 for ; Sun, 13 Jul 2003 04:11:03 -0700 (PDT) Received: from smtp.des.no (37.80-203-228.nextgentel.com [80.203.228.37]) by mx1.FreeBSD.org (Postfix) with ESMTP id 982B543FEC for ; Sun, 13 Jul 2003 04:11:02 -0700 (PDT) (envelope-from des@des.no) Received: by smtp.des.no (Pony Express, from userid 2602) id 4079896459; Sun, 13 Jul 2003 13:11:01 +0200 (CEST) Date: Sun, 13 Jul 2003 13:11:01 +0200 From: Dag-Erling Smorgrav To: Dominic Marks Message-ID: <20030713111100.GA86788@des.no> References: <20030706224753.GA12877@cus.org.uk> <20030710082642.GA17776@cus.org.uk> <20030713084332.GB86012@des.no> <20030713091109.GA93839@cus.org.uk> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <20030713091109.GA93839@cus.org.uk> User-Agent: Mutt/1.4.1i cc: freebsd-current@freebsd.org Subject: Re: OpenPAM dynamic module loading not working ? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 13 Jul 2003 11:11:04 -0000 On Sun, Jul 13, 2003 at 10:11:09AM +0100, Dominic Marks wrote: > Ok, can you explain why it was trying to find the pam_get_pass symbol > which was removed from the module (by a port patch) and not mentioned in > OpenPAM? I assume OpenPAM is looking in the module, catching a stray > reference to it and then slipping up from here? The patch doesn't remove references to pam_get_pass(); it removes the port's own implementation of pam_get_pass() under the assumption that libpam provides one (which it no longer does). I'm afraid it's simply not going to work on -CURRENT without heavy modification... It relies too heavily on old glue code which has been removed. DES -- Dag-Erling Smørgrav - des@des.no From owner-freebsd-current@FreeBSD.ORG Sun Jul 13 05:17:39 2003 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 94D5137B401 for ; Sun, 13 Jul 2003 05:17:39 -0700 (PDT) Received: from tao.xtaz.co.uk (pc-62-30-69-139-az.blueyonder.co.uk [62.30.69.139]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6071043F3F for ; Sun, 13 Jul 2003 05:17:38 -0700 (PDT) (envelope-from matt@xtaz.co.uk) Received: from webmail.xtaz.co.uk (localhost [127.0.0.1]) by tao.xtaz.co.uk (Postfix) with SMTP id 637D88FC5B for ; Sun, 13 Jul 2003 13:17:36 +0100 (BST) Received: from 192.168.1.10 (SquirrelMail authenticated user matt) by webmail.xtaz.co.uk with HTTP; Sun, 13 Jul 2003 13:17:36 +0100 (BST) Message-ID: <49176.192.168.1.10.1058098656.squirrel@webmail.xtaz.co.uk> Date: Sun, 13 Jul 2003 13:17:36 +0100 (BST) From: "Matt" To: current@freebsd.org User-Agent: SquirrelMail/1.4.0 MIME-Version: 1.0 Content-Type: text/plain;charset=iso-8859-1 X-Priority: 3 Importance: Normal Subject: IPFW and/or rc rule parsing not working since today's cvsup X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 13 Jul 2003 12:17:39 -0000 I normally sync to current once a week and have just done it today: FreeBSD tao.xtaz.co.uk 5.1-CURRENT FreeBSD 5.1-CURRENT #0: Sun Jul 13 12:24:40 BST 2003 root@shakira.xtaz.co.uk:/usr/obj/usr/src/sys/TAO i386 The problem is though that it looks like IPFW or RC has changed how it works. I'm not sure if this is intentional or not though. If it is intentional then I think it is a violation of POLA. The problem I have is this. In rc.conf I have the following: firewall_enable="YES" firewall_script="/etc/rc.firewall" firewall_type="/etc/ipfw.conf" And in /etc/ipfw.conf I have sets of rules one line at a time like: add 00010 divert natd all from any to any via xl0 add 00120 allow tcp from any to any 80 via xl0 etc. This has always worked for me ever since I first started using ipfw on fbsd 4.1 and has always worked on current until today's cvsup. Now though no rules get loaded. If I try what I have always done in the past which is ipfw -q flush && ipfw /etc/ipfw.conf then it tells me: usage: ipfw [options] do "ipfw -h" or see ipfw manpage for details Whereas before this week this worked perfectly. The /etc/rc.firewall still says that you can set a filename for the firewall_type so I assume this should still work as in fact just broken rather than a POLA. I definatly mergemaster'd everything that had changed properly. In fact I have even just run it again in case I missed something and everything is up to date. Any comments? Regards, Matt. -- email: matt@xtaz.co.uk - web: http://xtaz.co.uk/ Hardware, n.: The parts of a computer system that can be kicked. From owner-freebsd-current@FreeBSD.ORG Sun Jul 13 05:31:09 2003 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 19CAC37B401; Sun, 13 Jul 2003 05:31:09 -0700 (PDT) Received: from tao.xtaz.co.uk (pc-62-30-69-139-az.blueyonder.co.uk [62.30.69.139]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6198A43F93; Sun, 13 Jul 2003 05:31:08 -0700 (PDT) (envelope-from matt@xtaz.co.uk) Received: from webmail.xtaz.co.uk (localhost [127.0.0.1]) by tao.xtaz.co.uk (Postfix) with SMTP id 62DCE8FCAE; Sun, 13 Jul 2003 13:31:07 +0100 (BST) Received: from 192.168.1.10 (SquirrelMail authenticated user matt) by webmail.xtaz.co.uk with HTTP; Sun, 13 Jul 2003 13:31:07 +0100 (BST) Message-ID: <49205.192.168.1.10.1058099467.squirrel@webmail.xtaz.co.uk> In-Reply-To: <49176.192.168.1.10.1058098656.squirrel@webmail.xtaz.co.uk> References: <49176.192.168.1.10.1058098656.squirrel@webmail.xtaz.co.uk> Date: Sun, 13 Jul 2003 13:31:07 +0100 (BST) From: "Matt" To: luigi@FreeBSD.org User-Agent: SquirrelMail/1.4.0 MIME-Version: 1.0 Content-Type: text/plain;charset=iso-8859-1 X-Priority: 3 Importance: Normal cc: current@freebsd.org Subject: Re: IPFW and/or rc rule parsing not working since today's cvsup X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 13 Jul 2003 12:31:09 -0000 Matt said: > I normally sync to current once a week and have just done it today: > > FreeBSD tao.xtaz.co.uk 5.1-CURRENT FreeBSD 5.1-CURRENT #0: Sun Jul 13 > 12:24:40 BST 2003 root@shakira.xtaz.co.uk:/usr/obj/usr/src/sys/TAO > i386 > > The problem is though that it looks like IPFW or RC has changed how it > works. I'm not sure if this is intentional or not though. If it is > intentional then I think it is a violation of POLA. > > The problem I have is this. In rc.conf I have the following: > > firewall_enable="YES" > firewall_script="/etc/rc.firewall" > firewall_type="/etc/ipfw.conf" > > And in /etc/ipfw.conf I have sets of rules one line at a time like: > > add 00010 divert natd all from any to any via xl0 > add 00120 allow tcp from any to any 80 via xl0 > > etc. > > This has always worked for me ever since I first started using ipfw on > fbsd 4.1 and has always worked on current until today's cvsup. Now though > no rules get loaded. > > If I try what I have always done in the past which is ipfw -q flush && > ipfw /etc/ipfw.conf then it tells me: > > usage: ipfw [options] > do "ipfw -h" or see ipfw manpage for details > > Whereas before this week this worked perfectly. The /etc/rc.firewall still > says that you can set a filename for the firewall_type so I assume this > should still work as in fact just broken rather than a POLA. > > I definatly mergemaster'd everything that had changed properly. In fact I > have even just run it again in case I missed something and everything is > up to date. > > Any comments? > > Regards, Matt. > > -- > email: matt@xtaz.co.uk - web: http://xtaz.co.uk/ > Hardware, n.: The parts of a computer system that can be kicked. I have noticed that there have been a large number of ipfw commits this week in the cvs logs and so I believe this could be related. I am therefore emailing this direct to luigi as hopefully he can help :) -- email: matt@xtaz.co.uk - web: http://xtaz.co.uk/ Hardware, n.: The parts of a computer system that can be kicked. From owner-freebsd-current@FreeBSD.ORG Sun Jul 13 05:32:09 2003 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id AA98137B404; Sun, 13 Jul 2003 05:32:09 -0700 (PDT) Received: from vexpert.dbai.tuwien.ac.at (vexpert.dbai.tuwien.ac.at [128.131.111.2]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6273943FCB; Sun, 13 Jul 2003 05:32:08 -0700 (PDT) (envelope-from pfeifer@dbai.tuwien.ac.at) Received: from [128.131.111.60] (acrux [128.131.111.60]) by vexpert.dbai.tuwien.ac.at (Postfix) with ESMTP id 6106913789; Sun, 13 Jul 2003 14:32:07 +0200 (CEST) Date: Sun, 13 Jul 2003 14:32:10 +0200 (CEST) From: Gerald Pfeifer To: Julian Elischer In-Reply-To: <200307082106.h68L6pKH061228@freefall.freebsd.org> Message-ID: References: <200307082106.h68L6pKH061228@freefall.freebsd.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: emulation@FreeBSD.org cc: current@FreeBSD.org Subject: Re: LDT entries and WINE and Threads.. X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 13 Jul 2003 12:32:10 -0000 On Tue, 8 Jul 2003, Julian Elischer wrote: > I'm looking at this and I think that my interpretation is that > WINE, under FreeBSD, blindly allocates LDT entries starting at location 17, > without looking to see if they are in use already.. Do you think that's a bug in Wine, or just a Linuxism? In both cases, I suggest you contact the Wine developers at wine-devel@winehq.com who have been relatively responsive wrt. portability improvements (and dozens of patches I submitted to them to keep Wine building and running on FreeBSD). > It seems to me that we could better serve the applications by having a > differnt API for setting LDTs, and that the kernel should keep track of > which is free and which is not. I agree that, even if there is a bug/Linuxism in Wine, we are better off by remaining as closely to the behavior of Linux in cases like this, for in the end, if something breaks on FreeBSD while it works on GNU/Linux, it makes little difference to the user _why_ it broke. > comments? Thanks for your efforts in this area! ;-) As emulators/wine maintainer and regular upstream contributor, I'd appreciate being Cc:ed on relevant messages on this (not the least because user support requests often arrive in my inbox). Gerald (@FreeBSD.org) -- Gerald "Jerry" pfeifer@dbai.tuwien.ac.at http://www.pfeifer.com/gerald/ From owner-freebsd-current@FreeBSD.ORG Sun Jul 13 06:11:31 2003 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1585037B407; Sun, 13 Jul 2003 06:11:31 -0700 (PDT) Received: from serio.al.rim.or.jp (serio.al.rim.or.jp [202.247.191.123]) by mx1.FreeBSD.org (Postfix) with ESMTP id BAD4D43FA3; Sun, 13 Jul 2003 06:11:29 -0700 (PDT) (envelope-from matoba@st.rim.or.jp) Received: from mail6.rim.or.jp by serio.al.rim.or.jp (3.7W/HMX-13) id WAA24238; Sun, 13 Jul 2003 22:11:28 +0900 (JST) Received: from localhost (ntkngw076167.kngw.nt.adsl.ppp.infoweb.ne.jp [220.145.116.167]) by mail6.rim.or.jp (8.9.3/3.7W) id WAA24211; Sun, 13 Jul 2003 22:11:26 +0900 (JST) Date: Sun, 13 Jul 2003 22:11:15 +0900 (JST) Message-Id: <20030713.221115.730550024.matoba@st.rim.or.jp> To: freebsd-current@freebsd.org From: MATOBA Hirozumi In-Reply-To: <49176.192.168.1.10.1058098656.squirrel@webmail.xtaz.co.uk> <20030713.024127.730548457.matoba@st.rim.or.jp> References: <49176.192.168.1.10.1058098656.squirrel@webmail.xtaz.co.uk> Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit cc: freebsd-ipfw@freebsd.org Subject: Re: IPFW and/or rc rule parsing not working since today's cvsup X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 13 Jul 2003 13:11:31 -0000 On Sun, 13 Jul 2003 13:17:36 +0100 (BST), "Matt" wrote: | The problem I have is this. In rc.conf I have the following: | | firewall_enable="YES" | firewall_script="/etc/rc.firewall" | firewall_type="/etc/ipfw.conf" | | And in /etc/ipfw.conf I have sets of rules one line at a time like: | | add 00010 divert natd all from any to any via xl0 | add 00120 allow tcp from any to any 80 via xl0 | | etc. | | This has always worked for me ever since I first started using ipfw on | fbsd 4.1 and has always worked on current until today's cvsup. Now though | no rules get loaded. | | If I try what I have always done in the past which is ipfw -q flush && | ipfw /etc/ipfw.conf then it tells me: | | usage: ipfw [options] | do "ipfw -h" or see ipfw manpage for details If your "/etc/ipfw.conf" has blank line(s), then you maybe met the same situation as me. The mail that I posted to freebsd-ipfw@freebsd.org is: There are 3 cases for calling show_usage() in ipfw2.c. My case is caught by "if (l == 0)" in ipfw_main(). The other cases are caught by "if (ac == 0)" and by "while ((ch = getopt(ac, av, "acdefhnNqs:STtv")) != -1) switch (ch) { ... default:". -- matoba@st.rim.or.jp From owner-freebsd-current@FreeBSD.ORG Sun Jul 13 06:13:54 2003 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1FED837B401 for ; Sun, 13 Jul 2003 06:13:54 -0700 (PDT) Received: from harmony.village.org (rover.bsdimp.com [204.144.255.66]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4A8B143F3F for ; Sun, 13 Jul 2003 06:13:53 -0700 (PDT) (envelope-from imp@bsdimp.com) Received: from localhost (warner@rover2.village.org [10.0.0.1]) by harmony.village.org (8.12.8/8.12.3) with ESMTP id h6DDDkJm079506; Sun, 13 Jul 2003 07:13:47 -0600 (MDT) (envelope-from imp@bsdimp.com) Date: Sun, 13 Jul 2003 07:13:42 -0600 (MDT) Message-Id: <20030713.071342.106032104.imp@bsdimp.com> To: rodrigc@crodrigues.org From: "M. Warner Losh" In-Reply-To: <20030713031312.GA89014@crodrigues.org> References: <20030712155333.GA79322@crodrigues.org> <20030713031312.GA89014@crodrigues.org> X-Mailer: Mew version 2.2 on Emacs 21.3 / Mule 5.0 (SAKAKI) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit cc: freebsd-current@freebsd.org Subject: Re: GCC 3.3.1, new warnings with X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 13 Jul 2003 13:13:54 -0000 In message: <20030713031312.GA89014@crodrigues.org> Craig Rodrigues writes: : I think that this is a FreeBSD issue. I compiled : the same file under Linux, with a GCC 3.3.1 checked out on 7/11 : and did not encounter this warning. keep in mind that on linux the -wno-system-headers is default, while it isn't default on freebsd, which is why we see it and you don't there... Warner From owner-freebsd-current@FreeBSD.ORG Sun Jul 13 06:22:10 2003 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 437CB37B401 for ; Sun, 13 Jul 2003 06:22:10 -0700 (PDT) Received: from harmony.village.org (rover.bsdimp.com [204.144.255.66]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8094243FAF for ; Sun, 13 Jul 2003 06:22:09 -0700 (PDT) (envelope-from imp@bsdimp.com) Received: from localhost (warner@rover2.village.org [10.0.0.1]) by harmony.village.org (8.12.8/8.12.3) with ESMTP id h6DDLxJm079554; Sun, 13 Jul 2003 07:21:59 -0600 (MDT) (envelope-from imp@bsdimp.com) Date: Sun, 13 Jul 2003 07:21:19 -0600 (MDT) Message-Id: <20030713.072119.61266976.imp@bsdimp.com> To: kabaev@mail.ru From: "M. Warner Losh" In-Reply-To: <20030713000559.28c18be6.kabaev@mail.ru> References: <20030713031312.GA89014@crodrigues.org> <20030713000559.28c18be6.kabaev@mail.ru> X-Mailer: Mew version 2.2 on Emacs 21.3 / Mule 5.0 (SAKAKI) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit cc: rodrigc@crodrigues.org cc: freebsd-current@freebsd.org Subject: Re: GCC 3.3.1, new warnings with X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 13 Jul 2003 13:22:10 -0000 In message: <20030713000559.28c18be6.kabaev@mail.ru> Alexander Kabaev writes: : Short of fixing offending files in FSF libstdc++ or turning warning : suppression back on for standard C++ include files selectively, I have : no suggestion. In the past I know that FSF has accepted patches back, so maybe the right thing to do is: o figure out the fix(es) that we need. o submit them to fsf o if they accpet them, then we can import them on the vendor branch or disable warnings in the system headers if not The warnings are quite annoying, and we'll get a lot of grief from the growing number of large c++ ports. I'd be happy to come up with a patch. Warner From owner-freebsd-current@FreeBSD.ORG Sun Jul 13 06:24:53 2003 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1ACA737B401 for ; Sun, 13 Jul 2003 06:24:53 -0700 (PDT) Received: from smtpout.mac.com (A17-250-248-89.apple.com [17.250.248.89]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7E78743FAF for ; Sun, 13 Jul 2003 06:24:52 -0700 (PDT) (envelope-from leimy2k@mac.com) Received: from mac.com (smtpin07-en2 [10.13.10.152]) by smtpout.mac.com (Xserve/MantshX 2.0) with ESMTP id h6DDOn17016685; Sun, 13 Jul 2003 06:24:49 -0700 (PDT) Received: from mac.com (adsl-78-178-166.jan.bellsouth.net [216.78.178.166]) (authenticated bits=0) by mac.com (Xserve/8.12.9/MantshX 2.0) with ESMTP id h6DDNtIK007942; Sun, 13 Jul 2003 06:24:13 -0700 (PDT) In-Reply-To: <20030713000559.28c18be6.kabaev@mail.ru> References: <20030712155333.GA79322@crodrigues.org> <20030713031312.GA89014@crodrigues.org> <20030713000559.28c18be6.kabaev@mail.ru> Mime-Version: 1.0 (Apple Message framework v578) Content-Type: text/plain; charset=US-ASCII; format=flowed Message-Id: <401FAE5E-B535-11D7-BE3B-0003937E39E0@mac.com> Content-Transfer-Encoding: 7bit From: David Leimbach Date: Sun, 13 Jul 2003 08:23:54 -0500 To: Alexander Kabaev X-Mailer: Apple Mail (2.578) cc: Craig Rodrigues cc: freebsd-current@freebsd.org Subject: Re: GCC 3.3.1, new warnings with X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 13 Jul 2003 13:24:53 -0000 On Saturday, July 12, 2003, at 11:05PM, Alexander Kabaev wrote: > On Sat, 12 Jul 2003 23:13:12 -0400 > Craig Rodrigues wrote: > >> I am guessing that the C preprocessor does not think that it is >> in a system header, and thus prints out the warning. > > We specifically disable automatic warning suppression for system > headers, because we _want_ to know about them. Your Linux distribution > apparently does not care. > This is a good policy in general, however, one could easily argue that what is trying to be determined with signedness and such being less-than-compared to 0 isn't really a big deal and possibly the only way to implement this numeric_limits::digits thing without any type introspection which C++ currently lacks. The following would work for example in a template function: template void foo(T const & f) { if (numeric_limits::digits % 2) //type is signed else //type is unsigned } However to implement "digits" we have that nasty macro that makes the comparison which is meaningless for unsigned types of "< 0". This is probably a perfect example of where the C++ standards committee folks should be queried about the best way to implement numeric_limits::digits. Some of them have had no trouble pointing out that C99's tgmath.h header cannot be implemented in pure standard C99. This may also be true of numeric_limits::digits. I am going to the newsgroups... My old college advisor is/was a moderator on comp.lang.c++.moderated and he may "just know" the answer :). >> >> Any GCC/FreeBSD expert care to comment? ;) >> > Short of fixing offending files in FSF libstdc++ or turning warning > suppression back on for standard C++ include files selectively, I have > no suggestion. I'd rather we fix the problem in gcc but this extra verbosity when there is nothing wrong with user code also seems incorrect. I think the gcc developers should have a separate command line option for internal headers don't you? > > -- > Alexander Kabaev From owner-freebsd-current@FreeBSD.ORG Sun Jul 13 06:25:15 2003 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id BFD4537B401 for ; Sun, 13 Jul 2003 06:25:15 -0700 (PDT) Received: from smtpout.mac.com (A17-250-248-97.apple.com [17.250.248.97]) by mx1.FreeBSD.org (Postfix) with ESMTP id 40C2843F93 for ; Sun, 13 Jul 2003 06:25:15 -0700 (PDT) (envelope-from leimy2k@mac.com) Received: from mac.com (smtpin07-en2 [10.13.10.152]) by smtpout.mac.com (Xserve/MantshX 2.0) with ESMTP id h6DDPCgi013512; Sun, 13 Jul 2003 06:25:12 -0700 (PDT) Received: from mac.com (adsl-78-178-166.jan.bellsouth.net [216.78.178.166]) (authenticated bits=0) by mac.com (Xserve/8.12.9/MantshX 2.0) with ESMTP id h6DDNtIL007942; Sun, 13 Jul 2003 06:24:50 -0700 (PDT) In-Reply-To: <20030713.071342.106032104.imp@bsdimp.com> References: <20030712155333.GA79322@crodrigues.org> <20030713031312.GA89014@crodrigues.org> <20030713.071342.106032104.imp@bsdimp.com> Mime-Version: 1.0 (Apple Message framework v578) Content-Type: text/plain; charset=US-ASCII; format=flowed Message-Id: <58C6702E-B535-11D7-BE3B-0003937E39E0@mac.com> Content-Transfer-Encoding: 7bit From: David Leimbach Date: Sun, 13 Jul 2003 08:24:35 -0500 To: "M. Warner Losh" X-Mailer: Apple Mail (2.578) cc: rodrigc@crodrigues.org cc: freebsd-current@freebsd.org Subject: Re: GCC 3.3.1, new warnings with X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 13 Jul 2003 13:25:16 -0000 On Sunday, July 13, 2003, at 8:13AM, M. Warner Losh wrote: > In message: <20030713031312.GA89014@crodrigues.org> > Craig Rodrigues writes: > : I think that this is a FreeBSD issue. I compiled > : the same file under Linux, with a GCC 3.3.1 checked out on 7/11 > : and did not encounter this warning. > > keep in mind that on linux the -wno-system-headers is default, while > it isn't default on freebsd, which is why we see it and you don't > there... Ah, excellent... this is exactly what I was looking for. :) > > Warner From owner-freebsd-current@FreeBSD.ORG Sun Jul 13 08:15:54 2003 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0BC5737B401 for ; Sun, 13 Jul 2003 08:15:54 -0700 (PDT) Received: from hotmail.com (law15-dav56.law15.hotmail.com [64.4.22.191]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9724543F3F for ; Sun, 13 Jul 2003 08:15:53 -0700 (PDT) (envelope-from travisnj@hotmail.com) Received: from mail pickup service by hotmail.com with Microsoft SMTPSVC; Sun, 13 Jul 2003 08:15:53 -0700 Received: from 68.54.76.199 by law15-dav56.law15.hotmail.com with DAV; Sun, 13 Jul 2003 15:15:53 +0000 X-Originating-IP: [68.54.76.199] X-Originating-Email: [travisnj@hotmail.com] From: "Travis Johnson" To: Date: Sun, 13 Jul 2003 11:15:50 -0400 X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2800.1106 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106 Message-ID: X-OriginalArrivalTime: 13 Jul 2003 15:15:53.0520 (UTC) FILETIME=[A6BEB300:01C34951] Subject: 4.8 Kernel Compiling Error X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 13 Jul 2003 15:15:54 -0000 mkdep -f .depend -a -nostdinc -D_KERNEL -DKLD_MODULE -I- -I. -I@ -I@/../include -I/ usr/obj/usr/src/i386/usr/include /usr/src/sys/modules/iir/../../dev/iir/iir.c /usr/src/sys/modules/iir/../../dev/iir/iir_ctrl.c /usr/src/sys/modules/iir/../../dev/iir/iir_pci.c /usr/src/sys/modules/iir/../../dev/iir/iir.c:56: stddef.h: No such file or directory mkdep: compile failed *** Error code 1 Stop in /usr/src/sys/modules/iir. *** Error code 1 Stop in /usr/src/sys/modules. *** Error code 1 Stop in /usr/obj/usr/src/sys/MYKERNEL. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. I have used src from the cdrom and from FTP1, regardless I am unable to compile the kernel. Any assistance would be appreciated Thank you. From owner-freebsd-current@FreeBSD.ORG Sun Jul 13 08:22:00 2003 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A3AA537B401 for ; Sun, 13 Jul 2003 08:22:00 -0700 (PDT) Received: from hexagon.stack.nl (hexagon.stack.nl [131.155.140.144]) by mx1.FreeBSD.org (Postfix) with ESMTP id B603C43F75 for ; Sun, 13 Jul 2003 08:21:59 -0700 (PDT) (envelope-from jilles@stack.nl) Received: by hexagon.stack.nl (Postfix, from userid 65534) id 652A91C65; Sun, 13 Jul 2003 17:21:58 +0200 (CEST) Received: from toad.stack.nl (zen.stack.nl [2001:610:1108:5010::130]) by hexagon.stack.nl (Postfix) with ESMTP id 7E0251C44; Sun, 13 Jul 2003 17:21:54 +0200 (CEST) Received: by toad.stack.nl (Postfix, from userid 1677) id 543E595; Sun, 13 Jul 2003 17:21:54 +0200 (CEST) Date: Sun, 13 Jul 2003 17:21:54 +0200 From: Jilles Tjoelker To: Craig Rodrigues Message-ID: <20030713152154.GA96653@stack.nl> References: <20030712155333.GA79322@crodrigues.org> <20030713031312.GA89014@crodrigues.org> <20030713000559.28c18be6.kabaev@mail.ru> <20030713044331.GA89785@crodrigues.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20030713044331.GA89785@crodrigues.org> User-Agent: Mutt/1.5.4i X-Spam-Status: No, hits=-5.0 required=5.0 tests=EMAIL_ATTRIBUTION,IN_REP_TO,QUOTED_EMAIL_TEXT,REFERENCES, REPLY_WITH_QUOTES,USER_AGENT_MUTT version=2.55 X-Spam-Level: X-Spam-Checker-Version: SpamAssassin 2.55 (1.174.2.19-2003-05-19-exp) cc: Alexander Kabaev cc: freebsd-current@freebsd.org Subject: Re: GCC 3.3.1, new warnings with X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 13 Jul 2003 15:22:01 -0000 On Sun, Jul 13, 2003 at 12:43:31AM -0400, Craig Rodrigues wrote: > The warnings seemed to be caused by this code in > /usr/include/c++/3.3/limits: > ========================================================================= > 630 static const int digits = __glibcpp_digits (unsigned int); > 631 static const int digits10 = __glibcpp_digits10 (unsigned int); > ========================================================================= > The macros are defined in the same file here: > ============================================================================ > 134 #define __glibcpp_signed(T) ((T)(-1) < 0) > > 142 #define __glibcpp_digits(T) \ > 143 (sizeof(T) * __CHAR_BIT__ - __glibcpp_signed (T)) > ============================================================================ > The expanded macros look like: > static const int digits = (sizeof(unsigned int) * 8 - ((unsigned int)(-1) < 0)); > static const int digits10 = ((sizeof(unsigned int) * 8 - ((unsigned int)(-1) < 0)) * 643 / 2136); Perhaps this would work: #define __glibcpp_signed(T) (!((T)(-1) > 0)) I have tried this with GCC 3.2 (5.1-BETA i386, -W -Wall), and a plain C program (not C++). cc and c++ do the same. The old macro gives the warning about comparing signed types, but the new one does not. They both work for int, u_int, unsigned int and char. The compiler moans about (T)(-1) >= 0 as well. Is the assumption that (unsigned type)(-1) is never zero valid? If it's not, try (!((T)(-1) > 0 || (T)(-1) == 0)). GCC does not seem to moan about that, even though it's exactly the same as using >=. Jilles Tjoelker From owner-freebsd-current@FreeBSD.ORG Sun Jul 13 08:32:43 2003 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id EDABE37B401; Sun, 13 Jul 2003 08:32:43 -0700 (PDT) Received: from kientzle.com (h-66-166-149-50.SNVACAID.covad.net [66.166.149.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id 389B843F75; Sun, 13 Jul 2003 08:32:42 -0700 (PDT) (envelope-from kientzle@acm.org) Received: from acm.org (ugly.x.kientzle.com [66.166.149.53]) by kientzle.com (8.12.9/8.12.9) with ESMTP id h6DFWAgY024633; Sun, 13 Jul 2003 08:32:11 -0700 (PDT) (envelope-from kientzle@acm.org) Message-ID: <3F117C26.7080100@acm.org> Date: Sun, 13 Jul 2003 08:35:02 -0700 From: Tim Kientzle User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.0.1) Gecko/20021005 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Bruce Evans References: <20030712165749.GA14599@colocall.net> <3F104A71.7060906@acm.org> <3F105499.BC7768C0@mindspring.com> <3F10576E.3060904@acm.org> <20030713095642.B1771@gamplex.bde.org> <3F10B60C.3000106@acm.org> <20030713123229.A2435@gamplex.bde.org> Content-Type: multipart/mixed; boundary="------------000702050209080300050405" cc: jmallett@freebsd.org cc: freebsd-current@freebsd.org cc: Andrey Elperin Subject: Re: make release of CURRENT on 4.7 box X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: kientzle@acm.org List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 13 Jul 2003 15:32:44 -0000 This is a multi-part message in MIME format. --------------000702050209080300050405 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Bruce Evans wrote: > On Sat, 12 Jul 2003, Tim Kientzle wrote: >>In particular, newvers.sh is being run with the >>current directory being ${.OBJDIR}, and ${.OBJDIR} >>doesn't contain a Makefile, ... > > ... `make -V FOO' doesn't require a Makefile in -current. ... A-HA! >>I don't know the "right" way to fix this ... > > I think splitting it or making it exit after just setting variables > in the userland case is the right fix. ... I think you're right, but don't see a very simple way to make that work, especially given the surprising number of places that newvers.sh is used. However, the following one-line patch does work; it simply creates enough of a Makefile to silence make's warnings. Needs testing under -CURRENT, but I'm pretty confident it will work there as well. If someone could test this under -CURRENT and commit it, those of us doing 4.x->CURRENT cross-builds would greatly appreciate it. Tim --------------000702050209080300050405 Content-Type: text/plain; name="kientzle_include_Makefile.diff" Content-Transfer-Encoding: 7bit Content-Disposition: inline; filename="kientzle_include_Makefile.diff" Index: include/Makefile =================================================================== RCS file: /usr/cvs/FreeBSD-CVS/src/include/Makefile,v retrieving revision 1.204 diff -u -r1.204 Makefile --- include/Makefile 4 Jul 2003 19:54:06 -0000 1.204 +++ include/Makefile 13 Jul 2003 05:43:33 -0000 @@ -51,11 +51,17 @@ INCS+= osreldate.h +# The use of 'newvers.sh' here is kind of bogus, because +# it creates some additional files and does a few other odd +# things. The 'touch Makefile' here allows newvers.sh to +# run on 4.x, whose 'make' requires a Makefile for '-V KERN_IDENT' +# osreldate.h: ${.CURDIR}/../sys/conf/newvers.sh \ ${.CURDIR}/../sys/sys/param.h \ ${.CURDIR}/Makefile @${ECHO} creating osreldate.h from newvers.sh @setvar PARAMFILE ${.CURDIR}/../sys/sys/param.h; \ + echo default: > Makefile; \ . ${.CURDIR}/../sys/conf/newvers.sh; \ echo "$$COPYRIGHT" > osreldate.h; \ echo "#ifdef _KERNEL" >> osreldate.h; \ --------------000702050209080300050405-- From owner-freebsd-current@FreeBSD.ORG Sun Jul 13 08:39:34 2003 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D0DBE37B401 for ; Sun, 13 Jul 2003 08:39:34 -0700 (PDT) Received: from kientzle.com (h-66-166-149-50.SNVACAID.covad.net [66.166.149.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4574443F75 for ; Sun, 13 Jul 2003 08:39:34 -0700 (PDT) (envelope-from kientzle@acm.org) Received: from acm.org (ugly.x.kientzle.com [66.166.149.53]) by kientzle.com (8.12.9/8.12.9) with ESMTP id h6DFdRgY024659; Sun, 13 Jul 2003 08:39:27 -0700 (PDT) (envelope-from kientzle@acm.org) Message-ID: <3F117DDB.3000508@acm.org> Date: Sun, 13 Jul 2003 08:42:19 -0700 From: Tim Kientzle User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.0.1) Gecko/20021005 X-Accept-Language: en-us, en MIME-Version: 1.0 To: John Reynolds References: <16144.55332.161178.446499@whale.home-net> <20030713044837.GA56283@pit.databus.com> <16144.60146.32326.419894@whale.home-net> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit cc: Barney Wolff cc: current@freebsd.org Subject: Re: build error building cvs doc? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: kientzle@acm.org List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 13 Jul 2003 15:39:35 -0000 John Reynolds wrote: > [ On Sunday, July 13, Barney Wolff wrote: ] >>Me too. I'm about to try re-cvsupping, in case I caught some update >>in the middle. > > Somebody else asked if I was doing a "make -jN" buildworld where N > 1 and I > was. So, I just now did a buildworld with one process and it finished just > fine. Strange. > > The only other thing in the original logfile shows: > > make: don't know how to make /usr/obj/usr/src/rescue/rescue//usr/src/sbin/dhclient/client/clparse.o. Stop > *** Error code 2 > 1 error > > So, perhaps something related to the above is not "-jN safe". Yes, /rescue is known to be "not -jN safe" I've been trying to puzzle out exactly why and how to fix, but have yet to come up with anything. Suggestions/comments/advice welcome. Tim From owner-freebsd-current@FreeBSD.ORG Sun Jul 13 08:57:39 2003 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D9AA837B401 for ; Sun, 13 Jul 2003 08:57:39 -0700 (PDT) Received: from walton.kettenis.dyndns.org (a169212.upc-a.chello.nl [62.163.169.212]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9A85443F85 for ; Sun, 13 Jul 2003 08:57:36 -0700 (PDT) (envelope-from kettenis@elgar.kettenis.dyndns.org) Received: from elgar.kettenis.dyndns.org (elgar.kettenis.dyndns.org [192.168.0.2])h6DFvZaM009945; Sun, 13 Jul 2003 17:57:35 +0200 (CEST) (envelope-from kettenis@elgar.kettenis.dyndns.org) Received: from elgar.kettenis.dyndns.org (localhost [127.0.0.1]) h6DFvZt3098300; Sun, 13 Jul 2003 17:57:35 +0200 (CEST) (envelope-from kettenis@elgar.kettenis.dyndns.org) Received: (from kettenis@localhost)h6DFvYRD098297; Sun, 13 Jul 2003 17:57:34 +0200 (CEST) Date: Sun, 13 Jul 2003 17:57:34 +0200 (CEST) Message-Id: <200307131557.h6DFvYRD098297@elgar.kettenis.dyndns.org> From: Mark Kettenis To: marcel@xcllnt.net In-reply-to: <20030712203930.GA5446@dhcp01.pn.xcllnt.net> (message from Marcel Moolenaar on Sat, 12 Jul 2003 13:39:30 -0700) References: <20030711225002.GA71126@ns1.xcllnt.net> <200307121105.h6CB50l1047073@elgar.kettenis.dyndns.org> <20030712203930.GA5446@dhcp01.pn.xcllnt.net> cc: current@FreeBSD.org Subject: Re: GDB - do we dare? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 13 Jul 2003 15:57:40 -0000 Date: Sat, 12 Jul 2003 13:39:30 -0700 From: Marcel Moolenaar On Sat, Jul 12, 2003 at 01:05:00PM +0200, Mark Kettenis wrote: > > o We still have the Alpha gdb -k bug moved over from the 5.1 todo > list to the 5.2 todo list. I think this is "just" a bug fix. > > I'm not really familliar with the support for debugging FreeBSD > kernels in GDB since that support is not in the FSF tree. Is there > any chance that this code will be contributed back? This would > involve a copyright assignment, which could prove to be a major > obstacle. The copyright of our kgdb support is already the FSF. See /usr/src/gnu/usr.bin/binutils/gdb/kvm-fbsd.c I'll have to find out whether the paperwork is actually there. > The current support for debuggung libc_r-based threading is also not > present in the FSF tree. So the question raised above applies here too. It looks to me that it can be contributed back. That would be great. > I'm not really familiar with KSE, but AFAIK the kernel interfaces for > debugging KSE's aren't there yet. I think that's mostly due to a knowledge gap. We just need people who can bridge between gdb and FreeBSD. Someone like you :-) > o gdb(1) has created a 6.x branch, so it's likely that a new release > is in the pipeline (within 6 months?). Upgrading to 5.3 may make > a future upgrade easier due to smaller diffs and refreshed know-how. > > GDB 6.0 will defenitely be released before the end of the year :-). > We're aiming at the end of August, but it will probably be somewhere > in September. Interesting. It may even be possible to make gdb 6.0 part of FreeBSD 5.2 scheduling wise. Do we need a binutils update? We now have 2.13.2. Probably, yes. FSF GDB releases use a libbfd that's basically a snapshot taken at the point where the release branch was cut. You folks seem to try to get away with using libbfd from binutils. This usually works as long as the GDB and binutils releases used are not too far apart, so it's more likely that this works if binutils is updated. Actually, I think you'll need binutils 2.14 anyway for TLS. > A1 If having support for amd64 is a major reason for doing a new > import of GDB, importing the upcoming GDB 6.0 would make more sense > to me. No ia64 is the major reason :-) Hmm. I think I just crashed pluto1 trying to get it to run the GDB testsuite on a not-yet-fully-functional GDB port. Currently RSE is giving me some headaches. > A2 I'm volunteering to help out here. Cool, thanks. Shall we just create a p4 branch and start hacking? Oh dear, do I need to learn another version control system? Anyway, this can probably wait. I'll be on vacation from next tuesday until August 10, and I still have to do some work on the upstream GDB sources before I can start thinking about integrating things in the FreeBSD source tree. The GDB sparc target has suffered some bit rot, up to the point where it is hardly usable. > better on FreeBSD/i386 and FreeBSD/Alpha now. Now that I've got it > working on FreeBSD/amd64, I'll give FreeBSD/ia64 a shot. We probably need to talk then, because the ptrace interface needs to be fleshed out and I planned to do that while porting gdb. Probably. The current layout of `struct reg' and `struct fpreg' is a bit ... messy. Mark From owner-freebsd-current@FreeBSD.ORG Sun Jul 13 09:49:42 2003 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id AF6A237B401; Sun, 13 Jul 2003 09:49:42 -0700 (PDT) Received: from mailman.zeta.org.au (mailman.zeta.org.au [203.26.10.16]) by mx1.FreeBSD.org (Postfix) with ESMTP id 31CC243F3F; Sun, 13 Jul 2003 09:49:41 -0700 (PDT) (envelope-from bde@zeta.org.au) Received: from gamplex.bde.org (katana.zip.com.au [61.8.7.246]) by mailman.zeta.org.au (8.9.3p2/8.8.7) with ESMTP id CAA14538; Mon, 14 Jul 2003 02:49:17 +1000 Date: Mon, 14 Jul 2003 02:49:16 +1000 (EST) From: Bruce Evans X-X-Sender: bde@gamplex.bde.org To: Tim Kientzle In-Reply-To: <3F117C26.7080100@acm.org> Message-ID: <20030714021543.O4685@gamplex.bde.org> References: <20030712165749.GA14599@colocall.net> <3F104A71.7060906@acm.org> <3F105499.BC7768C0@mindspring.com> <3F10576E.3060904@acm.org> <20030713095642.B1771@gamplex.bde.org> <3F10B60C.3000106@acm.org> <20030713123229.A2435@gamplex.bde.org> <3F117C26.7080100@acm.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: jmallett@freebsd.org cc: freebsd-current@freebsd.org cc: Andrey Elperin Subject: Re: make release of CURRENT on 4.7 box X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 13 Jul 2003 16:49:43 -0000 On Sun, 13 Jul 2003, Tim Kientzle wrote: > Bruce Evans wrote: > > I think splitting it or making it exit after just setting variables > > in the userland case is the right fix. ... [it == newvers.sh] > > I think you're right, but don't see a very simple way to make that > work, especially given the surprising number of places > that newvers.sh is used. I think there aren't so many -- only kernel Makefiles and src/include/Makefile. There seems to be a simple way due to bitrot. $1 in newvers.sh is not set when newvers.sh is invoked from src/include/Makefile, but it seems to always be set when newvers.sh is invoked from kernel Makefiles, due to garbage in the latter. The garbage is now centralized in sys/conf/kern.post.mk: sh $S/conf/newvers.sh ${KERN_IDENT} ^^^^^^^^^^^^^ This passes an unused variable to newvers.sh. Passing and use of this variable was removed in 4.4BSD-Lite1, but FreeBSD's kernel Makefiles are based on Net/2 and haven't caught up with this change yet, while FreeBSD's newvers.sh is based on the Lite1 so it has the change. This variable became needed again in newvers.sh last month, but it wasn't used; the make -V hack was used instead. Some relevant uses and non-uses of $1 in newvers.sh: %%% FreeBSD rev.1.1 (same as Net/2?) echo "char version[] = \"version: ${v} ($1) ${t}\";" ^^^^ FreeBSD-1.1.5: echo "const char version[] = \"${kernvers} ($1) #${v}: ${t}\\n ${user}@${host}:${dir}\\n\";" ^^^^ 4.4BSD-Lite1: echo "char version[] = \"4.4BSD-Lite #${v}: ${t}\\n ${u}@${h}:${d}\\n\";" >>vers.c [No $1's here or elsewhere in newvers.sh] -current: i=`make -V KERN_IDENT` ... char version[] = "${VERSION} #${v}: ${t}\\n ${u}@${h}:${d}\\n"; ... char kern_ident[] = "${i}"; [No $1's here or elsewhere in newvers.sh, but I think $i is always the same as $1.] %%% So removing the make -V line and just using $1 should fix the main problem and the bitrot. Bruce From owner-freebsd-current@FreeBSD.ORG Sun Jul 13 09:50:20 2003 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id AAEF037B41B for ; Sun, 13 Jul 2003 09:50:20 -0700 (PDT) Received: from ns1.xcllnt.net (209-128-86-226.bayarea.net [209.128.86.226]) by mx1.FreeBSD.org (Postfix) with ESMTP id BE83443F93 for ; Sun, 13 Jul 2003 09:50:19 -0700 (PDT) (envelope-from marcel@xcllnt.net) Received: from dhcp01.pn.xcllnt.net (dhcp01.pn.xcllnt.net [192.168.4.201]) by ns1.xcllnt.net (8.12.9/8.12.9) with ESMTP id h6DGoHv1084880; Sun, 13 Jul 2003 09:50:17 -0700 (PDT) (envelope-from marcel@piii.pn.xcllnt.net) Received: from dhcp01.pn.xcllnt.net (localhost [127.0.0.1]) by dhcp01.pn.xcllnt.net (8.12.9/8.12.9) with ESMTP id h6DGoHE8077665; Sun, 13 Jul 2003 09:50:17 -0700 (PDT) (envelope-from marcel@dhcp01.pn.xcllnt.net) Received: (from marcel@localhost) by dhcp01.pn.xcllnt.net (8.12.9/8.12.9/Submit) id h6DGoGVd077664; Sun, 13 Jul 2003 09:50:16 -0700 (PDT) (envelope-from marcel) Date: Sun, 13 Jul 2003 09:50:16 -0700 From: Marcel Moolenaar To: Mark Kettenis Message-ID: <20030713165016.GA77613@dhcp01.pn.xcllnt.net> References: <20030711225002.GA71126@ns1.xcllnt.net> <200307121105.h6CB50l1047073@elgar.kettenis.dyndns.org> <20030712203930.GA5446@dhcp01.pn.xcllnt.net> <200307131557.h6DFvYRD098297@elgar.kettenis.dyndns.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200307131557.h6DFvYRD098297@elgar.kettenis.dyndns.org> User-Agent: Mutt/1.5.4i cc: current@FreeBSD.org Subject: Re: GDB - do we dare? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 13 Jul 2003 16:50:21 -0000 On Sun, Jul 13, 2003 at 05:57:34PM +0200, Mark Kettenis wrote: > > > A1 If having support for amd64 is a major reason for doing a new > > import of GDB, importing the upcoming GDB 6.0 would make more sense > > to me. > > No ia64 is the major reason :-) > > Hmm. I think I just crashed pluto1 trying to get it to run the GDB > testsuite on a not-yet-fully-functional GDB port. Currently RSE is > giving me some headaches. Yeah, this is known (both the crashes and the headache :-) I was working on that (the crashes), but now need to make ia64 functional again. The gcc import left us dead in the water. Our crt1.c is broken. > > A2 I'm volunteering to help out here. > > Cool, thanks. Shall we just create a p4 branch and start hacking? > > Oh dear, do I need to learn another version control system? Yes, preferrably. Using a p4 branch allows us to track the gdb 6 branch while we prepare for the import. It's a convenient place for people to grab the WIP. > > better on FreeBSD/i386 and FreeBSD/Alpha now. Now that I've got it > > working on FreeBSD/amd64, I'll give FreeBSD/ia64 a shot. > > We probably need to talk then, because the ptrace interface needs > to be fleshed out and I planned to do that while porting gdb. > > Probably. The current layout of `struct reg' and `struct fpreg' is a > bit ... messy. It is not. It is actually pretty neat. Incomplete maybe, but neat. -- Marcel Moolenaar USPA: A-39004 marcel@xcllnt.net From owner-freebsd-current@FreeBSD.ORG Sun Jul 13 09:50:58 2003 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 7ABB437B401 for ; Sun, 13 Jul 2003 09:50:58 -0700 (PDT) Received: from mail5.atl.registeredsite.com (mail5.atl.registeredsite.com [64.224.219.79]) by mx1.FreeBSD.org (Postfix) with ESMTP id B3FC443FB1 for ; Sun, 13 Jul 2003 09:50:57 -0700 (PDT) (envelope-from ) Received: from imta04a2.registeredsite.com (imta04a2.registeredsite.com [64.225.255.13])h6DFq38J016811 for ; Sun, 13 Jul 2003 11:52:03 -0400 To: current@FreeBSD.org From: "Auto-reply from ag@esqwire.com" In-Reply-To: <200307131650.h6DGoaOW002206@inbound-mx10.atl.registeredsite.com> Precedence: bulk Date: Sun, 13 Jul 2003 12:50:56 -0400 Message-ID: <20030713165056.NNHD25464.imta04a2.registeredsite.com@imta04a2> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Subject: Re: Movie X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 13 Jul 2003 16:50:58 -0000 MY ADDRESS HAS CHANGED. PLEASE RE-SEND YOUR EMAIL AS SET FORTH BELOW: CHANGE OF ADDRESS: Due to the Receipt of a tremendous amount of SPAM, I have changed my email address. My new email address is my first name @ my web site domain name. You should know what my first name and domain name are. My first name is available at my web site. You can also call me at 856-874-9651. Sorry for the inconvenience. From owner-freebsd-current@FreeBSD.ORG Sun Jul 13 10:07:33 2003 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id EFC7537B4B2 for ; Sun, 13 Jul 2003 10:07:32 -0700 (PDT) Received: from hotmail.com (law15-dav58.law15.hotmail.com [64.4.22.193]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8819743FAF for ; Sun, 13 Jul 2003 10:07:32 -0700 (PDT) (envelope-from travisnj@hotmail.com) Received: from mail pickup service by hotmail.com with Microsoft SMTPSVC; Sun, 13 Jul 2003 10:07:32 -0700 Received: from 68.54.76.199 by law15-dav58.law15.hotmail.com with DAV; Sun, 13 Jul 2003 17:07:32 +0000 X-Originating-IP: [68.54.76.199] X-Originating-Email: [travisnj@hotmail.com] From: "Travis Johnson" To: Date: Sun, 13 Jul 2003 13:07:30 -0400 X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2800.1106 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106 Message-ID: X-OriginalArrivalTime: 13 Jul 2003 17:07:32.0599 (UTC) FILETIME=[3FB50870:01C34961] Subject: Fw: 4.8 Kernel Compiling Error X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 13 Jul 2003 17:07:33 -0000 the error that I was receiving was due the default directory of config was ../../ and it was incorrect you must specify the FQP of the kernel you are building and then make depend will work fine.. Thanks ----- Original Message ----- From: "Travis Johnson" To: Sent: Sunday, July 13, 2003 11:15 AM Subject: 4.8 Kernel Compiling Error > mkdep -f > .depend -a -nostdinc -D_KERNEL -DKLD_MODULE -I- -I. -I@ -I@/../include -I/ > usr/obj/usr/src/i386/usr/include > /usr/src/sys/modules/iir/../../dev/iir/iir.c > /usr/src/sys/modules/iir/../../dev/iir/iir_ctrl.c > /usr/src/sys/modules/iir/../../dev/iir/iir_pci.c > /usr/src/sys/modules/iir/../../dev/iir/iir.c:56: stddef.h: No such file or > directory > mkdep: compile failed > *** Error code 1 > > Stop in /usr/src/sys/modules/iir. > *** Error code 1 > > Stop in /usr/src/sys/modules. > *** Error code 1 > > Stop in /usr/obj/usr/src/sys/MYKERNEL. > *** Error code 1 > > Stop in /usr/src. > *** Error code 1 > > Stop in /usr/src. > > I have used src from the cdrom and from FTP1, regardless I am unable to > compile the kernel. > > Any assistance would be appreciated > > Thank you. > > From owner-freebsd-current@FreeBSD.ORG Sun Jul 13 10:32:36 2003 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id F25D337B404 for ; Sun, 13 Jul 2003 10:32:35 -0700 (PDT) Received: from dust.freshx.de (freshx.de [80.190.100.215]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6880B43FAF for ; Sun, 13 Jul 2003 10:32:35 -0700 (PDT) (envelope-from kai.mosebach@freshx.de) Received: from alpha (p508B3231.dip.t-dialin.net [80.139.50.49]) by dust.freshx.de (Postfix) with ESMTP id 2360715E0B5 for ; Sun, 13 Jul 2003 19:32:26 +0200 (CEST) From: "Kai Mosebach" To: Date: Sun, 13 Jul 2003 19:32:38 +0200 Message-ID: <000201c34964$c1c4c000$0100000a@alpha> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook, Build 10.0.4024 Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165 Subject: linuxthreads not compiling X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 13 Jul 2003 17:32:36 -0000 Hi, - I have a 5.1-CURRENT system from 2003-July-10. - I tried to compile the linuxthreads package, but it failed. - From current.freebsd.org i downloaded the ports.tgz from 2003-July-11 - still linuxthreads isnt compiling error looks like : cc -O -pipe -mcpu=pentiumpro -mcpu=pentiumpro -g -O2 -Wall -DCOMPILING_LINUXTHREADS -I/usr/ports/devel/linuxthreads/work/linuxthreads-2.2.3_12 -I/usr/ports/devel/linuxthreads/work/linuxthreads-2.2.3_12/sysdeps/i386 -I/usr/ports/devel/linuxthreads/work/linuxthreads-2.2.3_12/sysdeps/pthre ad -I/usr/ports/devel/linuxthreads/work/linuxthreads-2.2.3_12/sysdeps/unix/ sysv/linux -I/usr/src/lib/libc/stdtime -DLIBC_RCS -DLINUXTHREADS -D__USE_UNIX98 -D__USE_XOPEN2K -D_STACK_GROWS_DOWN -DNEWLIBC -D_THREAD_SAFE -c clone.S clone.S:8:17: SYS.h: No such file or directory {standard input}: Assembler messages: {standard input}:55: Error: no such instruction: `kerncall' *** Error code 1 Stop in /usr/ports/devel/linuxthreads/work/linuxthreads-2.2.3_12. *** Error code 1 Stop in /usr/ports/devel/linuxthreads. Any ideas ? Regards kai From owner-freebsd-current@FreeBSD.ORG Sun Jul 13 10:41:49 2003 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id DCE6437B401 for ; Sun, 13 Jul 2003 10:41:49 -0700 (PDT) Received: from xorpc.icir.org (xorpc.icir.org [192.150.187.68]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4289D43F93 for ; Sun, 13 Jul 2003 10:41:49 -0700 (PDT) (envelope-from rizzo@xorpc.icir.org) Received: from xorpc.icir.org (localhost [127.0.0.1]) by xorpc.icir.org (8.12.8p1/8.12.3) with ESMTP id h6DHfmkN074228; Sun, 13 Jul 2003 10:41:48 -0700 (PDT) (envelope-from rizzo@xorpc.icir.org) Received: (from rizzo@localhost) by xorpc.icir.org (8.12.8p1/8.12.3/Submit) id h6DHfmm0074227; Sun, 13 Jul 2003 10:41:48 -0700 (PDT) (envelope-from rizzo) Date: Sun, 13 Jul 2003 10:41:48 -0700 From: Luigi Rizzo To: Matt Message-ID: <20030713104148.A74162@xorpc.icir.org> References: <49176.192.168.1.10.1058098656.squirrel@webmail.xtaz.co.uk> <49205.192.168.1.10.1058099467.squirrel@webmail.xtaz.co.uk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5.1i In-Reply-To: <49205.192.168.1.10.1058099467.squirrel@webmail.xtaz.co.uk>; from matt@xtaz.co.uk on Sun, Jul 13, 2003 at 01:31:07PM +0100 cc: current@FreeBSD.org Subject: Re: IPFW and/or rc rule parsing not working since today's cvsup X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 13 Jul 2003 17:41:50 -0000 thanks for pointing out -- it turns out that by mistake i have changed the handling of blank lines in ipfw configs. I will restore the old behaviour ASAP (it's a trivial 1-2 line change). cheers luigi On Sun, Jul 13, 2003 at 01:31:07PM +0100, Matt wrote: > > Matt said: > > I normally sync to current once a week and have just done it today: > > > > FreeBSD tao.xtaz.co.uk 5.1-CURRENT FreeBSD 5.1-CURRENT #0: Sun Jul 13 > > 12:24:40 BST 2003 root@shakira.xtaz.co.uk:/usr/obj/usr/src/sys/TAO > > i386 > > > > The problem is though that it looks like IPFW or RC has changed how it > > works. I'm not sure if this is intentional or not though. If it is > > intentional then I think it is a violation of POLA. > > > > The problem I have is this. In rc.conf I have the following: > > > > firewall_enable="YES" > > firewall_script="/etc/rc.firewall" > > firewall_type="/etc/ipfw.conf" > > > > And in /etc/ipfw.conf I have sets of rules one line at a time like: > > > > add 00010 divert natd all from any to any via xl0 > > add 00120 allow tcp from any to any 80 via xl0 > > > > etc. > > > > This has always worked for me ever since I first started using ipfw on > > fbsd 4.1 and has always worked on current until today's cvsup. Now though > > no rules get loaded. > > > > If I try what I have always done in the past which is ipfw -q flush && > > ipfw /etc/ipfw.conf then it tells me: > > > > usage: ipfw [options] > > do "ipfw -h" or see ipfw manpage for details > > > > Whereas before this week this worked perfectly. The /etc/rc.firewall still > > says that you can set a filename for the firewall_type so I assume this > > should still work as in fact just broken rather than a POLA. > > > > I definatly mergemaster'd everything that had changed properly. In fact I > > have even just run it again in case I missed something and everything is > > up to date. > > > > Any comments? > > > > Regards, Matt. > > > > -- > > email: matt@xtaz.co.uk - web: http://xtaz.co.uk/ > > Hardware, n.: The parts of a computer system that can be kicked. > > I have noticed that there have been a large number of ipfw commits this > week in the cvs logs and so I believe this could be related. I am > therefore emailing this direct to luigi as hopefully he can help :) > > -- > email: matt@xtaz.co.uk - web: http://xtaz.co.uk/ > Hardware, n.: The parts of a computer system that can be kicked. From owner-freebsd-current@FreeBSD.ORG Sun Jul 13 11:11:36 2003 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 83C9737B401 for ; Sun, 13 Jul 2003 11:11:36 -0700 (PDT) Received: from harmony.village.org (rover.bsdimp.com [204.144.255.66]) by mx1.FreeBSD.org (Postfix) with ESMTP id AB86E43FAF for ; Sun, 13 Jul 2003 11:11:35 -0700 (PDT) (envelope-from imp@bsdimp.com) Received: from localhost (warner@rover2.village.org [10.0.0.1]) by harmony.village.org (8.12.9/8.12.3) with ESMTP id h6DIBUcF001569; Sun, 13 Jul 2003 12:11:31 -0600 (MDT) (envelope-from imp@bsdimp.com) Date: Sun, 13 Jul 2003 12:11:25 -0600 (MDT) Message-Id: <20030713.121125.54936166.imp@bsdimp.com> To: jilles@stack.nl From: "M. Warner Losh" In-Reply-To: <20030713152154.GA96653@stack.nl> References: <20030713000559.28c18be6.kabaev@mail.ru> <20030713044331.GA89785@crodrigues.org> <20030713152154.GA96653@stack.nl> X-Mailer: Mew version 2.2 on Emacs 21.3 / Mule 5.0 (SAKAKI) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit cc: rodrigc@crodrigues.org cc: kabaev@mail.ru cc: freebsd-current@freebsd.org Subject: Re: GCC 3.3.1, new warnings with X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 13 Jul 2003 18:11:36 -0000 In message: <20030713152154.GA96653@stack.nl> Jilles Tjoelker writes: : The compiler moans about (T)(-1) >= 0 as well. Is the assumption that : (unsigned type)(-1) is never zero valid? yes. There are no known machines where -1 == 0 for types of different signs. Further, the C standard says that it must behave as if it is a two's complement machine, and I think that C++ says so too. Warner From owner-freebsd-current@FreeBSD.ORG Sun Jul 13 11:24:43 2003 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C9E3C37B401 for ; Sun, 13 Jul 2003 11:24:43 -0700 (PDT) Received: from harmony.village.org (rover.bsdimp.com [204.144.255.66]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4466843FB1 for ; Sun, 13 Jul 2003 11:24:35 -0700 (PDT) (envelope-from imp@bsdimp.com) Received: from localhost (warner@rover2.village.org [10.0.0.1]) by harmony.village.org (8.12.9/8.12.3) with ESMTP id h6DINucF001632; Sun, 13 Jul 2003 12:23:57 -0600 (MDT) (envelope-from imp@bsdimp.com) Date: Sun, 13 Jul 2003 12:23:52 -0600 (MDT) Message-Id: <20030713.122352.22176834.imp@bsdimp.com> To: jilles@stack.nl From: "M. Warner Losh" In-Reply-To: <20030713152154.GA96653@stack.nl> References: <20030713000559.28c18be6.kabaev@mail.ru> <20030713044331.GA89785@crodrigues.org> <20030713152154.GA96653@stack.nl> X-Mailer: Mew version 2.2 on Emacs 21.3 / Mule 5.0 (SAKAKI) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit cc: rodrigc@crodrigues.org cc: kabaev@mail.ru cc: freebsd-current@freebsd.org Subject: Re: GCC 3.3.1, new warnings with X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 13 Jul 2003 18:24:44 -0000 : > 134 #define __glibcpp_signed(T) ((T)(-1) < 0) : #define __glibcpp_signed(T) (!((T)(-1) > 0)) Why not the simpler: #define __glibcpp_signed(T) ((T)(-1) <= 0) that way we have an overlap on the range of the two types, so we won't get a warning. We know for a fact that -1 != 0 for all known machine types (all machines are two's complement, or are required to behave as if they are two's complement, per the standard). (unsigned int) -1 == 0xffffffff (assuming 32-bit int). even on a one's complement's machine, without the standard conversion, the 'type punning' conversion of -1 would yield 0xfffffffe, which is still > 0. Warner From owner-freebsd-current@FreeBSD.ORG Sun Jul 13 11:25:58 2003 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 5662337B404 for ; Sun, 13 Jul 2003 11:25:58 -0700 (PDT) Received: from smtpout.mac.com (A17-250-248-87.apple.com [17.250.248.87]) by mx1.FreeBSD.org (Postfix) with ESMTP id A290A43F93 for ; Sun, 13 Jul 2003 11:25:57 -0700 (PDT) (envelope-from leimy2k@mac.com) Received: from mac.com (smtpin08-en2 [10.13.10.153]) by smtpout.mac.com (Xserve/MantshX 2.0) with ESMTP id h6DIPo4U002683; Sun, 13 Jul 2003 11:25:50 -0700 (PDT) Received: from mac.com (adsl-78-178-166.jan.bellsouth.net [216.78.178.166]) (authenticated bits=0) by mac.com (Xserve/8.12.9/MantshX 2.0) with ESMTP id h6DIPlsq012844; Sun, 13 Jul 2003 11:25:47 -0700 (PDT) In-Reply-To: <20030713.121125.54936166.imp@bsdimp.com> References: <20030713000559.28c18be6.kabaev@mail.ru> <20030713044331.GA89785@crodrigues.org> <20030713152154.GA96653@stack.nl> <20030713.121125.54936166.imp@bsdimp.com> Mime-Version: 1.0 (Apple Message framework v578) Content-Type: text/plain; charset=BIG5; format=flowed Message-Id: <6B36552C-B55F-11D7-BE3B-0003937E39E0@mac.com> Content-Transfer-Encoding: quoted-printable From: David Leimbach Date: Sun, 13 Jul 2003 13:25:45 -0500 To: "M. Warner Losh" X-Mailer: Apple Mail (2.578) cc: rodrigc@crodrigues.org cc: kabaev@mail.ru cc: freebsd-current@freebsd.org cc: jilles@stack.nl Subject: Re: GCC 3.3.1, new warnings with X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 13 Jul 2003 18:25:58 -0000 On Sunday, July 13, 2003, at 1:11PM, M. Warner Losh wrote: > In message: <20030713152154.GA96653@stack.nl> > Jilles Tjoelker writes: > : The compiler moans about (T)(-1) >=3D 0 as well. Is the assumption = that > : (unsigned type)(-1) is never zero valid? > > yes. There are no known machines where -1 =3D=3D 0 for types of = different > signs. Further, the C standard says that it must behave as if it is a > two's complement machine, and I think that C++ says so too. > I am pretty certain you can do one's compliment in the C99 standard,=20 and that some of that is implementation/platform dependant. See section 6.2.6.2 of the C99 standard which enumerates the following 3 negative number representations: =A1Xthe corresponding value with sign bit 0 is negated (sign and=20 magnitude); =A1Xthe sign bit has the value-(2^N )(two=A1=A6s complement); =A1Xthe sign bit has the value-(2^N -1) (one=A1=A6s complement). further: "Which of these applies is implementation-defined, as is whether the=20 value with sign bit 1 and all value bits zero (for the first two), or=20 with sign bit and all value bits 1 (for one=A1=A6s complement), is a = trap=20 representation or a normal value. Inthe case of sign and magnitude and=20= one=A1=A6scomplement, if this representation is a normal value it is = called=20 a negative zero. " Yes... a negative 0. > Warner > _______________________________________________ > freebsd-current@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to=20 > "freebsd-current-unsubscribe@freebsd.org" From owner-freebsd-current@FreeBSD.ORG Sun Jul 13 11:31:55 2003 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id DBC2B37B401 for ; Sun, 13 Jul 2003 11:31:55 -0700 (PDT) Received: from ns1.xcllnt.net (209-128-86-226.bayarea.net [209.128.86.226]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0C26F43FAF for ; Sun, 13 Jul 2003 11:31:55 -0700 (PDT) (envelope-from marcel@xcllnt.net) Received: from dhcp01.pn.xcllnt.net (dhcp01.pn.xcllnt.net [192.168.4.201]) by ns1.xcllnt.net (8.12.9/8.12.9) with ESMTP id h6DIVpv1085299; Sun, 13 Jul 2003 11:31:51 -0700 (PDT) (envelope-from marcel@piii.pn.xcllnt.net) Received: from dhcp01.pn.xcllnt.net (localhost [127.0.0.1]) by dhcp01.pn.xcllnt.net (8.12.9/8.12.9) with ESMTP id h6DIVpE8078088; Sun, 13 Jul 2003 11:31:51 -0700 (PDT) (envelope-from marcel@dhcp01.pn.xcllnt.net) Received: (from marcel@localhost) by dhcp01.pn.xcllnt.net (8.12.9/8.12.9/Submit) id h6DIVpTZ078087; Sun, 13 Jul 2003 11:31:51 -0700 (PDT) (envelope-from marcel) Date: Sun, 13 Jul 2003 11:31:51 -0700 From: Marcel Moolenaar To: David Leimbach Message-ID: <20030713183151.GA78045@dhcp01.pn.xcllnt.net> References: <20030712155333.GA79322@crodrigues.org> <20030713031312.GA89014@crodrigues.org> <20030713000559.28c18be6.kabaev@mail.ru> <401FAE5E-B535-11D7-BE3B-0003937E39E0@mac.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <401FAE5E-B535-11D7-BE3B-0003937E39E0@mac.com> User-Agent: Mutt/1.5.4i cc: Craig Rodrigues cc: Alexander Kabaev cc: freebsd-current@freebsd.org Subject: Re: GCC 3.3.1, new warnings with X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 13 Jul 2003 18:31:56 -0000 On Sun, Jul 13, 2003 at 08:23:54AM -0500, David Leimbach wrote: > > This is a good policy in general, however, one could easily argue that > what > is trying to be determined with signedness and such being > less-than-compared > to 0 isn't really a big deal and possibly the only way to implement this > numeric_limits::digits thing without any type introspection which > C++ currently > lacks. What about? #define issigned(T) (((T)(0)>(T)(~0)) ? 1 : 0) -- Marcel Moolenaar USPA: A-39004 marcel@xcllnt.net From owner-freebsd-current@FreeBSD.ORG Sun Jul 13 11:36:10 2003 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id CABA937B401 for ; Sun, 13 Jul 2003 11:36:10 -0700 (PDT) Received: from rootlabs.com (root.org [67.118.192.226]) by mx1.FreeBSD.org (Postfix) with SMTP id 4548943FAF for ; Sun, 13 Jul 2003 11:36:10 -0700 (PDT) (envelope-from nate@rootlabs.com) Received: (qmail 14823 invoked by uid 1000); 13 Jul 2003 18:36:11 -0000 Date: Sun, 13 Jul 2003 11:36:11 -0700 (PDT) From: Nate Lawson To: MATOBA Hirozumi In-Reply-To: <20030713.182835.730549724.matoba@st.rim.or.jp> Message-ID: <20030713113407.Q14820@root.org> References: <20030711230155.Q9479@root.org> <20030713.182835.730549724.matoba@st.rim.or.jp> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: acpi-jp@jp.FreeBSD.org cc: current@freebsd.org Subject: Re: [acpi-jp 2415] Re: PATCH - acpi 0619 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 13 Jul 2003 18:36:11 -0000 On Sun, 13 Jul 2003, MATOBA Hirozumi wrote: > On Fri, 11 Jul 2003 23:07:08 -0700, Nate Lawson wrote: > | I've prepared a new diff of the 0619 drop of acpica along with the > | appropriate changes to support code: > | > | * Use ACPI_BUFFER as the type for AcpiGetObjectInfo > | * Remove AcpiEnableEvent/AcpiClearEvent for ACPI_EVENT_FIXED (power/sleep > | buttons) as they are no longer needed > | * Change calls to use the new GPE functions > | * Add AcpiOs*Lock functions > | * Import 0619 + local FreeBSD changes + dsmthdat.c patch (from > | kochi@netbsd.org) > | > | Please test and let me know how this works for you. It works fine on my > | IBM T23. > | > | http://www.root.org/~nate/freebsd/acpi-0619.diff.gz > > I tested this patch on IBM ThinkPad A22e, > but repeated messages > ACPI-0340: *** Error: Could not release ACPI Global Lock, AE_BAD_PARAMETER > appeared again (like as 2-3 weeks ago). > > It seems that the change of from version 1.1.1.16 to 1.1.1.17 > in src/sys/contrib/dev/acpica/hwregs.c > is overwritten by this patch (so partially back to the status of 1.1.1.16). I included all of our local changes but it looks like I didn't catch changes I had made on the vendor branch previously. I'll make sure I've got all those also. I expected the vendor would have made this change but I guess not. I still expect them to do so soon. -Nate From owner-freebsd-current@FreeBSD.ORG Sun Jul 13 11:38:04 2003 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id CC17E37B401 for ; Sun, 13 Jul 2003 11:38:04 -0700 (PDT) Received: from smtpout.mac.com (A17-250-248-89.apple.com [17.250.248.89]) by mx1.FreeBSD.org (Postfix) with ESMTP id 41B5543F93 for ; Sun, 13 Jul 2003 11:38:04 -0700 (PDT) (envelope-from leimy2k@mac.com) Received: from mac.com (smtpin08-en2 [10.13.10.153]) by smtpout.mac.com (Xserve/MantshX 2.0) with ESMTP id h6DIbZ17026487; Sun, 13 Jul 2003 11:37:35 -0700 (PDT) Received: from mac.com (adsl-78-178-166.jan.bellsouth.net [216.78.178.166]) (authenticated bits=0) by mac.com (Xserve/8.12.9/MantshX 2.0) with ESMTP id h6DIPlsr012844; Sun, 13 Jul 2003 11:37:32 -0700 (PDT) In-Reply-To: <20030713.122352.22176834.imp@bsdimp.com> References: <20030713000559.28c18be6.kabaev@mail.ru> <20030713044331.GA89785@crodrigues.org> <20030713152154.GA96653@stack.nl> <20030713.122352.22176834.imp@bsdimp.com> Mime-Version: 1.0 (Apple Message framework v578) Content-Type: text/plain; charset=US-ASCII; format=flowed Message-Id: <1046B4F9-B561-11D7-BE3B-0003937E39E0@mac.com> Content-Transfer-Encoding: 7bit From: David Leimbach Date: Sun, 13 Jul 2003 13:37:32 -0500 To: "M. Warner Losh" X-Mailer: Apple Mail (2.578) cc: rodrigc@crodrigues.org cc: kabaev@mail.ru cc: freebsd-current@freebsd.org cc: jilles@stack.nl Subject: Re: GCC 3.3.1, new warnings with X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 13 Jul 2003 18:38:05 -0000 On Sunday, July 13, 2003, at 1:23PM, M. Warner Losh wrote: > : > 134 #define __glibcpp_signed(T) ((T)(-1) < 0) > : #define __glibcpp_signed(T) (!((T)(-1) > 0)) > > Why not the simpler: > > #define __glibcpp_signed(T) ((T)(-1) <= 0) > > that way we have an overlap on the range of the two types, so we won't > get a warning. We know for a fact that -1 != 0 for all known machine > types (all machines are two's complement, or are required to behave as > if they are two's complement, per the standard). > You keep saying this... where is this "must behave as two's compliment stated?" > (unsigned int) -1 == 0xffffffff (assuming 32-bit int). or with a valid one's compliment C99 compliant system (unsigned int) -1 = 0xfffffffe; > > even on a one's complement's machine, without the standard conversion, > the 'type punning' conversion of -1 would yield 0xfffffffe, which is > still > 0. > Correct :). I still don't think C enforces two's compliment. Dave > Warner > _______________________________________________ > freebsd-current@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to > "freebsd-current-unsubscribe@freebsd.org" From owner-freebsd-current@FreeBSD.ORG Sun Jul 13 11:47:01 2003 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A935337B401 for ; Sun, 13 Jul 2003 11:47:01 -0700 (PDT) Received: from fafoe.narf.at (chello212186121237.14.vie.surfer.at [212.186.121.237]) by mx1.FreeBSD.org (Postfix) with ESMTP id BD17143F85 for ; Sun, 13 Jul 2003 11:47:00 -0700 (PDT) (envelope-from stefan@fafoe.narf.at) Received: from wombat.fafoe.narf.at (wombat.fafoe.narf.at [192.168.2.102]) by fafoe.narf.at (Postfix) with ESMTP id EFEF93FA8; Sun, 13 Jul 2003 20:46:54 +0200 (CEST) Received: by wombat.fafoe.narf.at (Postfix, from userid 1001) id 16F005E; Sun, 13 Jul 2003 20:46:51 +0200 (CEST) Date: Sun, 13 Jul 2003 20:46:51 +0200 From: Stefan Farfeleder To: David Leimbach Message-ID: <20030713184651.GB586@wombat.fafoe.narf.at> References: <20030713000559.28c18be6.kabaev@mail.ru> <20030713044331.GA89785@crodrigues.org> <20030713152154.GA96653@stack.nl> <20030713.121125.54936166.imp@bsdimp.com> <6B36552C-B55F-11D7-BE3B-0003937E39E0@mac.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <6B36552C-B55F-11D7-BE3B-0003937E39E0@mac.com> User-Agent: Mutt/1.5.4i cc: freebsd-current@freebsd.org Subject: Re: GCC 3.3.1, new warnings with X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 13 Jul 2003 18:47:01 -0000 On Sun, Jul 13, 2003 at 01:25:45PM -0500, David Leimbach wrote: > > On Sunday, July 13, 2003, at 1:11PM, M. Warner Losh wrote: > > >In message: <20030713152154.GA96653@stack.nl> > > Jilles Tjoelker writes: > >: The compiler moans about (T)(-1) >= 0 as well. Is the assumption that > >: (unsigned type)(-1) is never zero valid? > > > >yes. There are no known machines where -1 == 0 for types of different > >signs. Further, the C standard says that it must behave as if it is a > >two's complement machine, and I think that C++ says so too. > > > > I am pretty certain you can do one's compliment in the C99 standard, > and that > some of that is implementation/platform dependant. You seem to be confused. While signed integers certainly can use the one's complement representation, the conversion of an negative value to an unsigned type is a different matter. The relevant quote from C99 is: 6.3.1.3 Signed and unsigned integers 2 Otherwise, if the new type is unsigned, the value is converted by repeatedly adding or subtracting one more than the maximum value that can be represented in the new type until the value is in the range of the new type.49) Regards, Stefan Farfeleder From owner-freebsd-current@FreeBSD.ORG Sun Jul 13 12:01:36 2003 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: by hub.freebsd.org (Postfix, from userid 618) id D8A4A37B401; Sun, 13 Jul 2003 12:01:35 -0700 (PDT) To: freebsd-net@FreeBSD.ORG, freebsd-mobile@FreeBSD.ORG, freebsd-current@FreeBSD.ORG Date: Sun, 13 Jul 2003 12:01:35 -0700 (PDT) X-Mailer: ELM [version 2.4ME+ PL54 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Message-Id: <20030713190135.D8A4A37B401@hub.freebsd.org> From: wpaul@FreeBSD.ORG (Bill Paul) Subject: Call for testers: Broadcom 5705 gigabit ethernet X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 13 Jul 2003 19:01:36 -0000 While I still don't have any documentation for the BCM5705, I recently obtained a Broadcom driver with 5705 support. After scrutinizing it carefully, it looks like the differences between it and its predecessors are: - No jumbo frame support - RX return ring is limited in size to 512 entries - No support for DMA'ed statistics block (stats must be read from registers instead) - Initialization of certain on-chip blocks and parameters are skipped - 5705 rev A0 has a bug that requires a workaround: the driver has to poll the NIC's memory after setting up the RX descriptor ring to verify the chip has actually loaded it. I have merged all these changes into a copy of the bge(4) driver from -current (should also work with 5.1-RELEASE). You can get it from: http://www.freebsd.org/~wpaul/Broadcom/5705 To use it, just drop the supplied if_bge.c and if_bgereg.h files into /sys/dev/bge and recompile your kernel and/or if_bge.ko module. Unfortunately, I don't have a machine with a 5705 chip in it, so I need other people to help me test these changes. If you have avilable right now: - a laptop or other box with a 5705 gigE chip - FreeBSD 5.1-RELEASE or -CURRENT - another network interface that you can use to load this driver Then please test this updated driver for me and report back. Information that I would like to see: - Describe the system with the 5705 chip in it (I'm under the impression the 5705 is being used in embedded configurations only) - A copy of dmesg output showing the ASIC revision of your chip (doesn't have to be a verbose boot, though I won't mind if it is) - A detailed description of any problems you may observe while testing the driver Information I don't want to see: - Requests for help with other totally unrelated drivers - Requests for help transfering large sums of money out of Nigeria - Information about septic tank clealing - Pictures of people getting it on with barnyard animals - Bikeshed arguments Thanks in advance for any help anyone is able to provide. -Bill -- ============================================================================= -Bill Paul (510) 749-2329 | Senior Engineer, Master of Unix-Fu wpaul@windriver.com | Wind River Systems ============================================================================= "If stupidity were a handicap, you'd have the best parking spot." ============================================================================= From owner-freebsd-current@FreeBSD.ORG Sun Jul 13 12:07:25 2003 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 8A48237B401 for ; Sun, 13 Jul 2003 12:07:25 -0700 (PDT) Received: from falcon.midgard.homeip.net (h76n3fls20o913.bredband.comhem.se [213.67.148.76]) by mx1.FreeBSD.org (Postfix) with SMTP id 32D5E43F75 for ; Sun, 13 Jul 2003 12:07:23 -0700 (PDT) (envelope-from ertr1013@student.uu.se) Received: (qmail 17341 invoked by uid 1001); 13 Jul 2003 19:07:20 -0000 Date: Sun, 13 Jul 2003 21:07:20 +0200 From: Erik Trulsson To: David Leimbach Message-ID: <20030713190720.GA17305@falcon.midgard.homeip.net> Mail-Followup-To: David Leimbach , "M. Warner Losh" , rodrigc@crodrigues.org, kabaev@mail.ru, freebsd-current@freebsd.org, jilles@stack.nl References: <20030713000559.28c18be6.kabaev@mail.ru> <20030713044331.GA89785@crodrigues.org> <20030713152154.GA96653@stack.nl> <20030713.122352.22176834.imp@bsdimp.com> <1046B4F9-B561-11D7-BE3B-0003937E39E0@mac.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1046B4F9-B561-11D7-BE3B-0003937E39E0@mac.com> User-Agent: Mutt/1.5.4i cc: rodrigc@crodrigues.org cc: kabaev@mail.ru cc: freebsd-current@freebsd.org cc: jilles@stack.nl cc: "M. Warner Losh" Subject: Re: GCC 3.3.1, new warnings with X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 13 Jul 2003 19:07:25 -0000 On Sun, Jul 13, 2003 at 01:37:32PM -0500, David Leimbach wrote: > > On Sunday, July 13, 2003, at 1:23PM, M. Warner Losh wrote: > > >: > 134 #define __glibcpp_signed(T) ((T)(-1) < 0) > >: #define __glibcpp_signed(T) (!((T)(-1) > 0)) > > > >Why not the simpler: > > > >#define __glibcpp_signed(T) ((T)(-1) <= 0) > > > >that way we have an overlap on the range of the two types, so we won't > >get a warning. We know for a fact that -1 != 0 for all known machine > >types (all machines are two's complement, or are required to behave as > >if they are two's complement, per the standard). > > > > You keep saying this... where is this "must behave as two's compliment > stated?" > > > >(unsigned int) -1 == 0xffffffff (assuming 32-bit int). > > or with a valid one's compliment C99 compliant system > (unsigned int) -1 = 0xfffffffe; Only if UINT_MAX happens to be0xfffffffe, which it probablky won't be. For all C99 compliant systems you have that: (unsigned int) -1 == UINT_MAX > > > > >even on a one's complement's machine, without the standard conversion, > >the 'type punning' conversion of -1 would yield 0xfffffffe, which is > >still > 0. > > > Correct :). I still don't think C enforces two's compliment. C doesn't require two's compliment, but it encourages it. If you take a signed value and convert it to the corresponding unsigned type , the result must be equal modulo 2^N to the original value (where N is the number of bits in the unsigned type. (Ignoring any padding bits.)) (Actually it is modulo a value one greater than the largest value representable by the unsigned type, but this amounts to the same thing.) This means that -1 converted to an unsigned type will always be the largest number representable by that unsigned type. This is true regardless of how negative numbers are represented. For two's complement there is no need to change the representation when converting signed to unsigned values, while this can be needed when using sign-magnitude or one's-complement. And to answer the original question: It is valid to assume that -1 converted to an unsigned integer type will never be equal to 0. -- Erik Trulsson ertr1013@student.uu.se From owner-freebsd-current@FreeBSD.ORG Sun Jul 13 12:24:38 2003 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9DFE737B401 for ; Sun, 13 Jul 2003 12:24:38 -0700 (PDT) Received: from mail.soaustin.net (mail.soaustin.net [207.200.4.66]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1200F43FB1 for ; Sun, 13 Jul 2003 12:24:38 -0700 (PDT) (envelope-from linimon@lonesome.com) Received: from lonesome.lonesome.com (cs242746-11.austin.rr.com [24.27.46.11]) (using TLSv1 with cipher RC4-MD5 (128/128 bits)) (No client certificate requested) by mail.soaustin.net (Postfix) with ESMTP id D723814179; Sun, 13 Jul 2003 14:24:36 -0500 (CDT) From: Mark Linimon Organization: Lonesome Dove Computing Services To: Mark Kettenis , marcel@xcllnt.net Date: Sun, 13 Jul 2003 14:28:08 -0500 User-Agent: KMail/1.5.2 References: <20030711225002.GA71126@ns1.xcllnt.net> <20030712203930.GA5446@dhcp01.pn.xcllnt.net> <200307131557.h6DFvYRD098297@elgar.kettenis.dyndns.org> In-Reply-To: <200307131557.h6DFvYRD098297@elgar.kettenis.dyndns.org> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200307131428.08195.linimon@lonesome.com> cc: current@FreeBSD.org Subject: Re: GDB - do we dare? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 13 Jul 2003 19:24:38 -0000 > FSF GDB releases use a libbfd that's basically a > snapshot taken at the point where the release branch was cut. Hmm, seems like a motivation for a libbfd port that tracks the snapshot, for this very reason. mcl From owner-freebsd-current@FreeBSD.ORG Sun Jul 13 12:29:17 2003 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id EA4FF37B401 for ; Sun, 13 Jul 2003 12:29:17 -0700 (PDT) Received: from postal3.es.net (postal3.es.net [198.128.3.207]) by mx1.FreeBSD.org (Postfix) with ESMTP id D60DA43F85 for ; Sun, 13 Jul 2003 12:29:16 -0700 (PDT) (envelope-from oberman@es.net) Received: from ptavv.es.net ([198.128.4.29]) by postal3.es.net (Postal Node 3) with ESMTP (SSL) id MUA74016; Sun, 13 Jul 2003 12:29:15 -0700 Received: from ptavv (localhost [127.0.0.1]) by ptavv.es.net (Tachyon Server) with ESMTP id 37E8C5D08; Sun, 13 Jul 2003 12:29:14 -0700 (PDT) X-Mailer: exmh version 2.6.3 04/04/2003 with nmh-1.0.4 To: Nate Lawson In-Reply-To: Message from Nate Lawson of "Fri, 11 Jul 2003 23:07:08 PDT." <20030711230155.Q9479@root.org> Mime-Version: 1.0 Content-Type: multipart/mixed ; boundary="==_Exmh_14599644730" Date: Sun, 13 Jul 2003 12:29:14 -0700 From: "Kevin Oberman" Message-Id: <20030713192914.37E8C5D08@ptavv.es.net> cc: acpi-jp@jp.freebsd.org cc: current@freebsd.org Subject: Re: PATCH - acpi 0619 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 13 Jul 2003 19:29:18 -0000 This is a multipart MIME message. --==_Exmh_14599644730 Content-Type: text/plain; charset=us-ascii > Date: Fri, 11 Jul 2003 23:07:08 -0700 (PDT) > From: Nate Lawson > Sender: owner-freebsd-current@freebsd.org > > I've prepared a new diff of the 0619 drop of acpica along with the > appropriate changes to support code: > > * Use ACPI_BUFFER as the type for AcpiGetObjectInfo > * Remove AcpiEnableEvent/AcpiClearEvent for ACPI_EVENT_FIXED (power/sleep > buttons) as they are no longer needed > * Change calls to use the new GPE functions > * Add AcpiOs*Lock functions > * Import 0619 + local FreeBSD changes + dsmthdat.c patch (from > kochi@netbsd.org) > > Please test and let me know how this works for you. It works fine on my > IBM T23. > > http://www.root.org/~nate/freebsd/acpi-0619.diff.gz OK. I installed the patches on my T30 and saw no clear regressions, although I'd like to do more testing. I did get many more errors at boot time, all early in the operation. messages attached. Also, after patching, I tried building world and it would not work due to undefined symbols in the boot/i386/libi386 build. I have put the errors into the attachment at the top. Observed problems: USB does not recover from suspend. Display back-light say on after suspend. (Neither of these is different from the CURRENT code. Another issue that I recently noted after a complaint that battery life was worse with FreeBSD than with Linux or Windows. I have noted that the CPU does not seem to slow even though the system claims that it is reduced to 50% in economy mode. Instead, the CPU always seems to run at 1.8 GHz if it was on AC at power-up and 1.2 GHz if the system was on battery at power-up. THIS IS EXACTLY THE SAME THING I SEE WITH APM! So it's not a regression, but somehow something is simply not right here. And it now appears that the problem is not specific to T30s or even IBMs as the other report was not an IBM, but a Compaq. I plan to do further testing of this to confirm some details. Since I could not build a new world with the patch in place, I have backed it out for now. -- R. Kevin Oberman, Network Engineer Energy Sciences Network (ESnet) Ernest O. Lawrence Berkeley National Laboratory (Berkeley Lab) E-mail: oberman@es.net Phone: +1 510 486-8634 --==_Exmh_14599644730 Content-Type: text/plain ; name="acpi-info.txt"; charset=us-ascii Content-Description: acpi-info.txt Content-Disposition: attachment; filename="acpi-info.txt" ===> sys/boot/i386/libi386 cc -O -pipe -mcpu=pentiumpro -ffreestanding -DCOMPORT=0x3f8 -DCOMSPEED=9600 -DTERM_EMU -I/usr/src/sys/boot/i386/libi386/../../common -I/usr/src/sys/boot/i386/libi386/../btx/lib -I/usr/src/sys/boot/i386/libi386/../../../contrib/dev/acpica -I/usr/src/sys/boot/i386/libi386/../../.. -I. -I/usr/src/sys/boot/i386/libi386/../../../../lib/libstand/ -ffreestanding -mpreferred-stack-boundary=2 -c /usr/src/sys/boot/i386/libi386/biosacpi.c In file included from /usr/src/sys/boot/i386/libi386/biosacpi.c:35: /usr/src/sys/contrib/dev/acpica/actypes.h:922: error: `ACPI_DEVICE_ID_LENGTH' undeclared here (not in a function) /usr/src/sys/contrib/dev/acpica/actypes.h:930: error: `ACPI_MAX_CID_LENGTH' undeclared here (not in a function) *** Error code 1 Jul 13 05:31:24 puppeteer syslogd: kernel boot file is /boot/kernel/kernel Copyright (c) 1992-2003 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD 5.1-CURRENT #6: Sat Jul 12 22:02:26 PDT 2003 oberman@puppeteer.es.net:/usr/obj/usr/src/sys/IBM-T30-D Preloaded elf kernel "/boot/kernel/kernel" at 0xc054c000. Preloaded userconfig_script "/boot/kernel.conf" at 0xc054c26c. Preloaded elf module "/boot/kernel/acpi.ko" at 0xc054c2bc. Timecounter "i8254" frequency 1193182 Hz Timecounter "TSC" frequency 1798479836 Hz CPU: Intel(R) Pentium(R) 4 Mobile CPU 1.80GHz (1798.48-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0xf24 Stepping = 4 Features=0x3febf9ff real memory = 536281088 (511 MB) avail memory = 515014656 (491 MB) Pentium Pro MTRR support enabled npx0: on motherboard npx0: INT 16 interface acpi0: on motherboard pcibios: BIOS version 2.10 Using $PIR table, 14 entries at 0xc00fdeb0 ACPI-1287: *** Error: Method execution failed [\_SB_.PCI0.LPC_.FDC_._INI] (Node 0xc405d3e0), AE_NOT_EXIST ACPI-1287: *** Error: Method execution failed [\_SB_.PCI0.LPC_.EC__._INI] (Node 0xc4056860), AE_NOT_EXIST ACPI-1287: *** Error: Method execution failed [\_SB_.PCI0.LPC_.EC__.BAT0._STA] (Node 0xc405a0c0), AE_NOT_EXIST ACPI-0175: *** Error: Method execution failed [\_SB_.PCI0.LPC_.EC__.BAT0._STA] (Node 0xc405a0c0), AE_NOT_EXIST ACPI-1287: *** Error: Method execution failed [\_SB_.PCI0.LPC_.EC__.BAT1._STA] (Node 0xc4059ea0), AE_NOT_EXIST ACPI-0175: *** Error: Method execution failed [\_SB_.PCI0.LPC_.EC__.BAT1._STA] (Node 0xc4059ea0), AE_NOT_EXIST ACPI-1287: *** Error: Method execution failed [\_SB_.PCI0.LPC_.EC__.BGID] (Node 0xc405d520), AE_NOT_EXIST ACPI-1287: *** Error: Method execution failed [\_SB_.PCI0.LPC_.EC__.BINI] (Node 0xc405d540), AE_NOT_EXIST ACPI-1287: *** Error: Method execution failed [\_SB_.PCI0.LPC_.EC__.BSTA] (Node 0xc405d580), AE_NOT_EXIST ACPI-1287: *** Error: Method execution failed [\_SB_.PCI0.IDE0.SCND.MSTR._STA] (Node 0xc405d440), AE_NOT_EXIST ACPI-0175: *** Error: Method execution failed [\_SB_.PCI0.IDE0.SCND.MSTR._STA] (Node 0xc405d440), AE_NOT_EXIST ACPI-1287: *** Error: Method execution failed [\_SB_.PCI0.LPC_.EC__.BGID] (Node 0xc405d520), AE_NOT_EXIST ACPI-1287: *** Error: Method execution failed [\_SB_.PCI0.LPC_.EC__.BINI] (Node 0xc405d540), AE_NOT_EXIST ACPI-1287: *** Error: Method execution failed [\_SB_.PCI0.LPC_.EC__.BSTA] (Node 0xc405d580), AE_NOT_EXIST ACPI-1287: *** Error: Method execution failed [\_SB_.PCI0.USB0.URTH.UNST._STA] (Node 0xc405da60), AE_NOT_EXIST ACPI-0175: *** Error: Method execution failed [\_SB_.PCI0.USB0.URTH.UNST._STA] (Node 0xc405da60), AE_NOT_EXIST acpi0: power button is handled as a fixed feature programming model. Timecounter "ACPI-fast" frequency 3579545 Hz ACPI-1287: *** Error: Method execution failed [\_SB_.PCI0.LPC_.EC__.BAT0._STA] (Node 0xc405a0c0), AE_NOT_EXIST ACPI-0175: *** Error: Method execution failed [\_SB_.PCI0.LPC_.EC__.BAT0._STA] (Node 0xc405a0c0), AE_NOT_EXIST ACPI-1287: *** Error: Method execution failed [\_SB_.PCI0.LPC_.EC__.BAT1._STA] (Node 0xc4059ea0), AE_NOT_EXIST ACPI-0175: *** Error: Method execution failed [\_SB_.PCI0.LPC_.EC__.BAT1._STA] (Node 0xc4059ea0), AE_NOT_EXIST ACPI-1287: *** Error: Method execution failed [\_SB_.PCI0.LPC_.EC__.BGID] (Node 0xc405d520), AE_NOT_EXIST ACPI-1287: *** Error: Method execution failed [\_SB_.PCI0.LPC_.EC__.BINI] (Node 0xc405d540), AE_NOT_EXIST ACPI-1287: *** Error: Method execution failed [\_SB_.PCI0.LPC_.EC__.BSTA] (Node 0xc405d580), AE_NOT_EXIST ACPI-1287: *** Error: Method execution failed [\_SB_.PCI0.IDE0.SCND.MSTR._STA] (Node 0xc405d440), AE_NOT_EXIST ACPI-0175: *** Error: Method execution failed [\_SB_.PCI0.IDE0.SCND.MSTR._STA] (Node 0xc405d440), AE_NOT_EXIST ACPI-1287: *** Error: Method execution failed [\_SB_.PCI0.LPC_.EC__.BGID] (Node 0xc405d520), AE_NOT_EXIST ACPI-1287: *** Error: Method execution failed [\_SB_.PCI0.LPC_.EC__.BINI] (Node 0xc405d540), AE_NOT_EXIST ACPI-1287: *** Error: Method execution failed [\_SB_.PCI0.LPC_.EC__.BSTA] (Node 0xc405d580), AE_NOT_EXIST ACPI-1287: *** Error: Method execution failed [\_SB_.PCI0.USB0.URTH.UNST._STA] (Node 0xc405da60), AE_NOT_EXIST ACPI-0175: *** Error: Method execution failed [\_SB_.PCI0.USB0.URTH.UNST._STA] (Node 0xc405da60), AE_NOT_EXIST acpi_timer0: <24-bit timer at 3.579545MHz> port 0x1008-0x100b on acpi0 acpi_cpu0: port 0x530-0x537 on acpi0 acpi_tz0: port 0x530-0x537 on acpi0 acpi_lid0: on acpi0 ACPI-1287: *** Error: Method execution failed [\_SB_.LID_._PSW] (Node 0xc15213a0), AE_NOT_EXIST acpi_button0: on acpi0 ACPI-1287: *** Error: Method execution failed [\_SB_.SLPB._PSW] (Node 0xc1521320), AE_NOT_EXIST pcib0: port 0xcf8-0xcff on acpi0 pci0: on pcib0 pcib0: slot 29 INTA is routed to irq 11 pcib0: slot 29 INTB is routed to irq 11 pcib0: slot 29 INTC is routed to irq 11 pcib0: slot 31 INTB is routed to irq 11 Jul 13 05:31:24 puppeteer last message repeated 2 times agp0: mem 0xe0000000-0xe3ffffff at device 0.0 on pci0 pcib1: at device 1.0 on pci0 pci1: on pcib1 pcib1: slot 0 INTA is routed to irq 11 pci1: at device 0.0 (no driver attached) uhci0: port 0x1800-0x181f irq 11 at device 29.0 on pci0 usb0: on uhci0 usb0: USB revision 1.0 uhub0: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub0: 2 ports with 2 removable, self powered uhci1: port 0x1820-0x183f irq 11 at device 29.1 on pci0 usb1: on uhci1 usb1: USB revision 1.0 uhub1: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub1: 2 ports with 2 removable, self powered uhci2: port 0x1840-0x185f irq 11 at device 29.2 on pci0 usb2: on uhci2 usb2: USB revision 1.0 uhub2: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub2: 2 ports with 2 removable, self powered pcib2: at device 30.0 on pci0 pci2: on pcib2 pcib2: slot 0 INTA is routed to irq 11 pcib2: slot 0 INTB is routed to irq 11 pcib2: slot 2 INTA is routed to irq 11 pcib2: slot 8 INTA is routed to irq 11 cbb0: mem 0x50000000-0x50000fff irq 11 at device 0.0 on pci2 start (50000000) < sc->membase (d0200000) start (50000000) < sc->pmembase (f0000000) cardbus0: on cbb0 pccard0: <16-bit PCCard bus> on cbb0 cbb1: mem 0x51000000-0x51000fff irq 11 at device 0.1 on pci2 start (51000000) < sc->membase (d0200000) start (51000000) < sc->pmembase (f0000000) cardbus1: on cbb1 pccard1: <16-bit PCCard bus> on cbb1 pci2: at device 2.0 (no driver attached) fxp0: port 0x8000-0x803f mem 0xd0200000-0xd0200fff irq 11 at device 8.0 on pci2 fxp0: Ethernet address 00:09:6b:50:36:29 miibus0: on fxp0 inphy0: on miibus0 inphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto isab0: at device 31.0 on pci0Jul 13 05:31:24 puppeteer kernel: isa0: on isab0 atapci0: port 0x1860-0x186f,0x374-0x377,0x170-0x177,0x3f4-0x3f7,0x1f0-0x1f7 at device 31.1 on pci0 ata0: at 0x1f0 irq 14 on atapci0 ata1: at 0x170 irq 15 on atapci0 ichsmb0: port 0x1880-0x189f irq 11 at device 31.3 on pci0 smbus0: on ichsmb0 smb0: on smbus0 pcm0: port 0x18c0-0x18ff,0x1c00-0x1cff irq 11 at device 31.5 on pci0 pcm0: pci0: at device 31.6 (no driver attached) atkbdc0: port 0x64,0x60 irq 1 on acpi0 atkbd0: flags 0x1 irq 1 on atkbdc0 kbd0 at atkbd0 psm0: flags 0x2000 irq 12 on atkbdc0 psm0: model Generic PS/2 mouse, device ID 0 fdc0: port 0x3f7,0x3f0-0x3f5 irq 6 drq 2 on acpi0 fdc0: FIFO enabled, 8 bytes threshold fd0: <1440-KB 3.5" drive> on fdc0 drive 0 sio0 port 0x3f8-0x3ff irq 4 on acpi0 sio0: type 16550A sio1: configured irq 3 not in bitmap of probed irqs 0 sio1: port may not be enabled acpi_ec0: port 0x66,0x62 on acpi0 acpi_ec0: GPE bit is 0x1c, not using global lock acpi_cmbat0: on acpi0Jul 13 05:31:24 puppeteer kernel: acpi_cmbat1: on acpi0Jul 13 05:31:24 puppeteer kernel: acpi_acad0: on acpi0 sio1: configured irq 3 not in bitmap of probed irqs 0 sio1: port may not be enabled orm0: