This is the mail archive of the crossgcc@sources.redhat.com mailing list for the crossgcc project.
See the CrossGCC FAQ for lots more information.
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |
> Yep, that's it. You know the trick about cd'ing into a subdir of a >GCC build tree and doing "make all" there to only build that component? It >works here too. Configure for your debug host and "make all install" in >your top level dir; then configure for your debug target, cd into the >gdbserver directory, and make all there. (You could make install as well >but it wouldn't be very useful!) I was looking at this stuff over last >weekend, wondering whether to port gdbserver to vxworks... So let's see if I have this right. I have the powerpc-linux tree built using build-crossgcc.sh in /usr/local/cross-linux-tools. Would the following do what you think it should: export PATH=/usr/local/cross-linux-tools/bin:$PATH cd foo tar zxf ~/src/gdb-5.0.tar.gz mkdir build-gb cd build-gdb ../gdb-5.0/configure --target=powerpc-linux --prefix=/usr/local/cross-linux-tools make all install ../gdb-5.0/configure --host=powerpc-linux --prefix=/usr/local/cross-linux-tools cd gdb/gdbserver make all And in this directory i should have a gdbserver, right? -- Peter Barada Peter.Barada@motorola.com Wizard 781-852-2768 (direct) WaveMark Solutions(wholly owned by Motorola) 781-270-0193 (fax) ------ Want more information? See the CrossGCC FAQ, http://www.objsw.com/CrossGCC/ Want to unsubscribe? Send a note to crossgcc-unsubscribe@sourceware.cygnus.com
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |