linuxconsole-dev

Ruby cvs 2.6.12 did not compile

[Helge H. <hel...@ai...>]

Checked out ruby cvs, saw that it was 2.6.12, copied it over a 2.6.12
source tree, got this upon compile:

  CHK     include/linux/version.h
make[1]: `arch/x86_64/kernel/asm-offsets.s' is up to date.
  CHK     include/linux/compile.h
  CHK     usr/initramfs_list
  CC      drivers/char/decvte.o
drivers/char/decvte.c: In function `set_mode':
drivers/char/decvte.c:514: error: incompatible type for argument 1 of 
`set_kbd_mode'
drivers/char/decvte.c:516: error: incompatible type for argument 1 of 
`clr_kbd_mode'
drivers/char/decvte.c:547: error: incompatible type for argument 1 of 
`set_kbd_mode'
drivers/char/decvte.c:549: error: incompatible type for argument 1 of 
`clr_kbd_mode'
drivers/char/decvte.c:568: error: incompatible type for argument 1 of 
`set_kbd_mode'
drivers/char/decvte.c:570: error: incompatible type for argument 1 of 
`clr_kbd_mode'
drivers/char/decvte.c:596: error: incompatible type for argument 1 of 
`set_kbd_mode'
drivers/char/decvte.c:598: error: incompatible type for argument 1 of 
`clr_kbd_mode'
drivers/char/decvte.c: In function `vte_ris':
drivers/char/decvte.c:999: error: incompatible type for argument 1 of 
`set_kbd_mode'
drivers/char/decvte.c:1000: error: incompatible type for argument 1 of 
`clr_kbd_mode'
drivers/char/decvte.c:1001: error: incompatible type for argument 1 of 
`clr_kbd_mode'
drivers/char/decvte.c:1002: error: incompatible type for argument 1 of 
`clr_kbd_mode'
drivers/char/decvte.c: In function `terminal_emulation':
drivers/char/decvte.c:1122: error: incompatible type for argument 1 of 
`get_kbd_mode'
drivers/char/decvte.c:1296: error: incompatible type for argument 1 of 
`set_kbd_mode'
drivers/char/decvte.c:1300: error: incompatible type for argument 1 of 
`clr_kbd_mode'
make[2]: *** [drivers/char/decvte.o] Error 1
make[1]: *** [drivers/char] Error 2
make: *** [drivers] Error 2

Re: Ruby cvs 2.6.12 did not compile

[James S. <jsi...@ww...>]

> Checked out ruby cvs, saw that it was 2.6.12, copied it over a 2.6.12
> source tree, got this upon compile:

I just checked in the fix. Give it a try now.

Re: Ruby cvs 2.6.12 did not compile

[Hugo V. <hvw...@ya...>]

--- Helge Hafting <hel...@ai...> wrote:

> Checked out ruby cvs, saw that it was 2.6.12, 

<snip>

Did you get that with:

cvs -z3
-d:pserver:ano...@cv...:/cvsroot/linuxconsole
 co ruby

H.


		
____________________________________________________ 
Yahoo! Sports 
Rekindle the Rivalries. Sign up for Fantasy Football 
http://football.fantasysports.yahoo.com

Re: Ruby cvs 2.6.12 did not compile

[James S. <jsi...@ww...>]

> > Checked out ruby cvs, saw that it was 2.6.12, 
> 
> <snip>
> 
> Did you get that with:
> 
> cvs -z3
> -d:pserver:ano...@cv...:/cvsroot/linuxconsole
>  co ruby

I did a checkout with my user name.

Re: Ruby cvs 2.6.12 did not compile

[Hugo V. <hvw...@ya...>]

--- Helge Hafting <hel...@ai...> wrote:

> Checked out ruby cvs, saw that it was 2.6.12, copied
> it over a 2.6.12
> source tree, got this upon compile:
> 
>   CHK     include/linux/version.h
> make[1]: `arch/x86_64/kernel/asm-offsets.s' is up to
> date.
>   CHK     include/linux/compile.h
>   CHK     usr/initramfs_list
>   CC      drivers/char/decvte.o
> drivers/char/decvte.c: In function `set_mode':
> drivers/char/decvte.c:514: error: incompatible type

If to get 2.6.12 you do:
cvs -z3
-d:pserver:ano...@cv...:/cvsroot/linuxconsole
 co ruby

Then I got one step further:

  CC      drivers/char/vc_screen.o
drivers/char/vc_screen.c: In function `vcs_read':
drivers/char/vc_screen.c:168: error: `BUF_SIZE'
undeclared (first use in this function)
drivers/char/vc_screen.c:168: error: (Each undeclared
identifier is reported only once
drivers/char/vc_screen.c:168: error: for each function
it appears in.)
drivers/char/vc_screen.c: In function `vcs_write':
drivers/char/vc_screen.c:325: error: `BUF_SIZE'
undeclared (first use in this function)
make[3]: *** [drivers/char/vc_screen.o] Error 1

H



		
____________________________________________________ 
Yahoo! Sports 
Rekindle the Rivalries. Sign up for Fantasy Football 
http://football.fantasysports.yahoo.com

Re: Ruby cvs 2.6.12 did not compile

[Mario S. <mar...@we...>]

Hello

I get the error, with cvs-Ruby over a 2.6.12.2, config copied from=20
2.6.11-mm1-ruby:

  CC      drivers/char/vc_screen.o
drivers/char/vc_screen.c: In Funktion =C2=BBvcs_read=C2=AB:
drivers/char/vc_screen.c:168: error: `BUF_SIZE' undeclared (first use in th=
is=20
function)
drivers/char/vc_screen.c:168: error: (Each undeclared identifier is reporte=
d=20
only once
drivers/char/vc_screen.c:168: error: for each function it appears in.)
drivers/char/vc_screen.c: In Funktion =C2=BBvcs_write=C2=AB:
drivers/char/vc_screen.c:325: error: `BUF_SIZE' undeclared (first use in th=
is=20
function)
make[2]: *** [drivers/char/vc_screen.o] Fehler 1
make[1]: *** [drivers/char] Fehler 2
make: *** [drivers] Fehler 2

mfg
Mario
=2D-=20
mar...@we... ( Auch verschluesselt )=20
http://www.marioscheel.de ( Mit Public-Key )
ICQ# 223567831

Re: Ruby cvs 2.6.12 did not compile

[Hugo V. <hvw...@ya...>]

--- Mario Scheel <mar...@we...> wrote:

> Hello
> 
> I get the error, with cvs-Ruby over a 2.6.12.2,
> config copied from 
> 2.6.11-mm1-ruby:
> 
>   CC      drivers/char/vc_screen.o
> drivers/char/vc_screen.c: In Funktion »vcs_read«:
> drivers/char/vc_screen.c:168: error: `BUF_SIZE'
> 

