>
> Otay, please tell me how to fix:
>
> ===> usr.sbin/ifmcstat
> cc -O -pipe -DINET6 -I/usr/obj/usr/src/i386/usr/include -c
> /usr/src/usr.sbin/ifmcstat/ifmcstat.c
> gzip -cn /usr/src/usr.sbin/ifmcstat/ifmcstat.8 > ifmcstat.8.gz
> /usr/src/usr.sbin/ifmcstat/ifmcstat.c: In function `main':
> /us
"David O'Brien" wrote:
> On Wed, Dec 29, 1999 at 11:37:18AM -0800, Amancio Hasty wrote:
> > This is the scoop.
> ..snip..
> > gcc -v
> > Using builtin specs.
> > gcc version 2.95.2 19991024 (release)
> ..snip..
> > Without -O or -O2 the program compiles okay.
>
> What other platforms w/gcc 2.95
> "David O'Brien" wrote:
> > On Wed, Dec 29, 1999 at 11:37:18AM -0800, Amancio Hasty wrote:
> > > This is the scoop.
> > ..snip..
> > > gcc -v
> > > Using builtin specs.
> > > gcc version 2.95.2 19991024 (release)
> > ..snip..
> > > Without -O or -O2 the program compiles okay.
> >
> > What othe
Greg Lehey wrote:
> On Wednesday, 29 December 1999 at 21:54:42 -0700, Russell L. Carter wrote:
> >
> > Otay, please tell me how to fix:
> >
> > ===> usr.sbin/ifmcstat
> > cc -O -pipe -DINET6 -I/usr/obj/usr/src/i386/usr/include -c
> > /usr/src/usr.sbin/ifmcstat/ifmcstat.c
> > gzip -cn /usr/src/us
FreeBSD mailing list wrote:
>
> i===> libroken
> cc -O -pipe -I/usr/src/kerberosIV/lib/libroken/../../../crypto/kerberosIV/include
>-I/usr/obj/usr/src/kerberosIV/lib/libroken/../../include
>-I/usr/src/kerberosIV/lib/libroken/../../../crypto/kerberosIV/lib/roken
>-I/usr/obj/usr/src/kerberosI
juan wrote:
>
> yacc -d /usr/src/usr.bin/colldef/parse.y
> *** Signal 12
>
> Stop in /usr/src/usr.bin/colldef.
Are you doing anything special? If not, try cleaning /usr/obj first and
make sure your source tree is ok.
--
Marcel Moolenaarmailto:[EMAIL PROTECTED]
SCC Inte
Greg Lehey wrote:
>
> > /usr/obj/usr/src/i386/usr/src/usr.bin/colldef created for
> > /usr/src/usr.bin/colldef
> > yacc -d /usr/src/usr.bin/colldef/parse.y
> > *** Signal 12
>
> This looks like you've updated your source tree and have not built a
> new kernel. Try the new kernel first, then the
> current's new ppp discards the "#0001"-part from my
> german telekom account and makes it impossible to
> connect to my provider.
This should work ok now. Sorry for the inconvenience.
> It worked ~ 2 weeks ago with current and works also
> in 3.4-Stable.
>
> Werner
--
Brian <[EMAIL PROTECT
Greg Lehey wrote in message ID
<[EMAIL PROTECTED]>:
> Again, news for me. You can stop a revive and restart it at a later
> time; the state information includes the revive pointer. But the only
> real answer to this one would be to see the statistics.
Well, I deleted the plex and tried again:
I just noticed that after my make installworld my postfix install was
"busted" ... I found out that apparently there has been installed a new
binary called mailwrapper that replaced my existing sendmail-symlinks
(created by postfix ports' make replace command) with new symlinks to
mailwrapper.
I
While compiling a new kernel after the KERNEL -=> _KERNEL change i found
out that /usr/src/sys/crypto/des/des_locl.h still has a KERNEL check
instead of _KERNEL which breaks kernel-building. I changed it myself and
kernel compiled cleanly again.
This is with crypto checked out from cvsup2.interne
Looks like the leasing stuff in NFS has a little buglet...
(This is with 4.0-CURRENT cvsup'd a few days before Christmas)
Fatal trap 12: page fault while in kernel mode
fault virtual address = 0x12ffa8d4
fault code = supervisor read, page not present
instruction pointer = 0x8
Related to my last post, the system came up and started to fsck. It
appears, with current, that the system will refuse to r/w mount root
even though the fsck has complete successfully. Is this an rc-file
out-of-date issue, or has something changed in the kernel.
Root is an 18G SCSI (da0s1a) on
On Thu, 30 Dec 1999, David Gilbert wrote:
> Related to my last post, the system came up and started to fsck. It
> appears, with current, that the system will refuse to r/w mount root
> even though the fsck has complete successfully. Is this an rc-file
> out-of-date issue, or has something chang
> "Bill" == Bill Fumerola <[EMAIL PROTECTED]> writes:
Bill> On Thu, 30 Dec 1999, David Gilbert wrote:
>> Related to my last post, the system came up and started to fsck.
>> It appears, with current, that the system will refuse to r/w mount
>> root even though the fsck has complete successfull
On Thu, 30 Dec 1999, David Gilbert wrote:
> Bill> Reboot. I don't know why it works, but it does. :->
>
> Right... I already knew that, but it's a manual reboot... and this is
> "suboptimal" (ie. requiring operator intervention).
Indeed.
--
- bill fumerola - [EMAIL PROTECTED] - BF1560 - compu
On Thu, Dec 30, 1999 at 11:14:58AM -0500, David Gilbert wrote:
> > "Bill" == Bill Fumerola <[EMAIL PROTECTED]> writes:
>
> Bill> On Thu, 30 Dec 1999, David Gilbert wrote:
> >> Related to my last post, the system came up and started to fsck.
> >> It appears, with current, that the system will
On Thu, 30 Dec 1999, Bill Fumerola wrote:
> On Thu, 30 Dec 1999, David Gilbert wrote:
>
> > Bill> Reboot. I don't know why it works, but it does. :->
> >
> > Right... I already knew that, but it's a manual reboot... and this is
> > "suboptimal" (ie. requiring operator intervention).
>
> Indeed
I was just wondering if anyone else was having a problem making the world
on -CURRENT right now? I don't remember the exact error I got because
I'm at work, and my machine is at home, but for the last 3 weeks whenever
I try to make world, it dies in a different place, I've tried every day,
so I'm
Last nite , I managed to compile all of XFree86 3.9.17 with no
compiler bugs from gcc.
/usr/local/bin/gcc -v
Reading specs from /usr/local/lib/gcc-lib/i386-portbld-freebsd4.0/2.96/specs
gcc version 2.96 19991110 (experimental)
Enjoy
--
Amancio Hasty
[EMAIL PROTECTED]
To Unsubsc
I build world this morning, and it built fine.
Patrick
- Original Message -
From: Kenneth Wayne Culver <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Thursday, December 30, 1999 12:23 PM
Subject: -CURRENT make world broken
> I was just wondering if anyone else was having a problem m
Last time I checked (I haven't moved to the latest gcc, so I can't
confirm it there), one significant difference between 'cc -E' and
/usr/libexec/cpp was that the latter would read from a pipe, whilst
the former wouldn't. This can make converting to 'cc -E' a
non-trivial exercise.
Peter
To Uns
On Mon, Dec 27, 1999 at 06:28:02PM -0600, Steve Price wrote:
> For some reason now I can't startx(1) as either myself or root.
> I type startx and the PAM auth routines loop forever printing
> out 'Password:'. I comment out the last two lines in /etc/pam.conf
> and I get an authentication failure
On Thu, 30 Dec 1999, Dave J. Boers wrote:
# I'm having the same problem. Cvsupped and recompiled -current just a few
# hours ago. Then I recompiled X 3.3.5 and installed it. Now I can't start X
# anymore either. Lines containing "Password:" just keep scrolling over my
# terminal. The password li
Here is the answer I was given by somebody on this list last week.
#/etc/pam.conf
# tricky tricky forgive me
xserver authsufficient pam_permit.so no_use
# If we don't match anything else, default to using getpwnam().
other authrequiredpam_unix.so
try_first
On Thu, Dec 30, 1999 at 04:43:47PM -0600, Thomas T. Veldhouse wrote:
> Here is the answer I was given by somebody on this list last week.
>
> #/etc/pam.conf
> # tricky tricky forgive me
> xserver authsufficient pam_permit.so no_use
> # If we don't match anything else, d
On Thu, 30 Dec 1999, Thomas T. Veldhouse wrote:
# Here is the answer I was given by somebody on this list last week.
#
# #/etc/pam.conf
# # tricky tricky forgive me
# xserver authsufficient pam_permit.so no_use
# # If we don't match anything else, default to using getp
Hey all,
I've got a laptop that's giving me all kinds of pccard headaches and I'd
like to get it back to -current from the begining of the month before I
was having these problems. Is there any reason why I couldn't make world
from some time around 12/8/99 on -current from yesterday evening? Woul
On Thu, 30 Dec 1999, Steve Price wrote:
> On Thu, 30 Dec 1999, Thomas T. Veldhouse wrote:
>
> # Here is the answer I was given by somebody on this list last week.
> #
> # #/etc/pam.conf
> # # tricky tricky forgive me
> # xserver authsufficient pam_permit.so no_use
> #
In article <[EMAIL PROTECTED]>, Bill Swingle
<[EMAIL PROTECTED]> wrote:
> I've got a laptop that's giving me all kinds of pccard headaches
> and I'd like to get it back to -current from the begining of the
> month before I was having these problems. Is there any reason why I
> couldn't make world
In article <[EMAIL PROTECTED]>, Peter
Jeremy <[EMAIL PROTECTED]> wrote:
> Last time I checked (I haven't moved to the latest gcc, so I can't
> confirm it there), one significant difference between 'cc -E'
> and /usr/libexec/cpp was that the latter would read from a pipe,
> whilst the former would
On Fri, 31 Dec 1999, Peter Jeremy wrote:
> Last time I checked (I haven't moved to the latest gcc, so I can't
> confirm it there), one significant difference between 'cc -E' and
> /usr/libexec/cpp was that the latter would read from a pipe, whilst
> the former wouldn't. This can make converting
I've been doing a lot of neatening up here, and one of the tasks was to
get both of the cdrom drives I have (one per machine) moved over so that
they are on the same machine. This was so I can use the one that's a
writer in conjuntion with a reader, and do duplication.
Anyhow, getting the kernel
The way certain devices, like cd with its monotonically increasing counter
where devices are probed in order and assigned device based on precedence
and not hardwiring/controller connection, work is consistent between
the kernel and MAKEDEV. If you have 2 cd devices, you have cd0 and cd1,
so MAKE
On Fri, 31 Dec 1999, Brian Fundakowski Feldman wrote:
> The way certain devices, like cd with its monotonically increasing counter
> where devices are probed in order and assigned device based on precedence
> and not hardwiring/controller connection, work is consistent between
> the kernel and MA
From: Chuck Robey <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Friday, December 31, 1999 6:29 AM
Subject: multiple cd devices
> Anyhow, getting the kernel to recognize cd1 was no problem, but getting
> /dev/MAKEDEV to do that was a hairy PITA. I couldn't locate, in either
> cd(4) or cd(9),
On Thu, Dec 30, 1999 at 12:23:35PM -0500, Kenneth Wayne Culver <[EMAIL PROTECTED]>
wrote:
> I was just wondering if anyone else was having a problem making the world
> on -CURRENT right now? I don't remember the exact error I got because
> I'm at work, and my machine is at home, but for the last
37 matches
Mail list logo
