Re: Interpreting bytecode on a powerpc 405 EP

["Patrick Olinet" <patrick dot olinet at gmail dot com>]

David,

Unfortunately, rsh/rlogin servers are not available on my target
platform. Only telnet/ftp are allowed. I've been able to tell dejagnu
to use ftp to download the cross-compiled binaries onto the target,
but I'm stuck with the rsh problem. Dejagnu keeps on trying to use rsh
to execute the binaries, although I've added the following lines to my
board.exp file :

set board_info($board,protocol) "telnet"
set board_info($board,hostname) "192.168.0.46"
set board_info($board,telnet_username) "root"
set board_info($board,telnet_password) "xxxx"
set board_info($board,shell_prompt) "#"

I read part of the dejagnu documentation and the telnet sample at the
beginning works fine for me.

What's the right way (hope there is one!) to setup the libffi
testsuite for using telnet instead of rsh ?

Rgds,
Patrick

On 4/27/07, David Daney <ddaney@avtrex.com> wrote:
> Patrick Olinet wrote:
> > Ummh, it looks like it tries to run the testsuite on my build machine,
> > which obviously doesn't work (I'm cross compiling). I would like to
> > run the testsuite on my powerpc target but it's an embedded platform
> > with limited resources and I cannot afford setting up an development
> > environment on it.
> >
> > Is there a way to cross compile the testsuite on my build PC for my
> > PPC target and then run it from the target ?
> >
>
> Yes.  This is how I do it.  Place all the generated .so files into the
> library path of the target (i.e. in /lib or /usr/lib).  Then configure
> the target so that you can rsh/rlogin/rcp with no need to supply a
> password (properly configure your .rhosts file).
>
> Then in your home directory of the build machine you need your site.exe
> to be something like:
>
> site.exp
> -------------------------
> lappend boards_dir "/home/daney/boards"
>
> #
> # Determine target machines for all known targets
> #
>
> #
> # If we're testing GCC, G++ or GDB, then we want to run on all the
> # available targets. Otherwise, just test the first one.
> #
> # set verbose 9
> verbose "Global Config File: target_triplet is $target_triplet" 2
> global target_list
>
> set target_list { "proton-dave" }
> -------------------------
>
> You also need a boards directory that contains something like:
>
> boards/proton-dave.exp
> -------------------------------------------
> load_base_board_description "unix";
>
> # The generic type of board.
> set board_info($board,generic_name) "unix"
>
> # The name used to connect to this machine.
> set board_info($board,hostname) "proton-dave"
> set board_info($board,rsh_prog) /usr/bin/rsh
> set board_info($board,rcp_prog) /usr/bin/rcp
>
> set prefix_dir "/tmp"
> -------------------------------------------
>
> Then:
> export DEJAGNU=proton-dave
> make -k check
>
> David Daney
>
>
> > Patrick
> >
> >
> >
> > On 4/27/07, David Daney <ddaney@avtrex.com> wrote:
> >> Patrick Olinet wrote:
> >> > Andrew, Tom,
> >> >
> >> >
> >> > I finally managed to set up a new cross toolchain, based on gcc 4.1.0
> >> > (thanks to the crosstool environnment). Unfortunately, it doesn't help
> >> > since I got exactly the same error message.
> >> >
> >> > I'd like to run the libffi testsuite. It's not obvious for me how to
> >> > set it up and compile it, specially from within the crosstool
> >> > baseline. Could you provide me with guidelines on that ?
> >> >
> >> You need to find where crosstool placed the libffi build directory.
> >> Then do something like this:
> >>
> >> cd ...../target-name/libffi
> >> make -k check
> >>
> >> David Daney
> >>
> >>