Cross-Compile ncurses for ARM? - Embedded

This is a discussion on Cross-Compile ncurses for ARM? - Embedded ; Hey, Has anyone had any success cross-compiling ncurses? I am having problems with the configure script not recognizing my CC.. Ex, if my GNUmakefile does: ../configure --target=arm-unknown-linux-gnu --with-shared --without-ada --with-build-cc=$CC --with-build-cpp=$CXX --with-build-cppflags= $CPPFLAGS --disable-big-core --enable-termcap --enable-echo --enable- warnings and sets: ...

+ Reply to Thread
Results 1 to 4 of 4

Thread: Cross-Compile ncurses for ARM?

  1. Cross-Compile ncurses for ARM?

    Hey,

    Has anyone had any success cross-compiling ncurses? I am having
    problems with the configure script not recognizing my CC..

    Ex, if my GNUmakefile does:
    ../configure --target=arm-unknown-linux-gnu --with-shared --without-ada
    --with-build-cc=$CC --with-build-cpp=$CXX --with-build-cppflags=
    $CPPFLAGS --disable-big-core --enable-termcap --enable-echo --enable-
    warnings

    and sets:
    CC :=arm-none-linux-gnueabi-gcc
    CXX :=arm-none-linux-gnueabi-g++

    The configure script always outputs:
    checking for egrep... grep -E
    Configuring NCURSES 5.6 ABI 5 (Wed Jun 4 11:41:31 PDT 2008)
    checking build system type... x86_64-unknown-linux-gnu
    checking host system type... x86_64-unknown-linux-gnu
    checking target system type... arm-unknown-linux-gnu
    Configuring for linux-gnu
    checking for prefix... /usr
    checking for gcc... gcc
    checking for C compiler default output... a.out
    checking whether the C compiler works... yes
    checking whether we are cross compiling... no
    ....
    ----------------------------------------------------------------^^

    Anyone have any luck cross-compiling these sources for ARM? It would
    really help for a university robotics team..

    Thanks!
    Moe



  2. Re: Cross-Compile ncurses for ARM?

    Hi,

    On Jun 4, 8:56 pm, mad...@engmail.uwaterloo.ca wrote:

    > Has anyone had any success cross-compiling ncurses? I am having
    > problems with the configure script not recognizing my CC..
    >
    > Ex, if my GNUmakefile does:
    > ./configure --target=arm-unknown-linux-gnu --with-shared --without-ada
    > --with-build-cc=$CC --with-build-cpp=$CXX --with-build-cppflags=
    > $CPPFLAGS --disable-big-core --enable-termcap --enable-echo --enable-
    > warnings
    >
    > and sets:
    > CC :=arm-none-linux-gnueabi-gcc
    > CXX :=arm-none-linux-gnueabi-g++
    >
    > The configure script always outputs:
    > checking for egrep... grep -E
    > Configuring NCURSES 5.6 ABI 5 (Wed Jun 4 11:41:31 PDT 2008)
    > checking build system type... x86_64-unknown-linux-gnu
    > checking host system type... x86_64-unknown-linux-gnu
    > checking target system type... arm-unknown-linux-gnu
    > Configuring for linux-gnu
    > checking for prefix... /usr
    > checking for gcc... gcc
    > checking for C compiler default output... a.out
    > checking whether the C compiler works... yes
    > checking whether we are cross compiling... no
    > ...
    > ----------------------------------------------------------------^^
    >
    > Anyone have any luck cross-compiling these sources for ARM? It would
    > really help for a university robotics team..


    your main problem is the --target flag. afaik it is only used for
    building cross-compilers:

    [from ./configure --help]

    System types:
    --build=BUILD configure for building on BUILD [guessed]
    --host=HOST build programs to run on HOST [BUILD]
    --target=TARGET configure for building compilers for TARGET [HOST]

    what you need to specify is --host. the following works for me:

    ../configure --host=arm-unknown-linux-gnu --with-shared --without-ada
    --disable-big-core --enable-termcap --enable-echo --enable-warnings

    good luck!

  3. Re: Cross-Compile ncurses for ARM?

    On Jun 5, 2:39 am, Matthias Kaehlcke
    wrote:
    > Hi,
    >
    > On Jun 4, 8:56 pm, mad...@engmail.uwaterloo.ca wrote:
    >
    >
    >
    > > Has anyone had any success cross-compiling ncurses? I am having
    > > problems with the configure script not recognizing my CC..

    >
    > > Ex, if my GNUmakefile does:
    > > ./configure --target=arm-unknown-linux-gnu --with-shared --without-ada
    > > --with-build-cc=$CC --with-build-cpp=$CXX --with-build-cppflags=
    > > $CPPFLAGS --disable-big-core --enable-termcap --enable-echo --enable-
    > > warnings

    >
    > > and sets:
    > > CC :=arm-none-linux-gnueabi-gcc
    > > CXX :=arm-none-linux-gnueabi-g++

    >
    > > The configure script always outputs:
    > > checking for egrep... grep -E
    > > Configuring NCURSES 5.6 ABI 5 (Wed Jun 4 11:41:31 PDT 2008)
    > > checking build system type... x86_64-unknown-linux-gnu
    > > checking host system type... x86_64-unknown-linux-gnu
    > > checking target system type... arm-unknown-linux-gnu
    > > Configuring for linux-gnu
    > > checking for prefix... /usr
    > > checking for gcc... gcc
    > > checking for C compiler default output... a.out
    > > checking whether the C compiler works... yes
    > > checking whether we are cross compiling... no
    > > ...
    > > ----------------------------------------------------------------^^

    >
    > > Anyone have any luck cross-compiling these sources for ARM? It would
    > > really help for a university robotics team..

    >
    > your main problem is the --target flag. afaik it is only used for
    > building cross-compilers:
    >
    > [from ./configure --help]
    >
    > System types:
    > --build=BUILD configure for building on BUILD [guessed]
    > --host=HOST build programs to run on HOST [BUILD]
    > --target=TARGET configure for building compilers for TARGET [HOST]
    >
    > what you need to specify is --host. the following works for me:
    >
    > ./configure --host=arm-unknown-linux-gnu --with-shared --without-ada
    > --disable-big-core --enable-termcap --enable-echo --enable-warnings
    >
    > good luck!


    Thanks!

    And if anyone else is having issues, make sure you set BUILD_CC=gcc
    (or whatever your build env compiler is..).

    example that worked for me:
    ../configure arm-linux --host=arm-none-linux-gnueabi --with-shared --
    without-ada --with-build-cc=gcc --with-build-cpp=arm-none-linux-
    gnueabi-g++ --disable-big-core --enable-termcap --prefix=/usr --
    disable-GPM --with-build-ldflags="$(LDFLAGS)" --with-build-cflags="$
    (CFLAGS)" --with-build-cppflags="$(CPPFLAGS)"

    Cheers
    Moe
    University of Waterloo

  4. Re: Cross-Compile lttng for ARM?

    Hi,

    i'm working with an at91sam9263 and try to get lltng on it.
    A 2.6.25 kernel with the lttng patch is on the board.

    patch-2.6.25-lttng-0.10-
    ltt-control-0.48-27022008.
    lttv-0.10.0-pre5-05122007.tar.gz

    The problem is to compile the llt-control package and lttv for this target.

    I set the environment variables

    >> CC :=arm-none-linux-gnueabi-gcc
    >> CXX :=arm-none-linux-gnueabi-gcc

    and refer on kernel-source code.

    I think the failure is the call of "./configure"-

    >> ./configure --host=arm-unknow-linux --build=i686-pc-linux (look at output_config.txt)
    >> make
    >> make install


    If i try to start the output files on the board, i get this message:

    >> /bin/lttd: line 1: syntax error: "(" unexpected <<


    With an other configuration:
    ./configure arm-linux-gnueabi --build= i686-pc-linux --target=arm-linux-gnueabi- --enable-cross-compile
    (look at output_config2.txt)
    make (look at make.txt)
    make install (look at make_install.txt)

    Now the message is a:

    >>Segmentation fault

    How i could solve this problem?

    Thanks Nunu
    Attached Files

+ Reply to Thread