Re: 5.0 release schedule?

2002-09-02 Thread Murray Stokely

On Wed, Aug 28, 2002 at 09:08:32AM -0400, Rod Smith wrote:
 According to the timetable at
 http://www.freebsd.org/releases/5.0R/schedule.html, DP2 for FreeBSD 5.0

  I've updated that timetable to remove the specific date (it may take
up to 24 hours for the website to be updated).  We're actively working
on it and I expect a stable DP2 release in the month of September.

   - Murray

To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message



Re: 5.0 release schedule?

2002-09-02 Thread Murray Stokely

On Thu, Aug 29, 2002 at 01:41:41PM -0700, David O'Brien wrote:
 A 5.0 DP2 branch was created just yesterday.  So how ever good
 yesterday's -current was will affect DP2.  I rather expected the release
 engineers to at least querry the lists to ask what the known issues are
 before picking which code to base DP2 on.

  We plan to keep the DP2 branch in Perforce in sync with -CURRENT for
a while until things stabilize a bit more.  That wasn't a branch point
per se, just the initial integrate to populate the branch so we can
begin tweaking the documentation and such.  DP2 will certainly not be
based on yesterday's -CURRENT, it was too problematic and doesn't
contain the new GCC bits.

  - Murray

To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message



sparc64 tinderbox failure

2002-09-02 Thread Dag-Erling Smorgrav

--
 Rebuilding the temporary build tree
--
 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
--
=== gnu/usr.bin/cc/cc1plus
method.o: In function `use_thunk':
method.o(.text+0x90c): undefined reference to `sparc_output_mi_thunk'
*** Error code 1

Stop in /usr/home/des/tinderbox/sparc64/src/gnu/usr.bin/cc/cc1plus.
*** Error code 1

Stop in /usr/home/des/tinderbox/sparc64/src/gnu/usr.bin/cc.
*** Error code 1

Stop in /usr/home/des/tinderbox/sparc64/src.
*** Error code 1

Stop in /usr/home/des/tinderbox/sparc64/src.
*** Error code 1

Stop in /usr/home/des/tinderbox/sparc64/src.

To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message



Re: [bde@zeta.org.au: Re: Page faults from bento cluster (Re: Problemsreading vmcores)]

2002-09-02 Thread Jeff Roberson



  As near as I can tell the panic is happening in VOP_GETATTR().  It looks
  to me like it would be possible for the vnode to be recycled between the
  time when it passes the vp-v_mount test at the top of the loop and the
  time when vn_lock() succeeds.  Shouldn't we bump the vnode reference
  count by calling vref() at the top of the loop and add the appropriate
  calls to vrele()?

 Rev.1.395 made some changes that I didn't like much here.  The
 VOP_GETATTR() is now done unconditionally.  This pessimizes vflush()
 and enlarges any race windows.  I think WRITECLOSE is only used for
 mount -u from rw to ro, so the pessimization exercises code that was
 rarely used before.

 Rev.1.394 called VOP_GETATTR() with the interlock held.  This was wrong
 but probably reduced race windows.  The window seems to have been
 opened before rev.1.394 by releasing mntvnode_slock before aquiring
 the interlock.  RELENG_4 doesn't release mntvnode_slock at that point
 (it holds both locks across the VOP_GETATTR()).

 Bruce



I have patches that fix the locking behavior in vflush() in my current VFS
smp patch.  It's not quite complete but it has most of struct vnode locked
down.  The patch even moves the getattr back into the conditional path.
This may fix the behavior here.

Again, this is more than vflush, but I didn't want to seperate that out
and test it before going to bed.  If this fixes the problem I can commit
the relavent part of this patch soon.

http://www.chesapeake.net/~jroberson/VFSsmp.patch


Cheers,
Jeff


To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message



Re: aout support broken in gcc3

2002-09-02 Thread Jake Burkholder

Apparently, On Mon, Sep 02, 2002 at 02:24:08PM +1000,
Bruce Evans said words to the effect of;

 aout support is still required for a few things (mainly for compiling
 some boot blocks), but is broken in gcc3 for at least compile-time

Which boot blocks?

 assignments to long longs and shifts of long longs by a non-constant
 amount:
 
 %%%
 $ cat z.c
 long long x = 0;
 int y;
 
 foo()
 {
   x = x  y;
 }
 $ cc -O -S -aout z.c
 $ cat z.s
   .file   z.c
 .globl _x
   .data
   .p2align 3
   .type   _x,@object
   .size   _x,8
 _x:
   .quad   0
   .text
   .p2align 2,0x90
 .globl _foo
   .type   _foo,@function
 _foo:
   pushl   %ebp
   movl%esp, %ebp
   movb_y, %cl
   movl_x, %eax
   movl_x+4, %edx
   shldl   %eax, %edx
   sall%cl, %eax
   testl   $32, %ecx
   je  L2
   movl%eax, %edx
   movl$0, %eax
 L2:
   movl%eax, _x
   movl%edx, _x+4
   leave
   ret
 Lfe1:
   .size   _foo,Lfe1-_foo
   .comm_y,4
   .ident  GCC: (GNU) 3.1 [FreeBSD] 20020509 (prerelease)
 %%%
 
 The above assembler output has two syntax errors:
 - .quad 0.  .quad is not supported by the old aout assembler.
 - shldl %eax, %edx.  The old aout assembler only accepts the correct
   syntax of shldl %cl,%eax,%edx.  Note that gcc doesn't elide the
   similarly implicit %cl register for the sall instruction.
 
 Bruce
 
 
 To Unsubscribe: send mail to [EMAIL PROTECTED]
 with unsubscribe freebsd-current in the body of the message

To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message



Re: gcc 3.1 / streambuf.h broken with using namespace std;

2002-09-02 Thread Lamont Granquist



On Sun, 1 Sep 2002, David O'Brien wrote:
 On Sun, Sep 01, 2002 at 12:37:14PM -0700, Lamont Granquist wrote:
  It sounds like gcc-3.1 or gcc-3.2 will be archaic and buggy
  by the time that 5.2 and 5.3 come out.

 How would gcc-3.2 get more buggy over time than it is today??

I said it was buggy.  Do you mean to imply that gcc-3.2 doesn't have a
single bug in it?

Admittedly I should have said unmaintained though -- point being that
the bugs in it wouldn't be getting fixed by gcc developers who would
rather fix them in 3.3...

 archaic does apply however.

 Why the fsck can't people come up to speed on an issue before spewing
 FUD?

I fail to see why assuming that a software project the size of the gcc
compiler has a few bugs is FUD...


To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message



CPU slowdown using ACPI on a Toshiba Portege 7220cte

2002-09-02 Thread Ted Lindgreen


Some experiences with ACPI and APM on a Toshiba Portege 7220cte.
Interesting is the extreme CPU slow-down after suspend/resume
using ACPI.

Running current, (cvsup-ed Aug. 30).  A fixed-up ASL (similar to
the Tecra8200.asl diff from Mitsuru IWASAKI) is used with
acpi_dsdt_load=YES in /boot/loader.conf.  I have device apm in
the kernelconfig, so that I can easily switch between APM and ACPI
with hint.acpi.0.disable=1/0 in /boot/loader.conf.

With ACPI:

- At first everything seems to work allright, screen darkening,
  suspend/resume, batterie state, etc.
- However, it turns out that after a suspend/resume the system
  runs extremely slow: xengine, normally at 1800-1900 RPM,
  drops to 100-150 RPM. Sofar, I've only been able to restore
  the normal performance by rebooting.
- Connecting/removing power produces a kernel-logmessage:
system power profile changed to performance/economy
  but does not seem to have any other effect.
- Using Fn-F2, which normally switches between 3 power-states
  (low, user-setting, and high) does not work. The other Fn-Fx
  functions do work.
