Hello GDB group ! I often try to build up cross tool chains for different platforms: i386, PowerPC, Atmel AVR, HP PA-RISC, and SPARC soon.
But I always have the problem with the standard GDB server (not a stub in special environments). First of all a question: Why is the gdbserver not built up auto- matically. If I build a native GDB, then I want to have a `gdbserver' for my native system, for example I have the same core system, but only small disk (CompactFlash, for example) and I want to use `gdbserver' there. If I build a cross build, for example a PPC cross setup from a intel machine, then I think it is also a clear way to build a `gdb' running on a i386 and handling PPC code, and a `gdbserver' running on the target (--host=$TARGET) and in the best also install it to $prefix/$TARGET as `glibc' and others do so. When I build up such a tool chain, I always have source and object trees seperated. How can I configure and build a `gdbserver' in such a tree setup. When I do the configuration in the source tree under ./gdb/gdbserver (which I do not like in the source tree ...), then the built cannot find generated header files. I cannot run the `configure' from the object tree, as there is no subdirectory under `./gdb' named `gdbserver'. Doing a copy from the src/gdb-5.1.1/gdb/gdbserver to the corresponding place into the object tree does not work also. How is this done correctly. I cannot find good information on this topic in the internet. PLEASE: Send it directly to me, as I am not registered on the GDB mailing list (perhaps I want to, if the problem stays longer ...) With friendly regards Christoph P. -- ------------------------------------------------------- private: [EMAIL PROTECTED] company: [EMAIL PROTECTED] _______________________________________________ Bug-gdb mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/bug-gdb