On Thu, 23 Aug 2012 17:23:59 +0100, Jamie Paul Griffin wrote:
> [ Lowell Gilbert wrote on Thu 23.Aug'12 at 10:28:47 -0400 ]
>
> > Jamie Paul Griffin writes:
> >
> > > [ Lowell Gilbert wrote on Thu 23.Aug'12 at 9:23:14 -0400 ]
> > >
> > >> antonin tessier writes:
> > >>
> > >> > I have a probl
[ Lowell Gilbert wrote on Thu 23.Aug'12 at 10:28:47 -0400 ]
> Jamie Paul Griffin writes:
>
> > [ Lowell Gilbert wrote on Thu 23.Aug'12 at 9:23:14 -0400 ]
> >
> >> antonin tessier writes:
> >>
> >> > I have a problem when I try to build my own kernel. I had never
> >> > got such a one; here is
Jamie Paul Griffin writes:
> [ Lowell Gilbert wrote on Thu 23.Aug'12 at 9:23:14 -0400 ]
>
>> antonin tessier writes:
>>
>> > I have a problem when I try to build my own kernel. I had never
>> > got such a one; here is my kernel configuration file and the
>> > building errors that it makes.
>
[ Lowell Gilbert wrote on Thu 23.Aug'12 at 9:23:14 -0400 ]
> antonin tessier writes:
>
> > I have a problem when I try to build my own kernel. I had never got such a
> > one; here is my kernel configuration file and the building errors that it
> > makes.
> Or just stay with GENERIC; most co
antonin tessier writes:
> I have a problem when I try to build my own kernel. I had never got such a
> one; here is my kernel configuration file and the building errors that it
> makes.
You left out some devices that are required by other devices in your
configuration. for a start, it looks li
Hi,
I have a problem when I try to build my own kernel. I had never got such a one;
here is my kernel configuration file and the building errors that it makes.
"#device tun # Packet tunnel.
device pty # BSD-style compatibility pseudo ttys
device
On Mon, 20 Aug 2012 09:46:30 -0400, Robert Huff wrote:
>
> Polytropon writes:
>
> > > Very good point! I'd clear the /usr/src/obj directory as pointed out,
> > > then build a generic kenel, install it and boot from it. Then you
> > > know you've got a working kernel to fall back on.
> >
> >
Polytropon writes:
> > Very good point! I'd clear the /usr/src/obj directory as pointed out,
> > then build a generic kenel, install it and boot from it. Then you
> > know you've got a working kernel to fall back on.
>
> You could then make a copy of that kernel, e. g. from its initial
> i
On Mon, 20 Aug 2012 14:13:44 +0100, Jamie Paul Griffin wrote:
> == Michael Powell wrote on Sun 19.Aug'12 at 19:43:14 -0400 ==
>
> > Keep in mind whenever you install a new kernel your present kernel (and its
> > matching modules) get moved to kernel.old. What this means is that the
> > GENERIC y
== Jerry wrote on Mon 20.Aug'12 at 8:11:17 -0400 ==
> I inquired several years ago about the possibility of changing the
> renaming format into something like: "kernel_##_YY-MM-DD.old". The "##"
> would be incremented with each successive build on a given day. I
> thought it would alleviate jus
== Michael Powell wrote on Sun 19.Aug'12 at 19:43:14 -0400 ==
> Keep in mind whenever you install a new kernel your present kernel (and its
> matching modules) get moved to kernel.old. What this means is that the
> GENERIC you have with a base install will be moved to kernel.old and can be
> us
On Sun, 19 Aug 2012 19:43:14 -0400
Michael Powell articulated:
{snip}
> Keep in mind whenever you install a new kernel your present kernel
> (and its matching modules) get moved to kernel.old. What this means
> is that the GENERIC you have with a base install will be moved to
> kernel.old and can
antonin tessier wrote:
>
> Hi,
>
> I have a problem when I try to build my own kernel. I had never got such a
> one; here is my kernel configuration file and the building errors that it
> makes.
>
[snip]
>
> "# make kernel KERNCONF=GOLLUM
>
> MAKE=make sh /usr/src/sys/conf/newvers.sh GOLLUM
Hi,
I have a problem when I try to build my own kernel. I had never got such a one;
here is my kernel configuration file and the building errors that it makes.
"#device tun # Packet tunnel.
device pty # BSD-style compatibility pseudo ttys
device
At 02:11 PM 1/4/2006, Nguyen Danh Hieu wrote:
Could someone tell me what's wrong with my configuration plz here
are erros with command "make"
You have the wlan device commented out but the ural devices requires it.
You also have the da device commented out, but there are other
devices that r
Could someone tell me what's wrong with my configuration plz
here are erros with command "make"
linking kernel.debug
if_ural.o(.text+0x3bb): In function `ural_attach':
../../../dev/usb/if_ural.c:458: undefined reference to `ieee80211_ieee2mhz'
if_ural.o(.text+0x3ef):../../../dev/usb/if_ural.c:463
On Fri, 8 Aug 2003 09:49:08 -0700
Kent Stewart <[EMAIL PROTECTED]> wrote:
|On Friday 08 August 2003 07:10 am, mess-mate wrote:
|> Hi,
|> An error occurs when building my kernel :(
|> What does this mean ?? :
|
|That you deleted options without reading what is required. Read the
|requirements for
Thanks Marc.
Next time I'll read the config file better.
A+
mess-mate
On Fri, 8 Aug 2003 14:59:46 -0700
Mark Woodson <[EMAIL PROTECTED]> wrote:
|On Friday 08 August 2003 12:47 pm, mess-mate wrote:
|> |> umass.o: In function `umass_cam_quirk_cb':
|> |> umass.o(.text+0x21bb): undefined reference to
On Fri, Aug 08, 2003 at 09:47:49PM +0200, mess-mate wrote:
> |That you deleted options without reading what is required. Read the
> |requirements for umass in the USB section and reactivate the required
> |pieces.
> |
> |Kent
> Thanks for your help.
> Problem semi-solved. Disabled 'umass' in th
On Friday 08 August 2003 07:10 am, mess-mate wrote:
> Hi,
> An error occurs when building my kernel :(
> What does this mean ?? :
That you deleted options without reading what is required. Read the
requirements for umass in the USB section and reactivate the required
pieces.
Kent
>
> linking k
On Friday 08 August 2003 12:47 pm, mess-mate wrote:
> |> umass.o: In function `umass_cam_quirk_cb':
> |> umass.o(.text+0x21bb): undefined reference to `xpt_done'
> |> *** Error code 1
> |>
> |> Thanks for your help.
> |> mess-mate
>
> Thanks for your help.
> Problem semi-solved. Disabled 'umass' in
Hi,
An error occurs when building my kernel :(
What does this mean ?? :
linking kernel
umass.o: In function `umass_cam_attach_sim':
umass.o(.text+0x17c7): undefined reference to `cam_simq_alloc'
umass.o(.text+0x1818): undefined reference to `cam_sim_alloc'
umass.o(.text+0x1827): undefined referenc
Try:
# cd /usr/src
# make buildkernel KERNCONF=YOURKERNEL
# make installkernel KERNCONF=YOURKERNEL
- Original Message -
From: "Paul &" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Sunday, June 22, 2003 8:31 PM
Subject: Kernel building
> I'm tryi
On Sun, Jun 22, 2003 at 07:31:54PM -0400, Paul & wrote:
> I'm trying to build a custom kernel that I can eventually include a device
> for a (built in the mother board) sound controller.
>
> I tried several time and added back some devices which I think I don't need
> just to see if the kernel
I'm trying to build a custom kernel that I can eventually include a device
for a (built in the mother board) sound controller.
I tried several time and added back some devices which I think I don't need
just to see if the kernel will make, however, it doesn't.
I followed the directions in th
On Sun, Nov 03, 2002 at 11:03:17PM -0600, Ryan Sommers wrote:
> I'm assuming it's possible to build a kernel for a different computer
> then it's compiled on as long as they are the same architecture. How do
> I go about compiling my kernel for my laptop on my desktop? First I
> don't think the lap
I'm assuming it's possible to build a kernel for a different computer
then it's compiled on as long as they are the same architecture. How do
I go about compiling my kernel for my laptop on my desktop? First I
don't think the laptop could hold the source and more importantly I
think the 850 box wil
27 matches
Mail list logo