- A minor problem is that X-screen darkening does not switch
  off the backlight, whether or not DPMS is specified in the
  XF86Config. (Using Fn-F1 does turn off the backlight, so
  that's a fine workaround).
- I have used the standard and the fixed-up ASL, but I have seen
  no difference besides kernel logmessages like:
   ACPI: DSDT was overridden.

Using APM:
- Suspending in X freezes the system. I've not found any way
  out of that, other than hard resetting the system.
- Suspending in a vty-screen does works. So, having vidcontrol
  in rc.suspend/rc.resume makes suspend/resume work fine.
- There is no slowdown after suspend/resume.
- In contrast to ACPI above, the Fn-F2 works fine. In high-power
  mode xengine runs at 1800-1900 RPM, in low-power mode it slows
  down to 800-900 RPM. In user-setting it depend on what is set, but
  I have not been able to reproduce the extreme slow-down as when
  running ACPI.
- Like ACPI above, connecting/removing power produces a logmessage,
  but nothing else.
- Like ACPI above, X-screen darkening does not switch off the
  backlight, whether or not DPMS is specified.
- The apm command produces somewhat different output running
  APM, than running ACPI: with APM it shows the APM capabilities,
  with ACPI it says unknown. And when running on external power,
  onder APM it shows battery status and remaining time, while
  under ACPI this is unknown. However, when running on
  battery-power, status and life work both under APM and ACPI.

If I can do any other tests or try out anything, please ask.

Regards,
-- ted

To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message



Re: CPU slowdown using ACPI on a Toshiba Portege 7220cte

2002-09-02 Thread David Malone

On Mon, Sep 02, 2002 at 11:52:20AM +0200, Ted Lindgreen wrote:
 - Suspending in X freezes the system. I've not found any way
   out of that, other than hard resetting the system.

Could you try running acpidump before and after running X?  On my
machine the ACPI tables vanish when you run X 'cos the MTRR values
somehow control the mapping of the ACPI tables. You'll know if
you're having this problem 'cos you'll see:

acpidump: Can't find ACPI information

after starting X. (I'd guess this mainly aplies to Athlon systems.)

David.

To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message



Re: CURRENT's termcap broken

2002-09-02 Thread Vladimir B.

÷ Sat, 31.08.2002, × 02:04, Jens Schweikhardt ÎÁÐÉÓÁÌ:
 On Thu, Aug 29, 2002 at 05:03:17PM +0400, Vladimir B.  Grebenschikov wrote:
 # ? Wed, 28.08.2002, ? 23:46, Bruce A. Mah ???:
 #  If memory serves me right, Jens Schweikhardt wrote:
 #  
 #   # Do you have time to commit mention of it to UPDATING?  If so, please
 #   # draw Bruce Mah's attention to the delta so that he can steal your text
 #   # for use in the release notes.  If not, I'll get around to it eventually.
 #   # :-)
 #   
 #   I just added a note to src/UPDATING. Bruce, are you listening
 #   for the release notes?
 #   
 #   20020827:
 #  Our /etc/termcap now has all the entries from the XFree86 xterm
 #  almost unchanged. This means xterm now supports color by default.
 #  If you used TERM=xterm-color in the past you now should use
 #  TERM=xterm. (xterm-color will lead to benign warnings).
 #  
 # 
 # After this update, xterm-color produce warnings:
 # vbook:/home/vova 129_ mc
 # TERMCAP, line 0, terminal 'xterm-color': enter_alt_charset_mode but no
 # acs_chars
 # TERMCAP, line 0, terminal 'xterm-color': exit_alt_charset_mode but no
 # acs_chars
 # 
 # and midnight commander shows all with -, +, | instead of
 # pesudo-graphics.
 
 It seems this is the price we pay for alignment with what XFree86 ships.

I see

 # Ok I have tried setenv TERM xterm, midnight commander now black and
 # white, where I have mistaken ?
 
 I just installed the misc/mc package from 4.6 and midc is fully colored
 under xterm, rxvt and the console. Do you have a stale termcap.db?
 Does midc use/read some config file that says no color?

No, after restarting xterm all works fine, my fault sorry.
Thanx anyway. 

 Regards,
 
   Jens
 -- 
 Jens Schweikhardt http://www.schweikhardt.net/
 SIGSIG -- signature too long (core dumped)
-- 
Vladimir B. Grebenschikov
[EMAIL PROTECTED], SWsoft, Inc.

To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message



Re: CURRENT's termcap broken

2002-09-02 Thread Alex Zepeda

On Thu, Aug 29, 2002 at 01:46:05PM -0700, David O'Brien wrote:

 This is *totally* UNTRUE:
 
 /usr/local/bin//mutt:
 libslang.so = /usr/local/lib/libslang.so (0x280e5000)
 libm.so.2 = /usr/lib/libm.so.2 (0x28148000)
 libssl.so.2 = /usr/lib/libssl.so.2 (0x28167000)
 libcrypto.so.2 = /usr/lib/libcrypto.so.2 (0x28199000)
 libxpg4.so.3 = /usr/lib/libxpg4.so.3 (0x28263000)
 libintl.so.2 = /usr/local/lib/libintl.so.2 (0x28265000)
 libiconv.so.3 = /usr/local/lib/libiconv.so.3 (0x2826c000)
 libncurses.so.5 = /usr/lib/libncurses.so.5 (0x2834)
 libc.so.5 = /usr/lib/libc.so.5 (0x28382000)
 
 note the use of libslang.  TERM=xterm and not having COLORTERM set, mutt
 will not use colors.  TERM=xterm and COLORTERM=yes, mutt will use colors.
 TERM=xterm-color (COLORTERM set or not), mutt will use colors.

Speaking of mutt.  The end keys on my keyboard no longer work within
mutt and xterm.  The work just fine with some other programs and work
fine still within a console.  Just no longer within an xterm.

- alex

To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message



Re: aout support broken in gcc3

2002-09-02 Thread Bruce Evans

On Mon, 2 Sep 2002, Jake Burkholder wrote:

 Apparently, On Mon, Sep 02, 2002 at 02:24:08PM +1000,
   Bruce Evans said words to the effect of;

  aout support is still required for a few things (mainly for compiling
  some boot blocks), but is broken in gcc3 for at least compile-time

 Which boot blocks?

Oops, perhaps only mine.  (I use my version of biosboot which is like
pc98/boot2 except it supports loading elf kernels and some local things,
and it hasn't been converted to elf at the source level.)  When I wrote
the above I thought that several standard boot blocks used OBJFORMAT=-aout.
They actually just have a lot of ${OBJFORMAT} == aout ifdefs and
elf2aout conversions.  Most of aout support at the source level seems to
have been broken some time ago by using new gas features in assembler
code.

  The above assembler output has two syntax errors:
  - .quad 0.  .quad is not supported by the old aout assembler.
  - shldl %eax, %edx.  The old aout assembler only accepts the correct
syntax of shldl %cl,%eax,%edx.  Note that gcc doesn't elide the
similarly implicit %cl register for the sall instruction.

Wrong fixes for .quad are easy and are already done for some systems
(e.g., OpenBSD) by #undefing ASM_QUAD.

The following hack seems to fix shld (the breakage seems to be
intentional):

%%%
Index: i386.md
===
RCS file: /home/ncvs/src/contrib/gcc/config/i386/i386.md,v
retrieving revision 1.12
diff -u -2 -r1.12 i386.md
--- i386.md 1 Sep 2002 21:13:32 -   1.12
+++ i386.md 2 Sep 2002 05:51:30 -
@@ -10768,5 +10768,5 @@
   @
shld{l}\t{%2, %1, %0|%0, %1, %2}
-   shld{l}\t{%s2%1, %0|%0, %1, %2}
+   shld{l}\t{%2, %1, %0|%0, %1, %2}
   [(set_attr type ishift)
(set_attr prefix_0f 1)
%%%

I forgot to make the corresponding change for shrd.

Bruce


To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message



Re: CPU slowdown using ACPI on a Toshiba Portege 7220cte

2002-09-02 Thread Ted Lindgreen

[Quoting David Malone, on Sep  2, 12:22, in Re: CPU slowdown usi ...]

 On Mon, Sep 02, 2002 at 11:52:20AM +0200, Ted Lindgreen wrote:
  - Suspending in X freezes the system. I've not found any way
out of that, other than hard resetting the system.
 
 Could you try running acpidump before and after running X?  On my

Done: output of acpidump is identical before starting X, when running X,
and after stopping X.

-- ted


To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message



Re: HEADS UP: GCC 3.2 in progress

2002-09-02 Thread Maxim Sobolev

Alexander Kabaev wrote:
 
   I will import GCC 3.2 snapshot from the top of FSF gcc-3_2-branch in
 about ten minutes. This task should not take long to complete, but since
 this is the first time I am doing it, there is good possibility of
 unexpected delays, so please be patient.
 
   Please respond immediately if you feel that I need to hold the import
 for some reason.

Cool! Thank you for doing hard work, Alexander. BTW, does it mean that
we just got a fresh new gcc maintainer?

-Maxim

To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message



Re: HEADS UP: GCC 3.2 in progress

2002-09-02 Thread Peter Wemm

Maxim Sobolev wrote:
 Alexander Kabaev wrote:
  
I will import GCC 3.2 snapshot from the top of FSF gcc-3_2-branch in
  about ten minutes. This task should not take long to complete, but since
  this is the first time I am doing it, there is good possibility of
  unexpected delays, so please be patient.
  
Please respond immediately if you feel that I need to hold the import
  for some reason.
 
 Cool! Thank you for doing hard work, Alexander. BTW, does it mean that
 we just got a fresh new gcc maintainer?

I just hope we didn't scare him too much :-)

Cheers,
-Peter
--
Peter Wemm - [EMAIL PROTECTED]; [EMAIL PROTECTED]; [EMAIL PROTECTED]
All of this is for nothing if we don't go to the stars - JMS/B5


To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message



Re: aout support broken in gcc3

2002-09-02 Thread Peter Wemm

Bruce Evans wrote:
 On Mon, 2 Sep 2002, Jake Burkholder wrote:
 
  Apparently, On Mon, Sep 02, 2002 at 02:24:08PM +1000,
  Bruce Evans said words to the effect of;
 
   aout support is still required for a few things (mainly for compiling
   some boot blocks), but is broken in gcc3 for at least compile-time
 
  Which boot blocks?
 
 Oops, perhaps only mine.  (I use my version of biosboot which is like
 pc98/boot2 except it supports loading elf kernels and some local things,
 and it hasn't been converted to elf at the source level.)  When I wrote
 the above I thought that several standard boot blocks used OBJFORMAT=-aout.
 They actually just have a lot of ${OBJFORMAT} == aout ifdefs and
 elf2aout conversions.  Most of aout support at the source level seems to
 have been broken some time ago by using new gas features in assembler
 code.

I've been of the opinion for a while that it is well past time to remove
the hybrid a.out/ELF support in the compiler and stop pretending that we
support a.out.  All it does these days is slow down the compiler in the
usual case by pushing what are traditional compile-time decisions to
runtime.  As you point out, it hasn't worked for a while.

FreeBSD-3.x was a hybrid a.out/elf system
FreeBSD-4.x had vague a.out support but it was not installed by default.  It
may not have been officially deprecated, but was all but.
FreeBSD-5.x should IMHO be a.out free.

We have a couple of things that still use a.out and they are fairly well
encapsulated.  btxld can produce a.out formats for the loader etc even when
fed ELF source files.  elf2aout is also there for the few cases that it is
needed.

The point of updating the toolchain was so that we could use non-archaic
assembler syntax.

If somebody really wants to build a.out stuff, I would suggest that the
thing to do there is to build a binutils with static a.out support (ie:
have a modern gas) and a gcc configured for a.out.  Most of the binutils
bits and bmake glue are around for building an a.out binutils in our tree
(or in the Attic).  We can possibly configure two different cc1 etc
backends for a.out and elf if it comes to that.

The only really interesting use for a.out is for interfacing kernels and
boot code with old roms.  The current binutils in the tree has sufficient
a.out support for that.  It cannot build dynamic binaries or shared libs
though, but that is no big deal.

gcc has grown a native -funderscores option to help with the source
C vs asm symbol compatability problems.

But quite frankly, I'd rather have a binutils-aout and gcc-aout port if we
really have to have a.out support still.

Cheers,
-Peter
--
Peter Wemm - [EMAIL PROTECTED]; [EMAIL PROTECTED]; [EMAIL PROTECTED]
All of this is for nothing if we don't go to the stars - JMS/B5


To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message



'gmake' port broken after (due to ?) GCC 3.2 import

2002-09-02 Thread Nickolay Dudorov

Today (after GCC 3.2 import and makeworld) I
try to upgrade 'gmake' port and resulting 'gmake' command
dumps core in the libc's 'qsort'.

When I make 'gmake' without --with-included-gettext
option it work - at least I can make 'databases/gdbm' port with
it (which can be made without USE_GMAKE also :-).

N.Dudorov


To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message



groff and X11 broken (before gcc3.2)

2002-09-02 Thread Christian Weisgerber

I just finished updating my alpha box to shortly before the gcc3.2
import and now I'm seeing some weird breakage:

$ man ls
out of memory

It's actually nroff (groff) that aborts.
Also:

$ startx
[...]
xinit:  No such file or directory (errno 2):  unable to connect to X server
xinit:  No such process (errno 3):  Server error.

(Hmm, actually that may be due to the XFree86-Server-4.2.0_5 to _6
update.  I think I haven't restarted the X11 server since.)

-- 
Christian naddy Weisgerber  [EMAIL PROTECTED]


To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message



Re: Barebone system rackmount

2002-09-02 Thread Bryan Taylor

John,

You might want to check out www.rackmount.com.  Bought
some 1U/2U rackmount gears from them and pre-loaded with
FreeBSD 4.5. (Six months ago). Their machines are great.
Never had any problem.

Bryan Taylor



On Fri, 23 Aug 2002, John Chang wrote:

 Do you know where I could get a good server rackmount barebones system or a
 rackmount server with FreeBSD installed?

 I am looking to use it for a Web server using Apache.  And would you know
 where I can buy Apache that is more secure out of the box?

 I basically have very little experience with FreeBSD and Apache but since
 it is one of the most secure OSs I thought I would use it.  The alternative
 is using Win2k Adv. Server and IIS or Apache.

 Do you think it is possible to be able to manage a webserver with very
 little experience with FreeBSD and Apache?

 Anyone in Ann Arbor/Detroit Michigan with experience who can help me set it up?

 Thank you.


 To Unsubscribe: send mail to [EMAIL PROTECTED]
 with unsubscribe freebsd-current in the body of the message



To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message



Re: hw.pci.enable_io_modes default value.

2002-09-02 Thread Sheldon Hearn

On (2002/09/01 19:12), Marc Fonvieille wrote:

 I had freeze at boot problem with my laptop and -CURRENT:
 
 http://www.freebsd.org/cgi/query-pr.cgi?pr=42262
 
 I found the solution: setting hw.pci.enable_io_modes to 0.
 So I have a question: that sysctl has to be =1 by default? I mean if I
 have that issue with it and my laptop, maybe I'll not be the only one
 with that problem.
 
 Well I'm sure there is a good reason for that default setting. Perhaps
 we could write somewhere that setting may lead to hangs with some
 hardware :)

Don't be too sure. :-)

revision 1.194
date: 2002/07/26 07:58:16;  author: imp;  state: Exp;  lines: +36 -21
Make PCI_ENABLE_IO_MODES a sysctl hw.pci.enable_io_modes.  It can also
be set at boot time.  It defaults to 1 now since it can be set in the
boot loader.  If this proves unwise, we can reset it to defaulting to 0.

If enough people have trouble with this default, we might want to set it
to 0, since

1) We can't please everyone.
2) We should try to please people with working hardware first.

Ciao,
Sheldon.

To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message



Re: aout support broken in gcc3

2002-09-02 Thread Bruce Evans

On Mon, 2 Sep 2002, Peter Wemm wrote:

 Bruce Evans wrote:
  On Mon, 2 Sep 2002, Jake Burkholder wrote:
 
   Apparently, On Mon, Sep 02, 2002 at 02:24:08PM +1000,
 Bruce Evans said words to the effect of;
  
aout support is still required for a few things (mainly for compiling
some boot blocks), but is broken in gcc3 for at least compile-time
  
   Which boot blocks?
 
  Oops, perhaps only mine.  (I use my version of biosboot which is like
  pc98/boot2 except it supports loading elf kernels and some local things,
  and it hasn't been converted to elf at the source level.)  When I wrote
  ...

 I've been of the opinion for a while that it is well past time to remove
 the hybrid a.out/ELF support in the compiler and stop pretending that we
 support a.out.  All it does these days is slow down the compiler in the
 usual case by pushing what are traditional compile-time decisions to
 runtime.  As you point out, it hasn't worked for a while.

Except I just used it to compile biosboot :-).  (I had more problems with
ufs2 changes than with the compiler.)

Actually, I agree.  Not having a clean break in FreeBSD-3 was very expensive.
Support for running aout binaries and compatibility cruft to support old
binaries should have been dropped too.

Bruce


To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message



Re: aout support broken in gcc3

2002-09-02 Thread Alexander Kabaev

On Tue, 3 Sep 2002 01:09:11 +1000 (EST)
Bruce Evans [EMAIL PROTECTED] wrote:

 
 Except I just used it to compile biosboot :-).  (I had more problems
 with ufs2 changes than with the compiler.)
 
 Actually, I agree.  Not having a clean break in FreeBSD-3 was very
 expensive. Support for running aout binaries and compatibility cruft
 to support old binaries should have been dropped too.

Do we have an agreement here? A.OUT support is to be dropped with the
next gcc upgrade, when/if it will happen?

-- 
Alexander Kabaev

To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message



internal compiler error with gcc 3.2

2002-09-02 Thread Steve Kargl

To test gcc 3.2, I've been updating all of my installed
ports.  It appears gcc 3.2 is having problems with
libiconv-1.8_1.


cc -I. -I. -I../include -I./../include -I/usr/local/include -O -pipe -march=athlon -c 
./iconv.c  -fPIC -DPIC -o .libs/iconv.lo
In file included from gbk.h:64,
 from converters.h:202,
 from iconv.c:67:
gbkext1.h: In function `gbkext1_mbtowc':
gbkext1.h:852: unrecognizable insn:
(insn 157 155 159 (set (reg:QI 79)
(const_int 128 [0x80])) -1 (nil)
(nil))
gbkext1.h:852: Internal compiler error in extract_insn, at recog.c:2150
Please submit a full bug report,
with preprocessed source if appropriate.
See URL:http://www.gnu.org/software/gcc/bugs.html for instructions.
*** Error code 1


-- 
Steve

To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message



Re: internal compiler error with gcc 3.2

2002-09-02 Thread Steve Kargl

On Mon, Sep 02, 2002 at 08:52:56AM -0700, Steve Kargl wrote:
 To test gcc 3.2, I've been updating all of my installed
 ports.  It appears gcc 3.2 is having problems with
 libiconv-1.8_1.
 
 
 cc -I. -I. -I../include -I./../include -I/usr/local/include -O -pipe\
 -march=athlon -c ./iconv.c  -fPIC -DPIC -o .libs/iconv.lo
  ^
This appears to be the cause of the problem.  If I comment
out CPUTYPE?=athlon in /etc/make.conf, then libiconv compiles
without a problem.

 In file included from gbk.h:64,
  from converters.h:202,
  from iconv.c:67:
 gbkext1.h: In function `gbkext1_mbtowc':
 gbkext1.h:852: unrecognizable insn:
 (insn 157 155 159 (set (reg:QI 79)
 (const_int 128 [0x80])) -1 (nil)
 (nil))
 gbkext1.h:852: Internal compiler error in extract_insn, at recog.c:2150
 Please submit a full bug report,
 with preprocessed source if appropriate.
 See URL:http://www.gnu.org/software/gcc/bugs.html for instructions.
 *** Error code 1

-- 
Steve

To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message



Re: internal compiler error with gcc 3.2

2002-09-02 Thread Alexander Kabaev

On Mon, 2 Sep 2002 08:52:56 -0700
Steve Kargl [EMAIL PROTECTED] wrote:

 O -pipe -march=athlon 
  ^^
This bug is in GCC PR database. Do not use -march=athlon for now.
-- 
Alexander Kabaev

To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message



Re: internal compiler error with gcc 3.2

2002-09-02 Thread Alexander Kabaev

BTW, the bug is present in official 3.2 release too.

-- 
Alexander Kabaev

To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message



Re: internal compiler error with gcc 3.2

2002-09-02 Thread Andrea Campi

On Mon, Sep 02, 2002 at 09:01:31AM -0700, Steve Kargl wrote:
 On Mon, Sep 02, 2002 at 08:52:56AM -0700, Steve Kargl wrote:
  To test gcc 3.2, I've been updating all of my installed
  ports.  It appears gcc 3.2 is having problems with
  libiconv-1.8_1.
  
  
  cc -I. -I. -I../include -I./../include -I/usr/local/include -O -pipe\
  -march=athlon -c ./iconv.c  -fPIC -DPIC -o .libs/iconv.lo
   ^
 This appears to be the cause of the problem.  If I comment
 out CPUTYPE?=athlon in /etc/make.conf, then libiconv compiles
 without a problem.
 

I get the same error on a P3:

cc -I. -I. -I../include -I./../include -I/usr/local/include -O -pipe -march=pent
iumpro -c ./iconv.c  -fPIC -DPIC -o .libs/iconv.lo
In file included from gbk.h:64,
 from converters.h:202,
 from iconv.c:67:
gbkext1.h: In function `gbkext1_mbtowc':
gbkext1.h:852: unrecognizable insn:
(insn 157 155 159 (set (reg:QI 78)
(const_int 128 [0x80])) -1 (nil)
(nil))
gbkext1.h:852: Internal compiler error in extract_insn, at recog.c:2150
Please submit a full bug report,
with preprocessed source if appropriate.
See URL:http://www.gnu.org/software/gcc/bugs.html for instructions.
*** Error code 1


-- 
   Press every key to continue.

To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message



Re: internal compiler error with gcc 3.2

2002-09-02 Thread Steve Kargl

On Mon, Sep 02, 2002 at 12:05:40PM -0400, Alexander Kabaev wrote:
 On Mon, 2 Sep 2002 08:52:56 -0700
 Steve Kargl [EMAIL PROTECTED] wrote:
 
  O -pipe -march=athlon 
   ^^
 This bug is in GCC PR database. Do not use -march=athlon for now.

Okay.  In case it matters, world builds with -march=athlon set.

You may want to add a entry to src/UPDATING about the new
gcc 3.2 and any apparent gotcha's (like the problem with
-march=athlon).

-- 
Steve

To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message



Re: groff and X11 broken (before gcc3.2)

2002-09-02 Thread Eric Anholt

On Mon, 2002-09-02 at 05:35, Christian Weisgerber wrote:
 I just finished updating my alpha box to shortly before the gcc3.2
 import and now I'm seeing some weird breakage:

 $ startx
 [...]
 xinit:  No such file or directory (errno 2):  unable to connect to X server
 xinit:  No such process (errno 3):  Server error.
 
 (Hmm, actually that may be due to the XFree86-Server-4.2.0_5 to _6
 update.  I think I haven't restarted the X11 server since.)

You need to either reinstall Xwrapper port, or setuid root your XFree86
and accept the possible security holes.

I wish we could accept having some sort of suid Xwrapper installed with
XFree86-4-Server, but that would probably be shot down for security
concerns by those who don't use startx.

-- 
Eric Anholt [EMAIL PROTECTED]
http://people.freebsd.org/~anholt/dri/



To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message



HEADS UP: rcNG is now the default

2002-09-02 Thread Gordon Tetlow

I'm going to toggle the switch to activate rcNG as the default boot scripts.
If you experience any problems, put rc_ng=NO in your /etc/rc.conf and
please report any problems.

-gordon



msg42462/pgp0.pgp
Description: PGP signature


Fatal warnings breaks ipfw on LP64

2002-09-02 Thread Mike Barcroft


cc1: warnings being treated as errors
/usr/src/sys/netinet/ip_fw2.c: In function `ipfw_ctl':
/usr/src/sys/netinet/ip_fw2.c:2508: warning: cast from pointer to integer of different 
size
/usr/src/sys/netinet/ip_fw2.c:2521: warning: cast from pointer to integer of different 
size

Some of the code in question looks questionable:
/*
 * abuse 'next_rule' to store the set_disable word
 */
(u_int32_t)(((struct ip_fw *)bp)-next_rule) =
set_disable;

The rvalue is being cast in an assignment to make a pointer store an
integer?  Surely this can be written better.

Best regards,
Mike Barcroft

To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message



Re: aout support broken in gcc3

2002-09-02 Thread Gordon Tetlow

On Mon, Sep 02, 2002 at 11:34:48AM -0400, Alexander Kabaev wrote:
 On Tue, 3 Sep 2002 01:09:11 +1000 (EST)
 Bruce Evans [EMAIL PROTECTED] wrote:
 
  
  Except I just used it to compile biosboot :-).  (I had more problems
  with ufs2 changes than with the compiler.)
  
  Actually, I agree.  Not having a clean break in FreeBSD-3 was very
  expensive. Support for running aout binaries and compatibility cruft
  to support old binaries should have been dropped too.
 
 Do we have an agreement here? A.OUT support is to be dropped with the
 next gcc upgrade, when/if it will happen?

I think it should be turned off now. That will help shake out any issues
and people complaining that it is gone. The sooner the better.

-gordon



msg42464/pgp0.pgp
Description: PGP signature


Re: HEADS UP: rcNG is now the default

2002-09-02 Thread Gordon Tetlow

On Mon, Sep 02, 2002 at 09:33:35AM -0700, Gordon Tetlow wrote:
 I'm going to toggle the switch to activate rcNG as the default boot scripts.
 If you experience any problems, put rc_ng=NO in your /etc/rc.conf and
 please report any problems.

There is one outstanding issue with the sendmail script that I'm working on
a solution for. In the general case it should work fine. If you set
sendmail_enable=NONE it will echo a benign warning about it being set
improperly.

-gordon



msg42465/pgp0.pgp
Description: PGP signature


Re: 'gmake' port broken after (due to ?) GCC 3.2 import

2002-09-02 Thread Alexander Kabaev

Not a GCC fault. The bug is in internal gettext library gmake is linked
with. I looked into read_alias_file function and I simply cannot believe
what I am seeing there. Do they really believe malloc is supposed to
resize memory in-place all the time? Look what happens with map[0-n]
elements every time they reallocate their 'string_space' to accomodate
(n+1)th entry.

Building gmake without  --with-included gettext sugddenly seems like a
very good idea for me.

-- 
Alexander Kabaev

To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message



Re: 'gmake' port broken after (due to ?) GCC 3.2 import

2002-09-02 Thread Alexander Kabaev

On Mon, 2 Sep 2002 13:06:31 -0400
Alexander Kabaev [EMAIL PROTECTED] wrote:
Do they really believe malloc
^^^ I meant realloc here.
-- 
Alexander Kabaev

To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message



Re: gcc 3.1 / streambuf.h broken with using namespace std;

2002-09-02 Thread David O'Brien

On Mon, Sep 02, 2002 at 02:17:25AM -0700, Lamont Granquist wrote:
 On Sun, 1 Sep 2002, David O'Brien wrote:
  On Sun, Sep 01, 2002 at 12:37:14PM -0700, Lamont Granquist wrote:
   It sounds like gcc-3.1 or gcc-3.2 will be archaic and buggy
   by the time that 5.2 and 5.3 come out.
 
  How would gcc-3.2 get more buggy over time than it is today??
 
 I said it was buggy.  Do you mean to imply that gcc-3.2 doesn't have a
 single bug in it?

Labling software as buggy is a major put down.  If GCC 3.2 is buggy
because it has at least one bug; then FreeBSD 4.7 will also be buggy as
hell.

 Admittedly I should have said unmaintained though -- point being that
 the bugs in it wouldn't be getting fixed by gcc developers who would
 rather fix them in 3.3...

We don't maintain 3.x either -- much to the disappointment of some that
based products or major deployments on it.  But I do think we support the
current release branch much better than the GCC people do.  We have a
much more liberal MFC policy which lets us continue to fix invasive bugs
and add new features.

To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message



installworld broken

2002-09-02 Thread M. Warner Losh

I've had to add ex, touch and gencat to the installworld target.  And
I've still not manged to complete a installworld.

anybody else see this?

Warner

To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message



Re: internal compiler error with gcc 3.2

2002-09-02 Thread David W. Chapman Jr.

On Mon, Sep 02, 2002 at 09:01:31AM -0700, Steve Kargl wrote:
 On Mon, Sep 02, 2002 at 08:52:56AM -0700, Steve Kargl wrote:
  To test gcc 3.2, I've been updating all of my installed
  ports.  It appears gcc 3.2 is having problems with
  libiconv-1.8_1.
  
  
  cc -I. -I. -I../include -I./../include -I/usr/local/include -O -pipe\
  -march=athlon -c ./iconv.c  -fPIC -DPIC -o .libs/iconv.lo
   ^
 This appears to be the cause of the problem.  If I comment
 out CPUTYPE?=athlon in /etc/make.conf, then libiconv compiles
 without a problem.

Yes, seems to be any CPUTYPE as far as I can tell

-- 
David W. Chapman Jr.
[EMAIL PROTECTED]   Raintree Network Services, Inc. www.inethouston.net
[EMAIL PROTECTED]   FreeBSD Committer www.FreeBSD.org

To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message



Re: groff and X11 broken (before gcc3.2)

2002-09-02 Thread Christian Weisgerber

Eric Anholt [EMAIL PROTECTED] wrote:

  $ startx
  [...]
  xinit:  No such file or directory (errno 2):  unable to connect to X server
  xinit:  No such process (errno 3):  Server error.

Of course those xinit errors are useless; I should have looked at
XFree86.0.log.

 You need to either reinstall Xwrapper port, or setuid root your XFree86
 and accept the possible security holes.

*Smacks forehead*
I know that.  I really do.  I guess I wasn't quite awake yet this
morning.

 I wish we could accept having some sort of suid Xwrapper installed with
 XFree86-4-Server, but that would probably be shot down for security
 concerns by those who don't use startx.

I only use startx because xdm is chronically broken on alpha (at
least the way I use it).

-- 
Christian naddy Weisgerber  [EMAIL PROTECTED]


To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message



Re: 'gmake' port broken after (due to ?) GCC 3.2 import

2002-09-02 Thread Christian Weisgerber

Alexander Kabaev [EMAIL PROTECTED] wrote:

 Not a GCC fault. The bug is in internal gettext library gmake is linked
 with. I looked into read_alias_file function and I simply cannot believe
 what I am seeing there.

PR ports/41075.

-- 
Christian naddy Weisgerber  [EMAIL PROTECTED]


To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message



Re: groff and X11 broken (before gcc3.2)

2002-09-02 Thread Christian Weisgerber

Christian Weisgerber [EMAIL PROTECTED] wrote:

 It's actually nroff (groff) that aborts.

Even a simple groff --version or groff --help will produce the
out of memory error.

-- 
Christian naddy Weisgerber  [EMAIL PROTECTED]


To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message



Re: internal compiler error with gcc 3.2

2002-09-02 Thread David O'Brien

On Mon, Sep 02, 2002 at 12:08:41PM -0400, Alexander Kabaev wrote:
 BTW, the bug is present in official 3.2 release too.

What about 3.1.1 release?

To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message



Re: HEADS UP: GCC 3.2 in progress

2002-09-02 Thread David O'Brien

On Sun, Sep 01, 2002 at 10:21:13PM -0400, Joe Marcus Clarke wrote:
   Actually, if 3.2 doesn't use thunks, it's likely to break Mozilla again.
   This is really not that big of a deal.  I'll just need to alter a patch,
   and update the Mozilla people.
 
  My understanding from watching the patches move through mozilla is
  that the next release of mozilla _will_ work correctly with -CURRENT
  because it is aware of us not using thunks. The thunks patch for
  -CURRENT was verified in the mozilla src tree a week or two back. -sc
 
 Correct.  However, if the compiler changes in -CURRENT not to use thunks,
 then I need to adjust the local patch, and update the Mozilla bug.

Our GCC 3.x now does the exact same thing GCC on Linux does.  Why is this
not a problem on Linux?

To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message



Re: internal compiler error with gcc 3.2

2002-09-02 Thread Alexander Kabaev

On Mon, 2 Sep 2002 11:10:11 -0700
David O'Brien [EMAIL PROTECTED] wrote:

 On Mon, Sep 02, 2002 at 12:08:41PM -0400, Alexander Kabaev wrote:
  BTW, the bug is present in official 3.2 release too.
 
 What about 3.1.1 release?
I have GCC 3.1.1 port installed on STABLE. libiconv barf when compiled
with it too.

-- 
Alexander Kabaev

To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message



Re: hw.pci.enable_io_modes default value.

2002-09-02 Thread M. Warner Losh

In message: [EMAIL PROTECTED]
Sheldon Hearn [EMAIL PROTECTED] writes:
: On (2002/09/01 19:12), Marc Fonvieille wrote:
: 
:  I had freeze at boot problem with my laptop and -CURRENT:
:  
:  http://www.freebsd.org/cgi/query-pr.cgi?pr=42262
:  
:  I found the solution: setting hw.pci.enable_io_modes to 0.
:  So I have a question: that sysctl has to be =1 by default? I mean if I
:  have that issue with it and my laptop, maybe I'll not be the only one
:  with that problem.
:  
:  Well I'm sure there is a good reason for that default setting. Perhaps
:  we could write somewhere that setting may lead to hangs with some
:  hardware :)
: 
: Don't be too sure. :-)
: 
: revision 1.194
: date: 2002/07/26 07:58:16;  author: imp;  state: Exp;  lines: +36 -21
: Make PCI_ENABLE_IO_MODES a sysctl hw.pci.enable_io_modes.  It can also
: be set at boot time.  It defaults to 1 now since it can be set in the
: boot loader.  If this proves unwise, we can reset it to defaulting to 0.
: 
: If enough people have trouble with this default, we might want to set it
: to 0, since
: 
: 1) We can't please everyone.
: 2) We should try to please people with working hardware first.