Same here. In all previous versions that variable was
called CON_BUF_SIZE. What happened. Who knows.

H





		
____________________________________________________ 
Yahoo! Sports 
Rekindle the Rivalries. Sign up for Fantasy Football 
http://football.fantasysports.yahoo.com

Re: Ruby cvs 2.6.12 did not compile

[Hugo V. <hvw...@ya...>]

--- Mario Scheel <mar...@we...> wrote:

> Hello
> 
> I get the error, with cvs-Ruby over a 2.6.12.2,
> config copied from 
> 2.6.11-mm1-ruby:
> 
>   CC      drivers/char/vc_screen.o
> drivers/char/vc_screen.c: In Funktion »vcs_read«:
> drivers/char/vc_screen.c:168: error: `BUF_SIZE'
> undeclared (first use in this 
> function)

And if you change BUF_SIZE to CON_BUF_SIZE it compiles
but you get the next one:

drivers/char/vt.c: In function `vc_disallocate':
drivers/char/vt.c:1042: error: `screenbuf' undeclared
(first use in this function)

H




		
__________________________________ 
Do you Yahoo!? 
Make Yahoo! your home page 
http://www.yahoo.com/r/hs

Re: Ruby cvs 2.6.12 did not compile

[Stefan N. <neu...@tr...>]

Hugo Vanwoerkom <hvw...@ya...> writes:

> --- Mario Scheel <mar...@we...> wrote:
>
>> Hello
>>=20
>> I get the error, with cvs-Ruby over a 2.6.12.2,
>> config copied from=20
>> 2.6.11-mm1-ruby:
>>=20
>>   CC      drivers/char/vc_screen.o
>> drivers/char/vc_screen.c: In Funktion =BBvcs_read=AB:
>> drivers/char/vc_screen.c:168: error: `BUF_SIZE'
>> undeclared (first use in this=20
>> function)
>
> And if you change BUF_SIZE to CON_BUF_SIZE it compiles
> but you get the next one:
>
> drivers/char/vt.c: In function `vc_disallocate':
> drivers/char/vt.c:1042: error: `screenbuf' undeclared
> (first use in this function)

