I see that the /modules directory is empty in the latest 4.x snaps.
John
--
John Hay -- [EMAIL PROTECTED]
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-stable" in the body of the message
On Mon, Jul 17, 2000 at 07:44:56PM -0700, Richard Stanaford wrote:
> Recently.
>
> I did a successful upgrade from 4.0-RELEASE to STABLE on the DX4/100 just last
> week. The changes to binutils had been committed for some time I believe.
After watching days of this from various people, I decide
- Original Message -
From: "Chad R. Larson" <[EMAIL PROTECTED]>
| You mean, no problems you've noticed. You may very well be right
| about no problems, but please be aware that Windows will not
| detect/report many errors that will trip up FreeBSD. Quiet data
| corruption is the sometim
>The 'hack' restores general functionality.
the hack brings a buggy behavior back. xbone relied upon
the buggy behavior.
>The current KAME code does not support multiple tunnels between two
>hosts on a single interface. This restores that capability, which is
>required for sett
On Mon, Jul 17, 2000 at 05:20:29PM -0700, Chad R. Larson wrote:
> Could someone please offer a brief explanation about the nature of
> the change to the binutils?
Binutils 2.10.0 now accepts (read requires) proper AT&T ASM syntax.
Previous versions required a bastardized syntax that was neither p
Jun-ichiro itojun Hagino wrote:
>
> >> do you have xbone userland tool in freebsd master repository?
> >> i believed not. xserver is officially supported by freebsd and
> >> userland tools are in the tree. the situation looks different for me.
> >The xbone port has been submitted to the ports
[EMAIL PROTECTED] wrote:
>
> >> is there any reason why the (misnamed, but that's another issue) XBONEHACK
> >> option was eliminated during the recent KAME/FreeBSD-stable merge? (File
> >> /usr/src/sys/net/if_gif.c.) It took us a while to get this added to KAME,
> >> and we'd really like to se
I sent this to the ports mailing list but didn't get a reply. I'll try
here...
Has anybody had any success with building the XFree86 4.0.1 port (on
4-Stable, although I doubt that it makes an difference)? I've tried a few
times and I always get:
don't know how to make: clean
in the "doc"
Richard Stanaford wrote:
>
> --- Kent Stewart <[EMAIL PROTECTED]> wrote:
>
> > > I am doing this on a 336MHz Celeron. I did a clean upgrade to STABLE from
> > > 4.0-RELEASE on my DX4/100 box and I did use the quotes without difficulty.
> >
> > Recently or before 7 July. My first build was on
On Mon, 17 Jul 2000, Rodney W. Grimes wrote:
> >
> > --- David Uhring <[EMAIL PROTECTED]> wrote:
> > > On Mon, 17 Jul 2000, Walter Campbell wrote:
> >
> > > You might also check the cpu temperature during the compile. Using a
> > > K6-3/450,
> > > my cpu cooler was getting quite hot to the touc
--- Kent Stewart <[EMAIL PROTECTED]> wrote:
> > I am doing this on a 336MHz Celeron. I did a clean upgrade to STABLE from
> > 4.0-RELEASE on my DX4/100 box and I did use the quotes without difficulty.
>
> Recently or before 7 July. My first build was on a P-II 400 and it is
> only slightly fast
--- "Rodney W. Grimes" <[EMAIL PROTECTED]> wrote:
>
> Becareful, you may have eliminated your heat problem, but you have now
> created an excelent static electricity generator. High volumes of air
> moving over just about anything will build static at an alarming rate!
One word... Febreeze
Richard Stanaford wrote:
>
> --- Kent Stewart <[EMAIL PROTECTED]> wrote:
>
> > Just to make sure that from /usr/src you are doing a
> >
> > make installkernel KERNEL=NOVA
>
> I may have used ..
>
> make buildkernel KERNEL="NOVA"
The quotes are evil. One my first kernel I left if buildkernel
--- Kent Stewart <[EMAIL PROTECTED]> wrote:
> Just to make sure that from /usr/src you are doing a
>
> make installkernel KERNEL=NOVA
I may have used ..
make buildkernel KERNEL="NOVA"
If the quotes are evil I would have expected it to make more than just 'as'
mad. I'm going to CVSup, bu
Hello everyone,
I saw a message posted earlier regarding assembler problems while compiling
BIOS code either during a kernel build or a Buildworld. I too am having such a
problem.
I was attempting to build a kernel and got some spam regarding invalid
assembler instructions while dealing with a
Kent Stewart wrote:
> I just finish cvsup'ing and have completed a buildworld and
> buildkernel without any problems. Did you cvsup'ed such that you have
> the crypto files since they are part of src-all now days.
Of course this was the problem. Thanks, Kent!
--
Lars Eggert <[EMAIL PROTECTED]>
Kris Kennaway wrote:
> > is there any reason why the (misnamed, but that's another issue) XBONEHACK
> > option was eliminated during the recent KAME/FreeBSD-stable merge? (File
> > /usr/src/sys/net/if_gif.c.) It took us a while to get this added to KAME,
> > and we'd really like to see it merged i
On Mon, 17 Jul 2000, Lars Eggert wrote:
> Building a kernel (config file attached) on a freshly updated -stable
> system fails with:
Did you cvsup the src-sys-crypto collection?
Kris
--
In God we Trust -- all others must submit an X.509 certificate.
-- Charles Forsythe <[EMAIL PROTECTED]>
On Mon, 17 Jul 2000, Lars Eggert wrote:
> Hi,
>
> is there any reason why the (misnamed, but that's another issue) XBONEHACK
> option was eliminated during the recent KAME/FreeBSD-stable merge? (File
> /usr/src/sys/net/if_gif.c.) It took us a while to get this added to KAME,
> and we'd really li
On Mon, 17 Jul 2000, Adam wrote:
> 4.0 cd subscription:$25
> Time spent installing: 10-15 min
> cvsup to -stable: ~10-15 min
> buildworld: 1.5 hours
> Reading UPDATING: free
> re-reading e
Lars Eggert wrote:
>
> Building a kernel (config file attached) on a freshly updated -stable
> system fails with:
>
> cc -c -O3 -pipe -funroll-loops -fomit-frame-pointer -fno-builtin -Wall
> -Wredundant-decls -Wnested-externs -Wstrict-prototypes
> -Wmissing-prototypes -Wpointer-arith -Winline
Rene de Vries wrote:
> I've seen problems during an installworld when using -j x (where x > 1). I
> only do a buildworld using -j 4 and then use ordinary make (without -j)
for
> the install. A -j 5 will sometimes try to create files in a directory one
of
> the other make sub processes still has t
On Mon, Jul 17, 2000 at 12:55:57PM +1000, [EMAIL PROTECTED] wrote:
> The box either reboots part-way through, or I see something like this :
The machine either has a serious problem, or your /usr/src/* is not
consistent with the bits that make up RELENG_4 (4-STABLE), or your
/usr/obj/* contains c
On Mon, Jul 17, 2000 at 10:58:06AM -0400, Keith Mackay wrote:
> Is there a known issue in bioscall.s?
Yes, it has been documented all over the place in this mailing list.
It is also documented in /usr/src/UPDATING.
You should review the expectations of running -STABLE and consider if you
are bet
Philippe Le Berre wrote:
> After being through the high numbers of emails on the new *build*
> procedure, I still haven't see any hint on how to handle the make
> installworld remotely. Can I do it without the shutdown? Can I remotely
log
> on *shutdown* system ? Do I have to fly to the box?
>
> T
On Mon, 17 Jul 2000, Walter Campbell wrote:
> > The FreeBSD install I'm using had previously been running on a generic Dell
> > Pentium 200 and lived through a half-dozen buildworlds without breaking.
> >
> > Since I haven't seen a anyone else's world breaking this way, I'm assuming
> > that this
When I got upto the step "cd /usr/src/sys/modules"
"make install"
I got this error:
boxster:/usr/src/sys/modules# make
===> aha
Warning: Object directory not changed from original
/usr/src/sys/modules/aha
make: don't know how to make opt_cam.h. Stop
*** Error code 2
Stop.
boxster:/usr/src/sys/mod
On Mon, Jul 17, 2000 at 01:12:06PM -0700, Philippe Le Berre wrote:
> After being through the high numbers of emails on the new *build*
> procedure, I still haven't see any hint on how to handle the make
> installworld remotely. Can I do it without the shutdown? Can I remotely log
> on *shutdown
28 matches
Mail list logo