I made it 1 because I wanted to get feedback on what hardware is
broken.  So far only two people have complained.  Hundreds complained
when the default was 0.  Seems like the choice was good to me still.

Warner

To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message



Re: aout support broken in gcc3

2002-09-02 Thread David O'Brien

On Mon, Sep 02, 2002 at 09:29:05AM -0700, Gordon Tetlow wrote:
 I think it should be turned off now. That will help shake out any issues
 and people complaining that it is gone. The sooner the better.

It isn't a simple knob to turn it off.  It requires several source
changes.

To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message



Re: aout support broken in gcc3

2002-09-02 Thread Matthew Emmerton

On Tue, 3 Sep 2002, Bruce Evans wrote:

 On Mon, 2 Sep 2002, Peter Wemm wrote:
 
  Bruce Evans wrote:
   On Mon, 2 Sep 2002, Jake Burkholder wrote:
  
Apparently, On Mon, Sep 02, 2002 at 02:24:08PM +1000,
Bruce Evans said words to the effect of;
   
 aout support is still required for a few things (mainly for compiling
 some boot blocks), but is broken in gcc3 for at least compile-time
   
Which boot blocks?
  
   Oops, perhaps only mine.  (I use my version of biosboot which is like
   pc98/boot2 except it supports loading elf kernels and some local things,
   and it hasn't been converted to elf at the source level.)  When I wrote
   ...
 
  I've been of the opinion for a while that it is well past time to remove
  the hybrid a.out/ELF support in the compiler and stop pretending that we
  support a.out.  All it does these days is slow down the compiler in the
  usual case by pushing what are traditional compile-time decisions to
  runtime.  As you point out, it hasn't worked for a while.
 
 Except I just used it to compile biosboot :-).  (I had more problems with
 ufs2 changes than with the compiler.)
 
 Actually, I agree.  Not having a clean break in FreeBSD-3 was very expensive.
 Support for running aout binaries and compatibility cruft to support old
 binaries should have been dropped too.

