rsync kernel compile fails

rsync kernel compile fails

[Brad Midgley]

is the rsync kernel supposed to be working? i haven't changed my config
but it fails to compile:

make[3]: Entering directory `/mnt/extra/linux-imac/drivers/usb'
gcc -D__KERNEL__ -I/usr/src/linux/include -Wall -Wstrict-prototypes -O2
-fomit-frame-pointer -D__powerpc__ -fsigned-char -msoft-float -pipe
-fno-builtin -ffixed-r2 -Wno-uninitialized -mmultiple -mstring   -c -o
usb.o usb.c
usb.h: In function `usb_audio_interface':
In file included from usb.c:43:
usb.h:366: parameter name omitted
usb.h:366: parameter name omitted
usb.h: In function `usb_audio_endpoint':
usb.h:367: parameter name omitted
usb.h:367: parameter name omitted
make[3]: *** [usb.o] Error 1
make[3]: Leaving directory `/mnt/extra/linux-imac/drivers/usb'
make[2]: *** [first_rule] Error 2
make[2]: Leaving directory `/mnt/extra/linux-imac/drivers/usb'
make[1]: *** [_subdir_usb] Error 2
make[1]: Leaving directory `/mnt/extra/linux-imac/drivers'
make: *** [_dir_drivers] Error 2

(my config has this in its usb section)


# Universal Serial Bus (USB)

CONFIG_USB=y
# CONFIG_USB_UHCI is not set
CONFIG_USB_OHCI=y
CONFIG_USB_HUBD=y
# CONFIG_USB_AUDD is not set
# CONFIG_USB_HIDD is not set
CONFIG_USB_HIDBP=y
CONFIG_USB_HIDBP_KBD=y
CONFIG_USB_HIDBP_MSE=y
# CONFIG_USB_CDCD is not set
# CONFIG_USB_MSDD is not set

[brad@cricket brad]$ egcs --version
egcs-2.91.66

Brad
brad@pht.com | http://www.pht.com/~brad/



