Re: CALL FOR TESTERS! [Re: 6.2 SHOWSTOPPER - em completely unusable on 6.2]



At 03:15 PM 9/28/2006, O. Hartmann wrote:

/usr/src/sys/dev/usb/usb.c:282: error: for each function it appears in.)
/usr/src/sys/dev/usb/usb.c: At top level:
/usr/src/sys/dev/usb/usb.c:863: warning: 'usb_intr_task' defined but not used
*** Error code 1


Are you sure the patch applied cleanly to STABLE ? There are a couple of spots you need to change manually as it assumes the version of USB from HEAD.

Manually apply the patch for usb.c and ohci_pci.c if you are using STABLE and remove the offending bits from the patch and it should compile cleanly.

---Mike

_______________________________________________
freebsd-stable@xxxxxxxxxxx mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscribe@xxxxxxxxxxx"



Relevant Pages

  • Re: NetJoinDomain
    ... Error Code 87 The parameter is incorrect. ... Ich melde mich nochmal wenn ich den Patch getestet habe. ... strDomain = StrConv(strDomain, vbUnicode) ...
    (microsoft.public.vb.winapi.networks)
  • Re: ZFS patches.
    ... The patch applied fine for me, but I get a compile error part way through ... My world/kernel is from -current from Thursday, ... expected expression before ')' token ... *** Error code 1 ...
    (freebsd-current)
  • Re: panic: invalid ife->ifm_data (0xa) in mii_phy_setmedia
    ... Thanks a lot for your patch. ... bge0: ... *** Error code 1 ... diff -u -r1.36.2.7 if_bgereg.h ...
    (freebsd-stable)
  • Re: [RFC] Kernel patches for compilation with gcc 4.0
    ... I sent a separate e-mail to njl@ and marks@ about the acpi_wakeup patch. ... I remove the static variables which clashed with the global variables ... Because I got this compiler error in in.c: ... *** Error code 1 ...
    (freebsd-arch)
  • Re: A little bug in Win32Forth
    ... when I run xx2 or xx3, the error code should be: ... Lone: is not understood by class Display ... I get instead: Show3: is not understood by class Display ... I have made a patch to correct it, ...
    (comp.lang.forth)