I thought it was part of the plan to drop all traces of a.out support in
5.x.  Am I wrong?

--
Matt Emmerton


To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message



Re: installworld broken

2002-09-02 Thread M. Warner Losh

In message: [EMAIL PROTECTED]
M. Warner Losh [EMAIL PROTECTED] writes:
: I've had to add ex, touch and gencat to the installworld target.  And
: I've still not manged to complete a installworld.
: 
: anybody else see this?

Index: Makefile.inc1
===
RCS file: /home/imp/FreeBSD/CVS/src/Makefile.inc1,v
retrieving revision 1.303
diff -u -r1.303 Makefile.inc1
--- Makefile.inc1   23 Aug 2002 12:49:16 -  1.303
+++ Makefile.inc1   2 Sep 2002 18:51:38 -
@@ -371,9 +372,9 @@
 #
 distributeworld installworld: installcheck
mkdir -p ${INSTALLTMP}
-   for prog in [ awk cat chflags chmod chown date echo egrep find grep \
-   ln make mkdir mtree mv pwd_mkdb rm sed sh sysctl \
-   test true uname wc zic; do \
+   for prog in [ awk cap_mkdb cat chflags chmod chown date echo ex \
+   egrep find gencat grep ln m4 make mkdir mtree mv pwd_mkdb rm \
+   sed sh sysctl test touch true uname wc zic; do \
cp `which $$prog` ${INSTALLTMP}; \
done
cd ${.CURDIR}; ${IMAKE} re${.TARGET:S/world$//}

I plan to commit this change soon unless somone objects.  Yes, all the
programs I added are necessary.  Why they are now and not before, I
know not.

Warner

To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message



Re: aout support broken in gcc3

2002-09-02 Thread Peter Wemm

David O'Brien wrote:
 On Mon, Sep 02, 2002 at 09:29:05AM -0700, Gordon Tetlow wrote:
  I think it should be turned off now. That will help shake out any issues
  and people complaining that it is gone. The sooner the better.
 
 It isn't a simple knob to turn it off.  It requires several source
 changes.

Oh indeed, it is far from simple.  But as a bonus our compiler configuration
for i386 would be a lot closer to what the FSF compiler config looks like. 

Cheers,
-Peter
--
Peter Wemm - [EMAIL PROTECTED]; [EMAIL PROTECTED]; [EMAIL PROTECTED]
All of this is for nothing if we don't go to the stars - JMS/B5


To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message



Re: aout support broken in gcc3

2002-09-02 Thread David O'Brien

On Mon, Sep 02, 2002 at 01:24:19PM -0400, Matthew Emmerton wrote:
 I thought it was part of the plan to drop all traces of a.out support in
 5.x.  Am I wrong?

We should be *very* careful to accurately describe what is being
suggested.

I believe it is that 5.x a.out binaries not be supported.  However, 2.x
a.out binaries will be supported.  This is different thatn drop all
traces of a.out support.

To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message



Re: installworld broken

2002-09-02 Thread Steve Kargl

On Mon, Sep 02, 2002 at 12:52:43PM -0600, M. Warner Losh wrote:
 In message: [EMAIL PROTECTED]
 M. Warner Losh [EMAIL PROTECTED] writes:
 : I've had to add ex, touch and gencat to the installworld target.  And
 : I've still not manged to complete a installworld.
 : 
 : anybody else see this?
 

Strange, I just did a make buildworld ... mergermaster
sequence and I did not need the three utilities you mention.

-- 
Steve

To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message



sparc64 tinderbox failure

2002-09-02 Thread Dag-Erling Smorgrav

--
 Rebuilding the temporary build tree
--
 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
--
=== gnu/usr.bin/cc/cc1plus
method.o: In function `use_thunk':
method.o(.text+0x90c): undefined reference to `sparc_output_mi_thunk'
*** Error code 1

Stop in /usr/home/des/tinderbox/sparc64/src/gnu/usr.bin/cc/cc1plus.
*** Error code 1

Stop in /usr/home/des/tinderbox/sparc64/src/gnu/usr.bin/cc.
*** Error code 1

Stop in /usr/home/des/tinderbox/sparc64/src.
*** Error code 1

Stop in /usr/home/des/tinderbox/sparc64/src.
*** Error code 1

Stop in /usr/home/des/tinderbox/sparc64/src.

To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message



Re: internal compiler error with gcc 3.2

2002-09-02 Thread Kris Kennaway

On Mon, Sep 02, 2002 at 09:01:31AM -0700, Steve Kargl wrote:
 On Mon, Sep 02, 2002 at 08:52:56AM -0700, Steve Kargl wrote:
  To test gcc 3.2, I've been updating all of my installed
  ports.  It appears gcc 3.2 is having problems with
  libiconv-1.8_1.
  
  
  cc -I. -I. -I../include -I./../include -I/usr/local/include -O -pipe\
  -march=athlon -c ./iconv.c  -fPIC -DPIC -o .libs/iconv.lo
   ^
 This appears to be the cause of the problem.  If I comment
 out CPUTYPE?=athlon in /etc/make.conf, then libiconv compiles
 without a problem.

I'm also seeing an internal compiler error during 'make depend' of my
kernel, with CPUTYPE=k6.  It goes away if I set NO_CPU_COPTFLAGS.

Kris



msg42485/pgp0.pgp
Description: PGP signature


Re: hw.pci.enable_io_modes default value.

2002-09-02 Thread Marc Fonvieille

On Mon, Sep 02, 2002 at 12:32:28PM -0600, M. Warner Losh wrote:
 
 I made it 1 because I wanted to get feedback on what hardware is
 broken.  So far only two people have complained.  Hundreds complained
 when the default was 0.  Seems like the choice was good to me still.


I knew there was a good reason :)

Now the problem is archived in the mailing list, it will be useful for
other users.

Marc

To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message



Re: sparc64 tinderbox failure

2002-09-02 Thread Alexander Kabaev

On Mon, 2 Sep 2002 19:51:59 GMT
Dag-Erling Smorgrav [EMAIL PROTECTED] wrote:

 === gnu/usr.bin/cc/cc1plus
 method.o: In function `use_thunk':
 method.o(.text+0x90c): undefined reference to `sparc_output_mi_thunk'

Is this gcc 3.1 trying to build 3.2 or gcc 3.2 trying to build itself?
Buildworld completes fine on panther, the only FreeBSD sparc64 machine I
have access to.

-- 
Alexander Kabaev

To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message



Re: i386 tinderbox failure

2002-09-02 Thread Thomas Quinot

Le 2002-09-01, Scott Long écrivait :

  === aic7xxx/ahc
  (null): Unable to malloc scope object
  *** Error code 70
 
 Um, what?
 
 I just did a buildworld, followed by a buildkernel KERNCONF=GENERIC
 and did not see this.

Um, I see this one as well, on a not-too-recent -CURRENT that I'm trying
to bring up to date:

FreeBSD shalmaneser.enst.fr 5.0-CURRENT FreeBSD 5.0-CURRENT #15:
   Mon Apr 22 17:40:12 CEST 2002

The machine is otherwise essentially idle, and top shows plenty of
available memory.

Thomas.

-- 
[EMAIL PROTECTED]

To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message



aic7xxx kernel build failure...

2002-09-02 Thread Sean Chittenden

Is anyone else seeing something similar to the following?  I'm able to
build world, but can't get this kernel build to budge.  I've not seen
this error before so I'm a tad lost as to where to poke next.  -sc

=== aic7xxx
=== aic7xxx/aicasm
make -f /usr/src/sys/modules/aic7xxx/aicasm/../../../dev/aic7xxx/aicasm/Makefile  
MAKESRCPATH=/usr/src/sys/modules/aic7xxx/aicasm/../../../dev/aic7xxx/aicasm depend
=== aic7xxx/ahc
 - /usr/src/sys
machine - /usr/src/sys/i386/include
/usr/obj/usr/src/sys/DELLAPTOP/modules/usr/src/sys/modules/aic7xxx/ahc/../aicasm/aicasm
  -I/usr/src/sys/modules/aic7xxx/ahc/../../../cam/scsi  
-I/usr/src/sys/modules/aic7xxx/ahc/../../../dev/aic7xxx-o 
aic7xxx_seq.h -r aic7xxx_reg.h   -p aic7xxx_reg_print.c
-i /usr/src/sys/modules/aic7xxx/ahc/../../../dev/aic7xxx/aic7xxx_osm.h  
/usr/src/sys/modules/aic7xxx/ahc/../../../dev/aic7xxx/aic7xxx.seq
(null): Unable to malloc scope object
*** Error code 70

Stop in /usr/src/sys/modules/aic7xxx/ahc.
*** Error code 1

Stop in /usr/src/sys/modules/aic7xxx.
*** Error code 1

Stop in /usr/src/sys/modules.
*** Error code 1

Stop in /usr/obj/usr/src/sys/DELLAPTOP.
*** Error code 1

Stop in /usr/src.
*** Error code 1

Stop in /usr/src.



-- 
Sean Chittenden



msg42489/pgp0.pgp
Description: PGP signature


RE: aic7xxx kernel build failure...

2002-09-02 Thread Long, Scott

 
 Is anyone else seeing something similar to the following?  I'm able to
 build world, but can't get this kernel build to budge.  I've not seen
 this error before so I'm a tad lost as to where to poke next.  -sc

This is the third report of this that I've seen, and I'm completely
baffled.  How old is your existing kernel and world?  If it's old,
can you just build a new kernel (no modules) and try with that?

Scott

 
 === aic7xxx
 === aic7xxx/aicasm
 make -f 
 /usr/src/sys/modules/aic7xxx/aicasm/../../../dev/aic7xxx/aicas
 m/Makefile  
 MAKESRCPATH=/usr/src/sys/modules/aic7xxx/aicasm/../../../dev/a
 ic7xxx/aicasm depend
 === aic7xxx/ahc
 @ - /usr/src/sys
 machine - /usr/src/sys/i386/include
 /usr/obj/usr/src/sys/DELLAPTOP/modules/usr/src/sys/modules/aic
 7xxx/ahc/../aicasm/aicasm  
 -I/usr/src/sys/modules/aic7xxx/ahc/../../../cam/scsi  
 -I/usr/src/sys/modules/aic7xxx/ahc/../../../dev/aic7xxx   
  -o aic7xxx_seq.h -r aic7xxx_reg.h   -p 
 aic7xxx_reg_print.c-i 
 /usr/src/sys/modules/aic7xxx/ahc/../../../dev/aic7xxx/aic7xxx_
 osm.h  
 /usr/src/sys/modules/aic7xxx/ahc/../../../dev/aic7xxx/aic7xxx.seq
 (null): Unable to malloc scope object
 *** Error code 70
 
 Stop in /usr/src/sys/modules/aic7xxx/ahc.
 *** Error code 1
 
 Stop in /usr/src/sys/modules/aic7xxx.
 *** Error code 1
 
 Stop in /usr/src/sys/modules.
 *** Error code 1
 
 Stop in /usr/obj/usr/src/sys/DELLAPTOP.
 *** Error code 1
 
 Stop in /usr/src.
 *** Error code 1
 
 Stop in /usr/src.
 
 
 
 -- 
 Sean Chittenden
 

To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message



Re: aic7xxx kernel build failure...

2002-09-02 Thread Sean Chittenden

  Is anyone else seeing something similar to the following?  I'm able to
  build world, but can't get this kernel build to budge.  I've not seen
  this error before so I'm a tad lost as to where to poke next.  -sc
 
 This is the third report of this that I've seen, and I'm completely
 baffled.

Glad that's two of us then.  :)

 How old is your existing kernel and world?

aug-05

 If it's old, can you just build a new kernel (no modules) and try
 with that?

Okey doke... -DNO_MODULES?  (haven't done a kernel w/o any modules
before: there another way to just unlink the aic7xxx stuff from the
build?) -sc

  /usr/obj/usr/src/sys/DELLAPTOP/modules/usr/src/sys/modules/aic
  7xxx/ahc/../aicasm/aicasm  
  -I/usr/src/sys/modules/aic7xxx/ahc/../../../cam/scsi  
  -I/usr/src/sys/modules/aic7xxx/ahc/../../../dev/aic7xxx   
   -o aic7xxx_seq.h -r aic7xxx_reg.h   -p 
  aic7xxx_reg_print.c-i 
  /usr/src/sys/modules/aic7xxx/ahc/../../../dev/aic7xxx/aic7xxx_
  osm.h  
  /usr/src/sys/modules/aic7xxx/ahc/../../../dev/aic7xxx/aic7xxx.seq
  (null): Unable to malloc scope object
  *** Error code 70

-- 
Sean Chittenden



msg42491/pgp0.pgp
Description: PGP signature


Re: aout support broken in gcc3

2002-09-02 Thread Julian Elischer



On Mon, 2 Sep 2002, David O'Brien wrote:

 On Mon, Sep 02, 2002 at 01:24:19PM -0400, Matthew Emmerton wrote:
  I thought it was part of the plan to drop all traces of a.out support in
  5.x.  Am I wrong?
 
 We should be *very* careful to accurately describe what is being
 suggested.
 
 I believe it is that 5.x a.out binaries not be supported.  However, 2.x
 a.out binaries will be supported.  This is different thatn drop all
 traces of a.out support.

yes binary support will remain.. if you need to generate new ones (?)
unpack a 2.2.6 system into a chroot tree (jail?) and make it there :-)



To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message



Re: aout support broken in gcc3

2002-09-02 Thread Juli Mallett

* De: David O'Brien [EMAIL PROTECTED] [ Data: 2002-09-02 ]
[ Subjecte: Re: aout support broken in gcc3 ]
 On Mon, Sep 02, 2002 at 01:24:19PM -0400, Matthew Emmerton wrote:
  I thought it was part of the plan to drop all traces of a.out support in
  5.x.  Am I wrong?
 
 We should be *very* careful to accurately describe what is being
 suggested.
 
 I believe it is that 5.x a.out binaries not be supported.  However, 2.x
 a.out binaries will be supported.  This is different thatn drop all
 traces of a.out support.

I *hope* nobody is suggesting to rip out the ability to use compat22, let
alone the a.out execution facilities in the Kernel.  Though maybe making
those optional would be good?
-- 
Juli Mallett [EMAIL PROTECTED]   | FreeBSD: The Power To Serve
Will break world for fulltime employment. | finger [EMAIL PROTECTED]

To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message



Re: sparc64 tinderbox failure

2002-09-02 Thread Mike Barcroft

Alexander Kabaev [EMAIL PROTECTED] writes:
 On Mon, 2 Sep 2002 19:51:59 GMT
 Dag-Erling Smorgrav [EMAIL PROTECTED] wrote:
 
  === gnu/usr.bin/cc/cc1plus
  method.o: In function `use_thunk':
  method.o(.text+0x90c): undefined reference to `sparc_output_mi_thunk'
 
 Is this gcc 3.1 trying to build 3.2 or gcc 3.2 trying to build itself?
 Buildworld completes fine on panther, the only FreeBSD sparc64 machine I
 have access to.

The complete transcript is available here:
http://sparc64.style9.org/sparc64.log

Best regards,
Mike Barcroft

To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message



Re: sparc64 tinderbox failure

2002-09-02 Thread Alexander Kabaev


 The complete transcript is available here:
 http://sparc64.style9.org/sparc64.log

Which still does not answer my question. What GCC version is on this
machine? 

-- 
Alexander Kabaev

To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message



Re: sparc64 tinderbox failure

2002-09-02 Thread Mike Barcroft

Alexander Kabaev [EMAIL PROTECTED] writes:
 
  The complete transcript is available here:
  http://sparc64.style9.org/sparc64.log
 
 Which still does not answer my question. What GCC version is on this
 machine? 

Sorry, I thought your question was whether it was in the cross
building stage or later on in the build.

%gcc -v
Using built-in specs.
Configured with: FreeBSD/sparc64 system compiler
Thread model: posix
gcc version 3.1 [FreeBSD] 20020509 (prerelease)

I can provide you with an account on the system.

Best regards,
Mike Barcroft

To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message



CardBUS NIC Support w/ IBM ThinkPad 770Z under -CURRENT

2002-09-02 Thread Vincent Poy

Greetings everyone:

I decided to pull the trigger and try to run FreeBSD on my IBM
ThinkPad 770Z with a 3COM 3CXFEM656C 10/100 NIC + 56k modem Cardbus combo.
Originally I tried 4.6.2-RELEASE but Cardbus isn't support so I tried both
a NetGear FA411 10/100 PCMCIA and the LinkSys PCM100 Etherfast 10/100
PCMCIA.  Both worked under the ed1 driver.  When I was testing speeds
to/from my desktop which is on a Intel Pro100+ Management (fxp0), the
LinkSys was doing 1080Kbytes/sec or 8.64Mbps but the NetGear started at
300Kbytes/sec or 2.4Mbps and then the speed went down to 80Kbytes/sec or
640Kbps and stayed there.  I was looking at the -CURRENT srctree and
noticed that NEWCARD has been merged into GENERIC so from
current.FreeBSD.ORG, I got the 08182002 ISO Snapshot and attempted to use
the 3Com 3CXFEM656C on it, -current recognized the card and assigned it as
xl0 on irq 11.  As soon as the IP is assigned to it with:

ifconfig xl0 inet 209.204.138.100 netmask 255.255.255.0

It keeps sending xl0: watchdog timeout repeatively to the console.
When I tried the LinkSys and the NetGear PCMCIA 16bit cards, it says card
functions not found.  Anyone have any ideas what's wrong or what other
-current snapshot version should I be using?  Is it just the 3Com is a bad
card to use or is there another cardbus NIC that works well?  Thanks!


Cheers,
Vince - [EMAIL PROTECTED] - Vice President    __ 
Unix Networking Operations - FreeBSD-Real Unix for Free / / / / |  / |[__  ]
WurldLink Corporation  / / / /  | /  | __] ]
San Francisco - Honolulu - Hong Kong  / / / / / |/ / | __] ]
HongKong Stars/Gravis UltraSound Mailing Lists Admin /_/_/_/_/|___/|_|[]
Almighty1@IRC - oahu.DAL.NET Hawaii's DALnet IRC Network Server Admin