[[ This message was sent via the linuxppc-dev mailing list.  Replies are ]]
[[ not  forced  back  to the list, so be sure to Cc linuxppc-dev if your ]]
[[ reply is of general interest. Please check http://lists.linuxppc.org/ ]]
[[ and http://www.linuxppc.org/ for useful information before posting.   ]]

Re: rsync kernel compile fails

[Tom Rini]

On Wed, 2 Jun 1999, Brad Midgley wrote:

> is the rsync kernel supposed to be working? i haven't changed my config
> but it fails to compile:

It looks like a bit of trouble merging the new USB stack and Inaky's in
the rsync tree.  I saw a message from Paul on the USB list asking which
OHCI driver to use (I think the 1st one offered at config time is the best
one, they'll be merged together soon anyways)

--
Tom Rini (TR1265)
http://gate.crashing.org/~trini/


[[ This message was sent via the linuxppc-dev mailing list.  Replies are ]]
[[ not  forced  back  to the list, so be sure to Cc linuxppc-dev if your ]]
[[ reply is of general interest. Please check http://lists.linuxppc.org/ ]]
[[ and http://www.linuxppc.org/ for useful information before posting.   ]]

Re: rsync kernel compile fails

[Paul Mackerras]

Brad Midgley <brad@turbolinux.com> wrote:

> is the rsync kernel supposed to be working? i haven't changed my config
> but it fails to compile:

Well, the first problem is that drivers/Makefile goes into the usb
subdirectory for CONFIG_USB rather than the uusbd subdirectory.  Also
that tree doesn't have the multi-keyboard patch (and it won't apply
easily).

I have a 2.3.4 kernel working but without USB.  I plan to work on
getting the new USB stuff working on the iMac soon.  But in the
meantime maybe I need to get a recent 2.2.x kernel working with the
old UUSBD stack.  What I might do actually is kludge the USB keyboard
driver to convert all the keycodes to ADB keycodes, instead of
continuing with the multi-keyboard patch.

I have updated the rsync repository so that the linux-pmac-stable
module has the 2.2.7 tree that used to be in the linux-pmac-devel
module, and the linux-pmac-devel module now has a 2.3.4 tree.

Paul.

[[ This message was sent via the linuxppc-dev mailing list.  Replies are ]]
[[ not  forced  back  to the list, so be sure to Cc linuxppc-dev if your ]]
[[ reply is of general interest. Please check http://lists.linuxppc.org/ ]]
[[ and http://www.linuxppc.org/ for useful information before posting.   ]]

Re: rsync kernel compile fails

[Tom Rini]

On Thu, 3 Jun 1999, Paul Mackerras wrote:

> I have a 2.3.4 kernel working but without USB.  I plan to work on
> getting the new USB stuff working on the iMac soon.  But in the
> meantime maybe I need to get a recent 2.2.x kernel working with the
> old UUSBD stack.  What I might do actually is kludge the USB keyboard
> driver to convert all the keycodes to ADB keycodes, instead of
> continuing with the multi-keyboard patch.

It's actually not too hard to do.  (I did it to a vger tree for a while).
Just gotta backport the keyboard changes from 2.2.8 (or was it 7 when usb
went in?) and then fix a few problems that will no doubt show up w/ the
multikeyboard patch.  It'll work, and should be good enough until one of
the OHCI drivers in the new USB stack works w/ ppc (tho I suspect it might
be a bit of a pain, w/ the kernel_thread link problem, or whatever it
was...)

---
Tom Rini (TR1265)
http://dobbstown.yeti.edu/


[[ This message was sent via the linuxppc-dev mailing list.  Replies are ]]
[[ not  forced  back  to the list, so be sure to Cc linuxppc-dev if your ]]
[[ reply is of general interest. Please check http://lists.linuxppc.org/ ]]
[[ and http://www.linuxppc.org/ for useful information before posting.   ]]

Re: rsync kernel compile fails

[Paul Mackerras]

Tom Rini <tmrini@ntplx.net> wrote:

> It's actually not too hard to do.  (I did it to a vger tree for a while).
> Just gotta backport the keyboard changes from 2.2.8 (or was it 7 when usb
> went in?) and then fix a few problems that will no doubt show up w/ the
> multikeyboard patch.  It'll work, and should be good enough until one of
> the OHCI drivers in the new USB stack works w/ ppc (tho I suspect it might
> be a bit of a pain, w/ the kernel_thread link problem, or whatever it
> was...)

Do you have a recent 2.2.x tree that all works?

The reason I was thinking of converting the USB keycodes to ADB
keycodes is that that is what will have to happen with the new USB
stack (either that or converting everything to PC keycodes, which will
break a lot of things).

Paul.

[[ This message was sent via the linuxppc-dev mailing list.  Replies are ]]
[[ not  forced  back  to the list, so be sure to Cc linuxppc-dev if your ]]
[[ reply is of general interest. Please check http://lists.linuxppc.org/ ]]
[[ and http://www.linuxppc.org/ for useful information before posting.   ]]

Re: rsync kernel compile fails

[Tom Rini]

On Fri, 4 Jun 1999, Paul Mackerras wrote:

> Tom Rini <tmrini@ntplx.net> wrote:
> 
> > It's actually not too hard to do.  (I did it to a vger tree for a while).
> > Just gotta backport the keyboard changes from 2.2.8 (or was it 7 when usb
> > went in?) and then fix a few problems that will no doubt show up w/ the
> > multikeyboard patch.  It'll work, and should be good enough until one of
> > the OHCI drivers in the new USB stack works w/ ppc (tho I suspect it might
> > be a bit of a pain, w/ the kernel_thread link problem, or whatever it
> > was...)
> 
> Do you have a recent 2.2.x tree that all works?

I might have a 2.2.7 or 8 tree someplace w/ uusbd patched back in.  I
don't have anything w/ Linus' usb stack working.  (Looked at it and
figured I could wait until I had a pmac again).

> The reason I was thinking of converting the USB keycodes to ADB
> keycodes is that that is what will have to happen with the new USB
> stack (either that or converting everything to PC keycodes, which will
> break a lot of things).

I haven't looked at the current USB stack, but if it does what you seem to
be implying (changing the keycodes into their normal PC equiv) it's doing
something Wrong.  I'll go and skim what's in vger shortly..

---
Tom Rini (TR1265)
http://dobbstown.yeti.edu/


[[ This message was sent via the linuxppc-dev mailing list.  Replies are ]]
[[ not  forced  back  to the list, so be sure to Cc linuxppc-dev if your ]]
[[ reply is of general interest. Please check http://lists.linuxppc.org/ ]]
[[ and http://www.linuxppc.org/ for useful information before posting.   ]]

Re: rsync kernel compile fails

[Paul Mackerras]

Tom Rini <tmrini@ntplx.net> wrote:

> I haven't looked at the current USB stack, but if it does what you seem to
> be implying (changing the keycodes into their normal PC equiv) it's doing
> something Wrong.  I'll go and skim what's in vger shortly..

That's what it does all right.  I don't like it either but I don't
hold much hope of changing it.  I figure the best we will be able to
do is to change the USB keycodes into ADB keycodes instead of PC
keycodes.  That way the existing keymaps etc. should still work.

Paul.

[[ This message was sent via the linuxppc-dev mailing list.  Replies are ]]
[[ not  forced  back  to the list, so be sure to Cc linuxppc-dev if your ]]
[[ reply is of general interest. Please check http://lists.linuxppc.org/ ]]
[[ and http://www.linuxppc.org/ for useful information before posting.   ]]

Re: rsync kernel compile fails

[Tom Rini]

On Fri, 4 Jun 1999, Paul Mackerras wrote:

> Tom Rini <tmrini@ntplx.net> wrote:
> 
> > I haven't looked at the current USB stack, but if it does what you seem to
> > be implying (changing the keycodes into their normal PC equiv) it's doing
> > something Wrong.  I'll go and skim what's in vger shortly..
> 
> That's what it does all right.  I don't like it either but I don't
> hold much hope of changing it.  I figure the best we will be able to
> do is to change the USB keycodes into ADB keycodes instead of PC
> keycodes.  That way the existing keymaps etc. should still work.

Has anyone found out just why that's being done?   It doesn't really make
sense.  There's already usb keymaps for the things that would need 'em.
Perhaps a plea for sanity on linux-usb before things become too set in
stone?

---
Tom Rini (TR1265)
http://dobbstown.yeti.edu/


[[ This message was sent via the linuxppc-dev mailing list.  Replies are ]]
[[ not  forced  back  to the list, so be sure to Cc linuxppc-dev if your ]]
[[ reply is of general interest. Please check http://lists.linuxppc.org/ ]]
[[ and http://www.linuxppc.org/ for useful information before posting.   ]]

Problem with linux/in.h

[Patrik Jonsson]

Hi all,
When I try to compile code that uses networking (I tried ssh and freeciv) 
I get this error:

In file included from /usr/include/netinet/in.h:27,
                 from packets.c:19:
/usr/include/linux/in.h:109: parse error before `sa_family_t'
/usr/include/linux/in.h:109: warning: no semicolon at end of struct or
union
/usr/include/linux/in.h:116: parse error before `}'

The offending part of in.h is:

struct sockaddr_in {
  sa_family_t		sin_family;	/* Address family		*/
  unsigned short int	sin_port;	/* Port number			*/
  struct in_addr	sin_addr;	/* Internet address		*/

  /* Pad to size of `struct sockaddr'. */
  unsigned char		__pad[__SOCK_SIZE__ - sizeof(short int) -
			sizeof(unsigned short int) - sizeof(struct
in_addr)];
};

The problem seems to be that sa_family_t is never defined. Anyone got an
idea what's going on? This is with the 2.3.4 cvs sources.

Thanks,

	/Patrik



[[ This message was sent via the linuxppc-dev mailing list.  Replies are ]]
[[ not  forced  back  to the list, so be sure to Cc linuxppc-dev if your ]]
[[ reply is of general interest. Please check http://lists.linuxppc.org/ ]]
[[ and http://www.linuxppc.org/ for useful information before posting.   ]]

Re: Problem with linux/in.h

[Matt McLean]

On Thu, 3 Jun 1999, Patrik Jonsson wrote:

> 
> Hi all,
> When I try to compile code that uses networking (I tried ssh and freeciv) 
> I get this error:
> 
> In file included from /usr/include/netinet/in.h:27,
>                  from packets.c:19:
> /usr/include/linux/in.h:109: parse error before `sa_family_t'
> /usr/include/linux/in.h:109: warning: no semicolon at end of struct or
> union
> /usr/include/linux/in.h:116: parse error before `}'

This sounds like a very old compatibility problem with the older GNU libc
that came with R4[.1].  I recommend updating to the latest pre-R5.

-matt


[[ This message was sent via the linuxppc-dev mailing list.  Replies are ]]
[[ not  forced  back  to the list, so be sure to Cc linuxppc-dev if your ]]
[[ reply is of general interest. Please check http://lists.linuxppc.org/ ]]
[[ and http://www.linuxppc.org/ for useful information before posting.   ]]

Re: Problem with linux/in.h

[Paul Mackerras]

Patrik Jonsson <patrik@ucolick.org> wrote:

> When I try to compile code that uses networking (I tried ssh and freeciv) 
> I get this error:

Are you using R4 (i.e. glibc-1.99) or R5 (i.e. glibc-2.1)?  If you are
using glibc-1.99, I recommend you change the definition of __GLIBC__
in /usr/include/features.h to say

#define __GLIBC__ 1

rather than 2.  The problem is that some of the kernel include files
omit some definitions if __GLIBC__ == 2, since glibc-2.1 likes to
define things that should really be left to the kernel headers (IMHO).

Paul.

[[ This message was sent via the linuxppc-dev mailing list.  Replies are ]]
[[ not  forced  back  to the list, so be sure to Cc linuxppc-dev if your ]]
[[ reply is of general interest. Please check http://lists.linuxppc.org/ ]]
[[ and http://www.linuxppc.org/ for useful information before posting.   ]]