Just a guess screenbuf is vc->vc_screenbuf, but then you get:

  CC      drivers/char/vt.o
drivers/char/vt.c: In function `take_over_console':
drivers/char/vt.c:1912: error: structure has no member named `vc_size_rows'
make[2]: *** [drivers/char/vt.o] Error 1
make[1]: *** [drivers/char] Error 2
make: *** [drivers] Error 2

Changing vc_size_rows to vc_size_row makes things compilable, don't
know if it working with the changes...

Re: Ruby cvs 2.6.12 did not compile

[Daniel S. <har...@se...>]

Am Samstag, den 02.07.2005, 18:11 +0200 schrieb Stefan Neuwirth:
> Just a guess screenbuf is vc->vc_screenbuf, but then you get:
> 
>   CC      drivers/char/vt.o
> drivers/char/vt.c: In function `take_over_console':
> drivers/char/vt.c:1912: error: structure has no member named `vc_size_rows'
> make[2]: *** [drivers/char/vt.o] Error 1
> make[1]: *** [drivers/char] Error 2
> make: *** [drivers] Error 2
> 
> Changing vc_size_rows to vc_size_row makes things compilable, don't
> know if it working with the changes...

I had to fix more things (checked out CVS today) to have the kernel
compile. I found that I had to change "pci_name_bus(name, bus)" to
"pci_proc_domain(bus)" in drivers/pci/proc.c, add a forward declaration
of "struct input_handle *input_find_handle(char *phys_descr);" to
drivers/char/vt_proc.c and to change every occurence of "vt_kmalloced"
to "kmalloced".

Still, I get an error very early when booting. I cannot capture the full
output; the trace looks like this:

ret_from_fork
init
spawn_ksoftirqd

The diff between 2.6.12.2 and the CVS is attached including the compile
fixes. Does anybody have an idea of what is wrong?

Daniel

Re: Ruby cvs 2.6.12 did not compile

[Stefan N. <neu...@tr...>]

Daniel Sobe <har...@se...> writes:

> Am Samstag, den 02.07.2005, 18:11 +0200 schrieb Stefan Neuwirth:
>> Just a guess screenbuf is vc->vc_screenbuf, but then you get:
>> 
>>   CC      drivers/char/vt.o
>> drivers/char/vt.c: In function `take_over_console':
>> drivers/char/vt.c:1912: error: structure has no member named `vc_size_rows'
>> make[2]: *** [drivers/char/vt.o] Error 1
>> make[1]: *** [drivers/char] Error 2
>> make: *** [drivers] Error 2
>> 
>> Changing vc_size_rows to vc_size_row makes things compilable, don't
>> know if it working with the changes...
>
> I had to fix more things (checked out CVS today) to have the kernel
> compile. I found that I had to change "pci_name_bus(name, bus)" to
> "pci_proc_domain(bus)" in drivers/pci/proc.c, add a forward declaration
> of "struct input_handle *input_find_handle(char *phys_descr);" to
> drivers/char/vt_proc.c and to change every occurence of "vt_kmalloced"
> to "kmalloced".
>
> Still, I get an error very early when booting. I cannot capture the full
> output; the trace looks like this:
>
> ret_from_fork
> init
> spawn_ksoftirqd
>
> The diff between 2.6.12.2 and the CVS is attached including the compile
> fixes. Does anybody have an idea of what is wrong?

I recently switched to kernel 2.6.13-rc1-mm1-ruby (compiles an runs
without any problem). Due to my very special needs this kernel is the
best kernel I've seen in 2.6.x. But still a lot of problems, for
example matroxfb and framebuffer console.

  Stefan