To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message



Re: HEADS UP: GCC 3.2.1-pre imported

2002-09-02 Thread Mikhail Teterin

On Sunday 01 September 2002 05:58 pm, Alexander Kabaev wrote:
= GCC 3.2.1-pre is now in the tree. Please let me know if you see any
= problems recompiling your world/kernel.
=
= Remember to recompile your C++ ports. GCC 3.2 is not binary compatible
= with 3.1.

Most excellent! Thanks!

-mi

P.S. I wonder, if pentium[34]/SSE optimizations are working now...

To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message



Re: aic7xxx kernel build failure...

2002-09-02 Thread Sean Chittenden

Is anyone else seeing something similar to the following? 
   I'm able to
build world, but can't get this kernel build to budge.  
  I've not seen
this error before so I'm a tad lost as to where to poke next.  -sc
   
   This is the third report of this that I've seen, and I'm completely
   baffled.
  
  Glad that's two of us then.  :)
  
   How old is your existing kernel and world?
  
  aug-05
 
 The i386 tinderbox build encountered this once yesterday, but hasn't
 complained since.  shrug
 
   If it's old, can you just build a new kernel (no modules) and try
   with that?
  
  Okey doke... -DNO_MODULES?  (haven't done a kernel w/o any modules
  before: there another way to just unlink the aic7xxx stuff from the
  build?) -sc
  
 
 I think you need to put NOMODULES=1 onto the make line as so
 
   make buildkernel KERNCONF=foo NOMODULES=1
 
 If that doesn't work, you can unhook aic7xxx from the build by editing
 /sys/modules/Makefile.

