Hi all,
I've just upgraded my system to today's -CURRENT (I was running a
-CURRENT from April 2001). Although I encountered some problems, the
UPDATING file got me through (I love the way FreeBSD documents stuff)
and my system is running fine (background fsck, great!) except for my
PCMCIA CDROM p
WARNING!
This mail is generated automatically by virus-scanning software.
There was virus found in one or more attachment in e-mail sent by:
Peter Wagner <[EMAIL PROTECTED]> at date: Thu, 2 Nov 2000 09:34:34 - ,
with subject "US PRESIDENT AND FBI SECRETS =PLEASE VISIT => (http://WWW.2600.CO
I have a system running
FreeBSD 9.3-RELEASE #0 r268512: Fri Jul 11 03:13:02 UTC 2014 i386
I have updated the source tree to CURRENT r273542.
If I build "make buildworld" for the GENERIC kernel and no
make.conf or src.conf, it succeeds.
If I use an empty make.conf
Ian Lepore writes:
> >I have a system running
> >
> > FreeBSD 9.3-RELEASE #0 r268512: Fri Jul 11 03:13:02 UTC 2014 i386
> >
> >I have updated the source tree to CURRENT r273542.
> >If I build "make buildworld" for the GENERIC kernel and no
> > make.conf or src.conf, it succee
Putting TARGET/TARGET_ARCH on the command line didn't help.
Adding " -j 1 " to make - did.
I am now doing "make buildkernel" with TARGET/TARGET_ARCH on
the command line. For installkernel, do I need to use them also,
or will it magically know where to look?
Respe
roberth...@rcn.com writes:
> I am now doing "make buildkernel" with TARGET/TARGET_ARCH on
> the command line. For installkernel, do I need to use them also,
> or will it magically know where to look?
Kernel built.
However:
huff@>> make installkernel
ERROR: No kernel "G
David Wolfskill writes:
> >Kernel built.
> >However:
> >
> > huff@>> make installkernel
> > ERROR: No kernel "GENERIC" to install.
> > *** Error code 1
> > ...
> >I believe there is a kernel in
> > /usr/obj/amd64.amd64/usr/src/sys/GENERIC, and world in
> > /usr/obj/amd64.a
David Wolfskill writes:
> > > I believe that the cited message refers to the kernel configuration
> > > file, which is expected to be in sys/amd64/conf/GENERIC within the
> > > src hierarchy.
> >
> >Like this:
> >
> > huff@>> pwd
> > /usr/src
> > huff@>> dir sys/amd64/conf/GENER
Garrett Cooper writes:
> The message is telling you (indirectly) that you need to run make
> buildworld successfully first?
Recapping:
Current system:
FreeBSD 9.3-RELEASE #0 r268512: Fri Jul 11 03:13:02 UTC 2014 i386
Source tree at CURRENT/r273626.
No make.c
Fixed by scrubbing 9.3 and installing 10.1-RC3, which solved a
couple of other issues.
Respectfully,
Robert Huff
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-cu
Chris H writes:
> Working on a recent 11-CURRENT install
> (11-CURRENT #1 amd64 r274134 Nov 5 12:56:14 PST 2014)
> svn info /usr/ports Revision: 372176
>
> Given the above, and the fact that I have installed lang/gcc-48.
> Is there any reason that any port wanting to include xmmintrin.h
>
Dimitry Andric writes:
> >- Could a "MK_CLANG_ALL_TARGETS" or something similar option be
> > added to src.opts.mk to fine tune this process for those of us who
> > don't want to build a cross-compile toolchain every iteration for our
> > target MACHINE/MACHINE_ARCH?
>
> I would be fin
Hello:
I finally get to update a system from:
FreeBSD 11.0-RC2 #0 r304729: Wed Aug 24 06:59:03 UTC 2016 amd64
to -CURRENT.
After reading src/UPDATING, I understand everything (I think)
_except_:
20170311:
The old drm (sys/dev/drm/) drivers for i915 and radeon hav
Jakub Lach writes:
> Are you sure you are not using drm2 already? I would check
> with kldstat.
Ckecked; it's there.
> The message in UPDATING is about removing
> old code from the tree.
Maybe ... but this is one of those things that (in my
experience) either Just Work or
Hello:
I am trying to update a system from:
FreeBSD 11.0-RC2 #0 r304729: Wed Aug 24 06:59:03 UTC 2016 amd64
to:
huff@> svn info
Path: .
Working Copy Root Path: /usr/src
URL: http://svn.freebsd.org/base/head
Relative URL: ^/head
Repository Root: http://svn.freebsd.org/base
Repos
Wolfram Schneider writes:
> I upgraded a machine from 11-stable to 12-current. The /usr/obj tree
> is now 11GB huge:
>
> FreeBSD 12-current
> $ du -hs /usr/obj
> 11G /usr/obj
>
> on FreeBSD 11-stable it was less the size:
> $ du -hs /usr/obj
> 5.6G /usr/obj
Mine - also 12-cu
Shawn Webb writes:
> > > > It looks like evdev support in the kernel is broken.
> > > > sys/dev/kbdmux/kbdmux.c contains various unresolved symbols to
> > > > different evdev-related symbols.
> > > >
> > > > I have the following options in my kernel config:
> > > >
> > > > options
17 matches
Mail list logo
