Announcement

Collapse
No announcement yet.

Busybox SCP has compilation errors in Xport Pro SDK 2.0

Collapse
X
  • Filter
  • Time
  • Show
Clear All
new posts

  • Busybox SCP has compilation errors in Xport Pro SDK 2.0

    I made an error in the original title - this is regarding dropbear rather than busybox.

    I'm using Linux SDK 2.0 for Xport Pro.

    I've got dropbear SSH working fine but when I check the dropbear SCP line item I get the following errors:

    make[5]: `tinylogin' is up to date.
    make[5]: `tinylogin.links' is up to date.
    make[5]: Nothing to be done for `doc'.
    make[5]: Leaving directory `/xportpro_sdk_2/linux/user/tinylogin'
    make[4]: Leaving directory `/xportpro_sdk_2/linux/user/tinylogin'
    scp.c: In function 'main':
    scp.c:386: warning: implicit declaration of function 'setmode'
    scp.c:386: error: 'O_BINARY' undeclared (first use in this function)
    scp.c:386: error: (Each undeclared identifier is reported only once
    scp.c:386: error: for each function it appears in.)
    make[5]: *** [scp.o] Error 1
    make[5]: Leaving directory `/xportpro_sdk_2/linux/user/dropbear/dropbear-0.52'
    make[4]: *** [dropbear-0.52] Error 2
    make[4]: Leaving directory `../xportpro_sdk_2/linux/user/dropbear'
    make[3]: *** [dropbear] Error 2
    make[3]: *** Waiting for unfinished jobs....
    Using /xportpro_sdk_2/linux/user/busybox/busybox-1.13.3 as source for busybox

    It appears that code is being compiled due to an error in the compilation define value.

    From file: xportpro_sdk_2/linux/user/dropbear/dropbear-0.52/scp.c

    #ifdef HAVE_CYGWIN
    setmode(0, O_BINARY);
    #endif


    It appears that the definition of the HAVE_CYGWIN macro is in error as I don't believe that uclinix supports Cygwin.

    From the Make file in xportpro_sdk_2/linux/user/dropbear/dropbear-0.52

    CFLAGS=-I. -I$(srcdir) -I$(srcdir)/libtomcrypt/src/headers/ $(CPPFLAGS) -Os -g -fomit-frame-pointer -pipe -fno-common -fno-builtin -Wall -DEMBED -fno-dwarf2-cfi-asm -msep-data -Dlinux -D__linux__ -Dunix -D__uClinux__ -Dfork=vfork -DUSE_DEV_PTMX -DHAVE_CYGWIN -DDROPBEAR_COMPACT -DDISABLE_ERRMSG -DDISABLE_DROPBEAR_LOG -DARGTYPE=3 -DMP_31BIT -DRSA_FAST -Dfork=vfork -DUSE_DEV_PTMX -DHAVE_CYGWIN -DDROPBEAR_COMPACT -DDISABLE_ERRMSG -DDISABLE_DROPBEAR_LOG -DARGTYPE=3 -DMP_31BIT -DRSA_FAST -DENDIAN_BIG -DENDIAN_32BITWORD

    Once I modified the Makefile to remove the -DHAVE_CYGWIN (both of them), the busybox SCP program compiled and linked without errors.

    However, I'm not certain it will work correctly now. I need to know if this is the correct solution or if other Makefile changes are necessary.


    Blort
    Last edited by blort; 07-13-2011, 04:14 PM.

  • #2
    Originally posted by blort View Post
    I made an error in the original title - this is regarding dropbear rather than busybox.

    I'm using Linux SDK 2.0 for Xport Pro.

    I've got dropbear SSH working fine but when I check the dropbear SCP line item I get the following errors:

    make[5]: `tinylogin' is up to date.
    make[5]: `tinylogin.links' is up to date.
    make[5]: Nothing to be done for `doc'.
    make[5]: Leaving directory `/xportpro_sdk_2/linux/user/tinylogin'
    make[4]: Leaving directory `/xportpro_sdk_2/linux/user/tinylogin'
    scp.c: In function 'main':
    scp.c:386: warning: implicit declaration of function 'setmode'
    scp.c:386: error: 'O_BINARY' undeclared (first use in this function)
    scp.c:386: error: (Each undeclared identifier is reported only once
    scp.c:386: error: for each function it appears in.)
    make[5]: *** [scp.o] Error 1
    make[5]: Leaving directory `/xportpro_sdk_2/linux/user/dropbear/dropbear-0.52'
    make[4]: *** [dropbear-0.52] Error 2
    make[4]: Leaving directory `../xportpro_sdk_2/linux/user/dropbear'
    make[3]: *** [dropbear] Error 2
    make[3]: *** Waiting for unfinished jobs....
    Using /xportpro_sdk_2/linux/user/busybox/busybox-1.13.3 as source for busybox

    It appears that code is being compiled due to an error in the compilation define value.

    From file: xportpro_sdk_2/linux/user/dropbear/dropbear-0.52/scp.c

    #ifdef HAVE_CYGWIN
    setmode(0, O_BINARY);
    #endif


    It appears that the definition of the HAVE_CYGWIN macro is in error as I don't believe that uclinix supports Cygwin.

    From the Make file in xportpro_sdk_2/linux/user/dropbear/dropbear-0.52

    CFLAGS=-I. -I$(srcdir) -I$(srcdir)/libtomcrypt/src/headers/ $(CPPFLAGS) -Os -g -fomit-frame-pointer -pipe -fno-common -fno-builtin -Wall -DEMBED -fno-dwarf2-cfi-asm -msep-data -Dlinux -D__linux__ -Dunix -D__uClinux__ -Dfork=vfork -DUSE_DEV_PTMX -DHAVE_CYGWIN -DDROPBEAR_COMPACT -DDISABLE_ERRMSG -DDISABLE_DROPBEAR_LOG -DARGTYPE=3 -DMP_31BIT -DRSA_FAST -Dfork=vfork -DUSE_DEV_PTMX -DHAVE_CYGWIN -DDROPBEAR_COMPACT -DDISABLE_ERRMSG -DDISABLE_DROPBEAR_LOG -DARGTYPE=3 -DMP_31BIT -DRSA_FAST -DENDIAN_BIG -DENDIAN_32BITWORD

    Once I modified the Makefile to remove the -DHAVE_CYGWIN (both of them), the busybox SCP program compiled and linked without errors.

    However, I'm not certain it will work correctly now. I need to know if this is the correct solution or if other Makefile changes are necessary.


    Blort
    I too am having similar issues with Xport Pro SDK version 2. I was wondering whether it had anything to do with the compatibility issues of Busybox SCP.

    Comment


    • #3
      I also experience this problem - and as we are note running on CYGWIN I just commented this one line out - than droipbear compiles, but i get an error when i want to start dropbear:

      Code:
      [68] Nov 30 00:00:08 premature exit:
      anybody has an Idea?

      Comment


      • #4
        Originally posted by f15h View Post
        I also experience this problem - and as we are note running on CYGWIN I just commented this one line out - than droipbear compiles, but i get an error when i want to start dropbear:

        Code:
        [68] Nov 30 00:00:08 premature exit:
        anybody has an Idea?
        It appears this issue is still outstanding. I have googled this to death and have found no solutions.

        Any help would be appreciated.

        Comment

        Working...
        X