Well, I ended up unlinking it from the build and am installing now.
Once I get a fresh world installed, I'll try and rebuild world again
to see if the problem persists.  Would you like me to get a ktrace of
aicasm running before I rebuild world?  -sc

-- 
Sean Chittenden

To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message



compiling kdelibs3 fails with -current's gcc 3.2

2002-09-02 Thread Michael Reifenberger

Hi,
with -current I get during compiling kdelibs3 (and after successfully compiling
qt3 and arts):
...
c++ -DHAVE_CONFIG_H -I. -I. -I.. -I../dcop -I../libltdl -I../kdecore -I../kdeui
-I../kio -I../kio/kio -I../kio/kfile -I/usr/X11R6/include -I/usr/local/include -
pthread -DQT_THREAD_SUPPORT -I/usr/local/include -I/usr/local/include -I/usr/X11
R6/include -D_THREAD_SAFE -I/usr/local/include -DNDEBUG -DNO_DEBUG -O2 -O -pipe
-fno-exceptions -fno-check-new -DQT_NO_TRANSLATION -DQT_CLEAN_NAMESPACE -DQT_NO_
ASCII_CAST -DQT_NO_COMPAT -c kkeyserver_x11.cpp -MT kkeyserver_x11.lo -MD -MP -M
F .deps/kkeyserver_x11.TPlo  -fPIC -DPIC -o .libs/kkeyserver_x11.o
kkeyserver_x11.cpp: In function `void
   __static_initialization_and_destruction_0(int, int)':
kkeyserver_x11.cpp:73: Internal compiler error in cp_expr_size, at cp/cp-lang.c
   :130
Please submit a full bug report,
with preprocessed source if appropriate.
See URL:http://www.gnu.org/software/gcc/bugs.html for instructions.
gmake[3]: *** [kkeyserver_x11.lo] Fehler 1
gmake[3]: Verlassen des Verzeichnisses Verzeichnis »/usr/ports/x11/kdelibs3/work
/kdelibs-3.0.3/kdecore
...

I tried CFLAGS with -O[1|2] and with or without -march=-pentium3.
Always the same error.

Anyone else?

Bye!

Michael Reifenberger
^.*Plaut.*$, IT, R/3 Basis, GPS


To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message



Re: aout support broken in gcc3

2002-09-02 Thread Richard Tobin

 yes binary support will remain.. if you need to generate new ones (?)

You say this as if no-one would want to do it, but I still use
programs (lisp and prolog compilers) that need to generate and read in
compiled .o files, and undump themselves after reading in such
files, and which are never likely to be updated to know about (the
much more complicated) elf format.

-- Richard

To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message



Re: aout support broken in gcc3

2002-09-02 Thread Juli Mallett

* De: Richard Tobin [EMAIL PROTECTED] [ Data: 2002-09-02 ]
[ Subjecte: Re: aout support broken in gcc3 ]
  yes binary support will remain.. if you need to generate new ones (?)
 
 You say this as if no-one would want to do it, but I still use
 programs (lisp and prolog compilers) that need to generate and read in
 compiled .o files, and undump themselves after reading in such
 files, and which are never likely to be updated to know about (the
 much more complicated) elf format.

I think you're extremeley confused.
-- 
Juli Mallett [EMAIL PROTECTED]   | FreeBSD: The Power To Serve
Will break world for fulltime employment. | finger [EMAIL PROTECTED]

To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message



Re: compiling kdelibs3 fails with -current's gcc 3.2

2002-09-02 Thread Manfred Antar

At 12:29 AM 9/3/2002 +0200, Michael Reifenberger wrote:
Hi,
with -current I get during compiling kdelibs3 (and after successfully compiling
qt3 and arts):
...
c++ -DHAVE_CONFIG_H -I. -I. -I.. -I../dcop -I../libltdl -I../kdecore -I../kdeui
-I../kio -I../kio/kio -I../kio/kfile -I/usr/X11R6/include -I/usr/local/include -
pthread -DQT_THREAD_SUPPORT -I/usr/local/include -I/usr/local/include -I/usr/X11
R6/include -D_THREAD_SAFE -I/usr/local/include -DNDEBUG -DNO_DEBUG -O2 -O -pipe
-fno-exceptions -fno-check-new -DQT_NO_TRANSLATION -DQT_CLEAN_NAMESPACE -DQT_NO_
ASCII_CAST -DQT_NO_COMPAT -c kkeyserver_x11.cpp -MT kkeyserver_x11.lo -MD -MP -M
F .deps/kkeyserver_x11.TPlo  -fPIC -DPIC -o .libs/kkeyserver_x11.o
kkeyserver_x11.cpp: In function `void
   __static_initialization_and_destruction_0(int, int)':
kkeyserver_x11.cpp:73: Internal compiler error in cp_expr_size, at cp/cp-lang.c
   :130
Please submit a full bug report,
with preprocessed source if appropriate.
See URL:http://www.gnu.org/software/gcc/bugs.html for instructions.
gmake[3]: *** [kkeyserver_x11.lo] Fehler 1
gmake[3]: Verlassen des Verzeichnisses Verzeichnis »/usr/ports/x11/kdelibs3/work
/kdelibs-3.0.3/kdecore
...

I tried CFLAGS with -O[1|2] and with or without -march=-pentium3.
Always the same error.

Anyone else?


Same thing here with fresh QT and arts with gcc3.2.
With current built this afternoon.
before I tried I did a pkg_delete -f kde* so as to not have any stale libs.
Manfred

==
||  [EMAIL PROTECTED]   ||
||  Ph. (415) 681-6235  ||
==


To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message



Dissertation text available

2002-09-02 Thread Menelaos G. Tzouris

Dear all,

I have now uploaded the final text of my dissertation on 
http://www.geocities.com/tzmnlaos/oss/tzouris_diss.pdf

Thanks to everybody that helped towards the completions of this research.

Best Regards,
Menelaos.


