On Sat, 8 Dec 2001 02:07:22 -0500, Jeremy Parker [EMAIL PROTECTED] wrote:
I have also experienced this issue, caused me a lot of trouble. The only
workaround I have figured out, is to bring up the interface with an IP
address, then start dhclient and it seems to work.
This is a very
The above message is what I get after upgrading from an August 7 to
an August 17 world/kernel and trying to run
linux-netscape47-communicator. Prior world/kernel combination worked
okay, there have been no changes to the kernel configuration (which
I can provide if required).
I noticed some
Niels Chr. Bank-Pedersen wrote:
I see this as well. Apparantly version 1.98 of
sys/kern/imgact_elf.c causes the string containing the path
to /compat/linux/lib/ld-2.1.2.so to be truncated. A quick
workaround is to symlink /co to /compat/linux/lib/ld-2.1.2.so .
Granted, it's a fix, but
Hmm, wait a minute here... path is a char*, so sizeof(path) will
always return the pointer size (4 on IA32), not what was allocated.
PYD
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message
Andrea Campi wrote:
Nope, UDMA33 (IBM-DARA-20600 on IBM Thinkpad).
Question: you built a world yesterday, but what world did you have BEFORE? I
mean, what matters is the kernel/world which was running while you were
compiling, was that recent ( 15 days old)? Are you seeing any lock reversal
Andrea Campi wrote:
I am noticing a severe slowdown on my -CURRENT system. It actually started
after Feb [3-5] changes in intrupt handling, but I didn't really notice
until I run a make world (which I delayed doing because of, well you guess,
the libc breakage). When I say severe I mean make
"Andrey A. Chernov" wrote:
Recent -current, 'make' fails ('make depend' works), I got this for
_every_ module:
ld -r -o 3dfx.kld tdfx_pci.o
/usr/libexec/elf/ld: cannot open tdfx_pci.o: No such file or directory
*** Error code 1
Stop in /usr/src/sys/modules/3dfx.
I think this might be
Julian Elischer wrote:
I used to use a Linksys Etherfast card
in my Inspiron, but I haven't used it for
a while. Today I tried to use it again
but it failed miserably..
Most probably you noticed this already, but (in src/UPDATING):
20001218:
Linksys Fast Ethernet PCCARD cards
John Indra wrote:
Dear all...
Recent -CURRENT make buildkernel target died with this message:
=== uscanner
cc -O -pipe -g -D_KERNEL -Wall -Wredundant-decls -Wnested-externs
-Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline
-Wcast-qual -fformat-extensions -ansi
Hmmm. It looks like there were other bits missing... the MELCO LUATX
entry was replaced in the last commit to usbdevs by two new entries,
LUATX1 and LUATX5, but if_aue.c was not modified to reflect this. You
need to do this manually.
If the goal is to make modifications in one place only (and
FWIW, it looks like VESA support broke after the SMPng commit. I used to run
my VTYs in VESA_800x600 mode, but just after the commit it hung the machine
(this is on a dual-processor system, with a Voodoo 5500).
PYD
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]]On
Since revision 1.5 of the above, my kernel is giving me a "too many dependant
configs (8)" when probing PNP resources.
Problem is, it looks like the SoundBlaster AWE 64 Gold advertises 8 different
PNP configurations (at least, that's what I got when i bumped MAXDEP to 16 and
rebooted in verbose
Could someone with a recent (ie 1 week) -CURRENT confirm whether they
have problems booting their system when setting allscreens_flags to
"VESA_800x600"? I have now verified the problem with two different
systems -- Compaq Professional Workstation 5100 (UP, Matrox Millenium
II) and Intel
The build is currently broken is /usr/src/usr.bin/xlint/llib, becasue lint
invokes ccp with the -undef option, which does not seem to be supported
anymore... any clues?
PYD@home
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Sorry if my previous message wasn't clear: the change of behaviour in cpp
breaks lint, hence the build.
FWIW, Mr. K posted a message on the 13th which already outlined the problem
with lint -- no answers so far.
-Original Message-
From: Pierre Y. Dampure [EMAIL PROTECTED]
To: [EMAIL
... it looks like only a small subset of the man pages for bind 8.2.2P5
(in /usr/src/contrib) gets installed. In particular, we are missing the
man page for nsupdate. Any reasons for not installing the whole bunch,
since we do install the binaries?
PYD
To Unsubscribe: send mail to [EMAIL
As stated. The Makefile calls for perl5, which is not available at that
time. Replacing perl5 by perl solves the problem.
Cheers,
PYD
To Unsubscribe: send mail to majord...@freebsd.org
with unsubscribe freebsd-current in the body of the message
Thomas T. Veldhouse wrote:
Are there any parts of world that are going to have a hard time
building under egcs because of this?
There would be if it had stay like that... the last changes from David :
cvs commit: src/gnu/lib/libstdc++/doc Makefile
Date: Mon, 5 Apr 1999
Jeroen Ruigrok/Asmodai wrote:
Those errors are still present.
Wrong:
[(dampurep)~/src]: cat
hello.cc // begin
program
#include iostream
using namespace std;
int main(int argc, char** argv) {
cout Hello World!!!\n endl;
Just succeeded a make world and kernel recompile. A round of applause
for David, please !
David: I'm starting with the PPro optimisations on right now.
PYD
To Unsubscribe: send mail to majord...@freebsd.org
with unsubscribe freebsd-current in the body of the message
I know this is the -current list, but... I haven't received a single
message on the cvs-all list since 11:57 GMT this morning, whilst a cvsup
just gave me a loads of commits today... this does not seem to be a
local issue, since I receive -current normally (or so it seems, at
least).
Any clues?
David O'Brien wrote:
Is anyone else experiencing this?
--
I did earlier on today; I removed /usr/src/gnu/usr.bin/cc/libgcc, and
all went fine. It might in fact have been a consequence of one of your
earlier commits (when you moved the Makefile to the Attic)?
Best Regards,
PYD
To
David O'Brien wrote:
Better yet, can we just run with this today instead of tomorrow?
Can someone with a FAST machine do a CVSup from Freefall and `make world'
to verify that it is not broken?
My machines are either EGCS'ified, 3.1-CURRENT, or take 5 hours to `make
world'.
--
--
David O'Brien wrote:
Can someone with a FAST machine do a CVSup from Freefall and `make world'
to verify that it is not broken?
CVSupped from 01:25 BST, make -j12 -DCLOBBER world on an SMP box, both
ELF and aout libraries generated, compile options -02 -m486, all clear.
The word is go.
PYD
Leif Neland wrote:
But fpsrvadm.exe just dumps core when make install runs.
So is current 4.0 and fp30 compatible?
Some mods were recently committed to cater for support of large (in
terms of RAM) systems; these break BSDI compatibility and might be the
root of your problems.
Best
25 matches
Mail list logo