Tzouris,M wrote:

 Hello again,
  
 I uploaded a newer version of my online questionnaire
 (http://www.lse-students.ac.uk/tzouris/oss), and I am searching for Open
 Source contributors who might be interested in answering it.
  
 The questionnaire is designed in a way that it won't require more than 
 10 minutes to be answered.
  
 My previous request didn't have the expected responce, so you are 
 kindly asked to answer this one. It will take you for sure less than 
 10 minutes!
  
 My MPhil/PhD which is commencing in the upcoming October, will be based
 on my current research. So as you can understand your help is really
 important to me.
  
 If you are a contributor, you are kindly requested to fill in this 
 questionnaire
 http://www.lse-students.ac.uk/tzouris/oss
  
 Thank you very much in advance for your help,
 Menelaos.
  
 PS: my background:
 I am an MSc student at the London School of Economics, department of
 Information Systems, London, U.K. (http://is.lse.ac.uk) I am currently
 writing my summer dissertation (MSc thesis) on Open Source. This is
 where I need your help!
  
 I received my Bsc in Computer Science fro the Athens University of
 Economics and Business (http://www.cs.aueb.gr http://www.cs.acueb.gr)
 Some of the issues that have been covered in my BSc are published here:
 http://www.geocities.com/tzmnlaos
  
 =
 Menelaos G. Tzouris
 Graduate Student
 Department of Information Systems
 London School of Economics and Political Science




Do You Yahoo!?
ÁðïêôÞóôå ôç äùñåÜí @yahoo.gr äéåýèõíóç óáò óôï http://www.otenet.gr

To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message



perl busted, spins, ignores SIGKILL

2002-09-02 Thread Lamont Granquist


i cvsup'd last night, and now i tried portupdate -a -f and debugging
build problems with libtool i found that on my system i can make perl spin
and consume 100% of a CPU just by:

perl -pe s/foo/bar/g /tmp

(turs out i can do this with any perl command, even perl --version...)

i also can't kill this process, or attach to it with gdb.  i can get an
strace though which looks like:

execve(8AF3^D(HF3^E(B0F3BFBFF4BFBF^DF4BFBFE1^E(^?^R
, [], [/* 0 vars */]) = -1 ENOENT (No such file or directory)
execve(, [], [/* 0 vars */])  = -1 ENOENT (No such file or
directory)
execve(, [], [/* 0 vars */])  = -1 ENOENT (No such file or
directory)
execve(, [], [/* 0 vars */])  = 0
mmap(0, 2664, PROT_READ|PROT_WRITE, MAP_ANON, -1, 0) = 0x28061000
munmap(0x28061000, 2664)= 0
__sysctl([sysctl.debug], 2, , [0], NULL, 0) = 0
mmap(0, 32768, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANON, -1, 0) =
0x28061000
geteuid(0x28049000) = 0
getuid()= 0 (euid 0)
getegid(0x28049000) = 0
getgid()= 0 (egid 0)
open(/var/run/ld-elf.so.hints, O_RDONLY) = 3
read(3,  object\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0..., 128)
= 128
lseek(3, 549755813888, SEEK_SET)= 128
read(3, /usr/lib:/usr/lib/compat:/usr/X1..., 55) = 55
close(3)= 0
access(/usr/lib/libc.so.5, F_OK)  = 0
open(/usr/lib/libc.so.5, O_RDONLY)= 3
fstat(3, {st_mode=0, st_size=0, ...})   = 0
read(3, \0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0..., 4096)
= 409
6
mmap(0, 794624, PROT_READ|PROT_EXEC, MAP_PRIVATE, 3, 0) = 0x28069000
mmap(0x28113000, 20480, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_FIXED, 3,
0xa9
000) = 0x28113000
mmap(0x28118000, 77824, PROT_READ|PROT_WRITE,
MAP_PRIVATE|MAP_FIXED|MAP_ANON, -1
, 0) = 0x28118000
close(3)= 0
mmap(0, 216, PROT_READ|PROT_WRITE, MAP_ANON, -1, 0) = 0x2812b000
munmap(0x2812b000, 216) = 0
mprotect(0x28069000, 696320, PROT_READ|PROT_WRITE|PROT_EXEC) = 0
mmap(0, 18824, PROT_READ|PROT_WRITE, MAP_ANON, -1, 0) = 0x2812b000
munmap(0x2812b000, 18824)   = 0
mprotect(0x28069000, 696320, PROT_READ|PROT_EXEC) = 0
sigaction(SIGILL, {SIG_DFL}, {SIG_DFL}) = 0
sigprocmask(SIG_BLOCK, NULL, [])= 0
sigaction(SIGILL, {SIG_DFL}, NULL)  = 0
sigprocmask(SIG_BLOCK, ~[ILL TRAP ABRT EMT FPE BUS SEGV SYS], []) = 0
sigprocmask(SIG_SETMASK, [], NULL)  = 0
execve(8AF3^D(HF3^E(B8F3BFBFDF4BFBF^LF4BFBFE1^E(^?^R
, [], [/* 0 vars */]) = -1 ENOENT (No such file or directory)
execve(, [], [/* 0 vars */])  = -1 ENOENT (No such file or
directory)
execve(, [], [/* 0 vars */])  = -1 ENOENT (No such file or
directory)
execve(, [], [/* 0 vars */])  = -1 ENOENT (No such file or
directory)
execve(, [], [/* 0 vars */])  = -1 ENOENT (No such file or
directory)
execve(, [], [/* 0 vars */])  = 0

(wash, rinse, repeat endlessly..)

strace sometimes fails with:

PIOCWSTOP: Input/output error

ahhh...  the plot thickens, now its stopped consuming CPU, strace does
this:

coredump# strace -p 4432
--- SIGINT (Interrupt) ---
--- SIGINT (Interrupt) ---
coredump# strace -p 4432
strace: open(/proc/..., ...): No such file or directory
trouble opening proc file
coredump# strace -p 4432
strace: open(/proc/..., ...): No such file or directory
trouble opening proc file


To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message



Re: aout support broken in gcc3

2002-09-02 Thread Richard Tobin

 I think you're extremeley confused.

In what way?  Or are you just being rude?

-- RIchard

To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message



alpha tinderbox failure

2002-09-02 Thread Dag-Erling Smorgrav

--
 Rebuilding the temporary build tree
--
 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/alpha/obj/var/tmp/des/src/alpha/usr/include
--
 stage 4: building libraries
--
 stage 4: make dependencies
--
=== usr.bin/getconf
Virtual memory exhausted in `operator new'
*** Error code 1

Stop in /var/tmp/des/src/usr.bin/getconf.
*** Error code 1

Stop in /var/tmp/des/src/usr.bin.
*** Error code 1

Stop in /var/tmp/des/src.
*** Error code 1

Stop in /var/tmp/des/src.
*** Error code 1

Stop in /var/tmp/des/src.

To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message



Re: gcc 3.1 / streambuf.h broken with using namespace std;

2002-09-02 Thread Lamont Granquist



On Mon, 2 Sep 2002, David O'Brien wrote:
 On Mon, Sep 02, 2002 at 02:17:25AM -0700, Lamont Granquist wrote:
  On Sun, 1 Sep 2002, David O'Brien wrote:
   On Sun, Sep 01, 2002 at 12:37:14PM -0700, Lamont Granquist wrote:
It sounds like gcc-3.1 or gcc-3.2 will be archaic and buggy
by the time that 5.2 and 5.3 come out.
  
   How would gcc-3.2 get more buggy over time than it is today??
 
  I said it was buggy.  Do you mean to imply that gcc-3.2 doesn't have a
  single bug in it?

 Labling software as buggy is a major put down.  If GCC 3.2 is buggy
 because it has at least one bug; then FreeBSD 4.7 will also be buggy as
 hell.

A year from now it probably will be seen as being buggy as hell and i
think you're taking the description of buggy far too personally...
Software has bugs, over time those bugs surface, some of them are due to
design flaws which mean they don't get fixed in older versions and
also developers tend to abandon support of older versions.  The perception
is that the software becomes buggy and it becomes frustrating to work with
that software, even if you were perfectly happy with it a year ago.

  Admittedly I should have said unmaintained though -- point being that
  the bugs in it wouldn't be getting fixed by gcc developers who would
  rather fix them in 3.3...

 We don't maintain 3.x either -- much to the disappointment of some that
 based products or major deployments on it.  But I do think we support the
 current release branch much better than the GCC people do.  We have a
 much more liberal MFC policy which lets us continue to fix invasive bugs
 and add new features.

Even more reason to try to get as current with gcc as possible with 5.0 --
if they're not liberally MFC'ing to 3.2 then it makes sense to launch
5.0 on a pre-3.3.  Otherwise its up to the FreeBSD developers to try to
duplicate the gcc developers efforts and patch gcc-3.2 in the 5.0 tree.


To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message



Re: compiling kdelibs3 fails with -current's gcc 3.2

2002-09-02 Thread Alex Zepeda

On Tue, Sep 03, 2002 at 12:29:23AM +0200, Michael Reifenberger wrote:

 I tried CFLAGS with -O[1|2] and with or without -march=-pentium3.
 Always the same error.
 
 Anyone else?

I'm seeing the exact same thing.  I can't install linux_base either, nor 
can I build rpm.

- alex

To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message



Re: aout support broken in gcc3

2002-09-02 Thread Juli Mallett

* De: Richard Tobin [EMAIL PROTECTED] [ Data: 2002-09-02 ]
[ Subjecte: Re: aout support broken in gcc3 ]
  I think you're extremeley confused.
 
 In what way?  Or are you just being rude?

GCC being able to produce a.out format binaries has nothing to do with
the ability of a Lisp or Prolog to compile to object files, and read
such, whether said object files be a.out or ELF or COFF or PECOFF or
Mach-O or ...  For example, Mono works with PECOFF32 images, and can
read them in and out on Windows, NetBSD, OpenBSD, FreeBSD, Linnex, and
probably QNX.

And nothing says that '.o' or 'a.out' implies the image is in a.out or
ELF or PECOFF or ... format.

juli.
-- 
Juli Mallett [EMAIL PROTECTED]   | FreeBSD: The Power To Serve
Will break world for fulltime employment. | finger [EMAIL PROTECTED]

To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message



Re: compiling kdelibs3 fails with -current's gcc 3.2

2002-09-02 Thread Alexander Kabaev

On Mon, 2 Sep 2002 16:27:45 -0700
Alex Zepeda [EMAIL PROTECTED] wrote:
 
 I'm seeing the exact same thing.  I can't install linux_base either,
 nor can I build rpm.

Have no idea what is your problem with linux_base, but rpm build fine
here after one gets past __size_t and machine/types.h.

-- 
Alexander Kabaev


To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message



Re: internal compiler error with gcc 3.2

2002-09-02 Thread Terry Lambert

Andrea Campi wrote:
   cc -I. -I. -I../include -I./../include -I/usr/local/include -O -pipe\
   -march=athlon -c ./iconv.c  -fPIC -DPIC -o .libs/iconv.lo
^
 
 I get the same error on a P3:
 
 cc -I. -I. -I../include -I./../include -I/usr/local/include -O -pipe
 -march=pentiumpro -c ./iconv.c  -fPIC -DPIC -o .libs/iconv.lo
  ^

Maybe -march=* doesn't work?

-- Terry

To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message



Re: internal compiler error with gcc 3.2

2002-09-02 Thread Alexander Kabaev

On Mon, 02 Sep 2002 17:20:49 -0700
Terry Lambert [EMAIL PROTECTED] wrote:

  cc -I. -I. -I../include -I./../include -I/usr/local/include -O -pipe
  -march=pentiumpro -c ./iconv.c  -fPIC -DPIC -o .libs/iconv.lo
   ^
 
 Maybe -march=* doesn't work?

I traced it down to broken if_convert optomization. 


-- 
Alexander Kabaev


To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message



Re: compiling kdelibs3 fails with -current's gcc 3.2

2002-09-02 Thread Alexander Kabaev

The patch I sent is reversed. Use patch -R to apply.
-- 
Alexander Kabaev


To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message



Re: aout support broken in gcc3

2002-09-02 Thread Matthew Emmerton

 * De: David O'Brien [EMAIL PROTECTED] [ Data: 2002-09-02 ]
 [ Subjecte: Re: aout support broken in gcc3 ]
  On Mon, Sep 02, 2002 at 01:24:19PM -0400, Matthew Emmerton wrote:
   I thought it was part of the plan to drop all traces of a.out support
in
   5.x.  Am I wrong?
 
  We should be *very* careful to accurately describe what is being
  suggested.
 
  I believe it is that 5.x a.out binaries not be supported.  However, 2.x
  a.out binaries will be supported.  This is different thatn drop all
  traces of a.out support.

 I *hope* nobody is suggesting to rip out the ability to use compat22, let
 alone the a.out execution facilities in the Kernel.  Though maybe making
 those optional would be good?

Sorry, I didn't mean what I said.  I meant what Juli suggested (support for
compat2x) but removing native 5.x support for a.out, which will help clean
up some things in the tools chain.

--
Matt Emmerton


To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message



Re: aic7xxx kernel build failure...

2002-09-02 Thread Justin T. Gibbs

 Well, I ended up unlinking it from the build and am installing now.
 Once I get a fresh world installed, I'll try and rebuild world again
 to see if the problem persists.  Would you like me to get a ktrace of
 aicasm running before I rebuild world?  -sc

That would have been interesting.

--
Justin


To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message



Re: Re: compiling kdelibs3 fails with -current's gcc 3.2

2002-09-02 Thread Alexander Kabaev

 Where can I find this patch? I didn't see it in the message body or attached to any 
of your previous messages. 

Sorry,

apparently attachments are stripped now before being delivered
to the mailing lists. The patch is below:


Index: cp/cp-lang.c
===
RCS file: /home/ncvs/src/contrib/gcc/cp/cp-lang.c,v
retrieving revision 1.1.1.2
diff -u -r1.1.1.2 cp-lang.c
--- cp/cp-lang.c1 Sep 2002 20:38:06 -   1.1.1.2
+++ cp/cp-lang.c3 Sep 2002 00:47:05 -
@@ -122,14 +122,8 @@
 {
   if (CLASS_TYPE_P (TREE_TYPE (exp)))
 {
-  /* The backend should not be interested in the size of an expression
-of a type with both of these set; all copies of such types must go
-through a constructor or assignment op.  */
-  if (TYPE_HAS_COMPLEX_INIT_REF (TREE_TYPE (exp))
-  TYPE_HAS_COMPLEX_ASSIGN_REF (TREE_TYPE (exp)))
-   abort ();
-  /* This would be wrong for a type with virtual bases, but they are
-caught by the abort above.  */
+  /* This would be wrong for a type with virtual bases, but they should
+not get here.  */
   return CLASSTYPE_SIZE_UNIT (TREE_TYPE (exp));
 }
   else


To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message



Re: compiling kdelibs3 fails with -current's gcc 3.2

2002-09-02 Thread Alex Zepeda

On Mon, Sep 02, 2002 at 08:10:42PM -0400, Alexander Kabaev wrote:

 Have no idea what is your problem with linux_base, but rpm build fine
 here after one gets past __size_t and machine/types.h.

And how does one do that?

- alex

To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message



Re: sparc64 tinderbox failure

2002-09-02 Thread Peter Wemm

Alexander Kabaev wrote:
 On Mon, 2 Sep 2002 19:51:59 GMT
 Dag-Erling Smorgrav [EMAIL PROTECTED] wrote:
 
  === gnu/usr.bin/cc/cc1plus
  method.o: In function `use_thunk':
  method.o(.text+0x90c): undefined reference to `sparc_output_mi_thunk'
 
 Is this gcc 3.1 trying to build 3.2 or gcc 3.2 trying to build itself?
 Buildworld completes fine on panther, the only FreeBSD sparc64 machine I
 have access to.

This has got to be a local problem, perhaps where src/contrib/sparc/sparc.c
is out of sync on the builder machine.  This builds fine on
panther.freebsd.org.

Cheers,
-Peter
--
Peter Wemm - [EMAIL PROTECTED]; [EMAIL PROTECTED]; [EMAIL PROTECTED]
All of this is for nothing if we don't go to the stars - JMS/B5


To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message



Re: sparc64 tinderbox failure

2002-09-02 Thread Jake Burkholder

Apparently, On Mon, Sep 02, 2002 at 08:21:12PM -0700,
Peter Wemm said words to the effect of;

 Alexander Kabaev wrote:
  On Mon, 2 Sep 2002 19:51:59 GMT
  Dag-Erling Smorgrav [EMAIL PROTECTED] wrote:
  
   === gnu/usr.bin/cc/cc1plus
   method.o: In function `use_thunk':
   method.o(.text+0x90c): undefined reference to `sparc_output_mi_thunk'
  
  Is this gcc 3.1 trying to build 3.2 or gcc 3.2 trying to build itself?
  Buildworld completes fine on panther, the only FreeBSD sparc64 machine I
  have access to.
 
 This has got to be a local problem, perhaps where src/contrib/sparc/sparc.c
 is out of sync on the builder machine.  This builds fine on
 panther.freebsd.org.

Yeah, I just finished a native world here and have cross built several
since the compiler upgrade.

Jake

To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message



RE: aic7xxx kernel build failure...

2002-09-02 Thread Robert Watson

I ran into this, and found that re-running config and make depend made it
go away.  Didn't have time to do any other follow-up.

Robert N M Watson FreeBSD Core Team, TrustedBSD Projects
[EMAIL PROTECTED]  Network Associates Laboratories

On Mon, 2 Sep 2002, Long, Scott wrote:

  
  Is anyone else seeing something similar to the following?  I'm able to
  build world, but can't get this kernel build to budge.  I've not seen
  this error before so I'm a tad lost as to where to poke next.  -sc
 
 This is the third report of this that I've seen, and I'm completely
 baffled.  How old is your existing kernel and world?  If it's old,
 can you just build a new kernel (no modules) and try with that?
 
 Scott
 
  
  === aic7xxx
  === aic7xxx/aicasm
  make -f 
  /usr/src/sys/modules/aic7xxx/aicasm/../../../dev/aic7xxx/aicas
  m/Makefile  
  MAKESRCPATH=/usr/src/sys/modules/aic7xxx/aicasm/../../../dev/a
  ic7xxx/aicasm depend
  === aic7xxx/ahc
  @ - /usr/src/sys
  machine - /usr/src/sys/i386/include
  /usr/obj/usr/src/sys/DELLAPTOP/modules/usr/src/sys/modules/aic
  7xxx/ahc/../aicasm/aicasm  
  -I/usr/src/sys/modules/aic7xxx/ahc/../../../cam/scsi  
  -I/usr/src/sys/modules/aic7xxx/ahc/../../../dev/aic7xxx   
   -o aic7xxx_seq.h -r aic7xxx_reg.h   -p 
  aic7xxx_reg_print.c-i 
  /usr/src/sys/modules/aic7xxx/ahc/../../../dev/aic7xxx/aic7xxx_
  osm.h  
  /usr/src/sys/modules/aic7xxx/ahc/../../../dev/aic7xxx/aic7xxx.seq
  (null): Unable to malloc scope object
  *** Error code 70
  
  Stop in /usr/src/sys/modules/aic7xxx/ahc.
  *** Error code 1
  
  Stop in /usr/src/sys/modules/aic7xxx.
  *** Error code 1
  
  Stop in /usr/src/sys/modules.
  *** Error code 1
  
  Stop in /usr/obj/usr/src/sys/DELLAPTOP.
  *** Error code 1
  
  Stop in /usr/src.
  *** Error code 1
  
  Stop in /usr/src.
  
  
  
  -- 
  Sean Chittenden
  
 
 To Unsubscribe: send mail to [EMAIL PROTECTED]
 with unsubscribe freebsd-current in the body of the message
 


To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message



Re: sparc64 tinderbox failure

2002-09-02 Thread Mike Barcroft

Peter Wemm [EMAIL PROTECTED] writes:
 Alexander Kabaev wrote:
  On Mon, 2 Sep 2002 19:51:59 GMT
  Dag-Erling Smorgrav [EMAIL PROTECTED] wrote:
  
   === gnu/usr.bin/cc/cc1plus
   method.o: In function `use_thunk':
   method.o(.text+0x90c): undefined reference to `sparc_output_mi_thunk'
  
  Is this gcc 3.1 trying to build 3.2 or gcc 3.2 trying to build itself?
  Buildworld completes fine on panther, the only FreeBSD sparc64 machine I
  have access to.
 
 This has got to be a local problem, perhaps where src/contrib/sparc/sparc.c
 is out of sync on the builder machine.  This builds fine on
 panther.freebsd.org.

The source directory had some stale copies of files that weren't being
updated.  I fixed them, so hopefully the next build will work
correctly.

Best regards,
Mike Barcroft

To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message



Re: HEADS UP: rcNG is now the default

2002-09-02 Thread Gordon Tetlow

On Mon, Sep 02, 2002 at 10:30:19PM -0700, Gregory Neil Shapiro wrote:
 gordont There is one outstanding issue with the sendmail script that I'm working on
 gordont a solution for. In the general case it should work fine. If you set
 gordont sendmail_enable=NONE it will echo a benign warning about it being set
 gordont improperly.
 
 I've been discussing the issue with Mike Makonnen and we are going to use
 his idea of deprecating the use of NONE (with a warning) for -CURRENT and
 leaving it available in -STABLE.  At some point, NONE support will go
 away in 5.X.

I committed a script that pretty much works as the current sendmail support
does. I should have run it by you before, but I was in a hurry to get to a
barbecue and trying to keep the tree from breaking too badly. Please feel
free to rip apart my commit and make it closer to your satisfaction.

-gordon



msg42526/pgp0.pgp
Description: PGP signature


Re: GCC 3.2.1-pre and /usr/src/UPDATING

2002-09-02 Thread Garance A Drosihn

At 4:59 PM -0400 9/2/02, Mikhail Teterin wrote:
On Sunday 01 September 2002 05:58 pm, Alexander Kabaev wrote:
= GCC 3.2.1-pre is now in the tree. Please let me know if you
= see any problems recompiling your world/kernel.
=
= Remember to recompile your C++ ports. GCC 3.2 is not binary
= compatible with 3.1.

Most excellent! Thanks!

Someone needs to update /usr/src/UPDATING then, so people will
find out about this need to recompile their C++ world.  Who is
it that updates UPDATING these days?

Thanks for getting this update done, btw.  I was starting to worry
that we might not get this transition before 5.0-release, and this
transition would certainly be more painful if we tried to do
it *after* 5.0-release!

-- 
Garance Alistair Drosehn=   [EMAIL PROTECTED]
Senior Systems Programmer   or  [EMAIL PROTECTED]
Rensselaer Polytechnic Instituteor  [EMAIL PROTECTED]

To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message



Re: GCC 3.2.1-pre and /usr/src/UPDATING

2002-09-02 Thread Juli Mallett

* De: Garance A Drosihn [EMAIL PROTECTED] [ Data: 2002-09-02 ]
[ Subjecte: Re: GCC 3.2.1-pre and /usr/src/UPDATING ]
 Someone needs to update /usr/src/UPDATING then, so people will
 find out about this need to recompile their C++ world.  Who is
 it that updates UPDATING these days?

Whoever needs to.
-- 
Juli Mallett [EMAIL PROTECTED]   | FreeBSD: The Power To Serve
Will break world for fulltime employment. | finger [EMAIL PROTECTED]

To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message



Re: GCC 3.2.1-pre and /usr/src/UPDATING

2002-09-02 Thread M. Warner Losh

I just updated it for gcc 3.2.

Warner

To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message