From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 13075 invoked by alias); 24 Feb 2002 11:26:31 -0000 Mailing-List: contact gdb-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sources.redhat.com Received: (qmail 12967 invoked from network); 24 Feb 2002 11:26:23 -0000 Received: from unknown (HELO viefep11-int.chello.at) (213.46.255.27) by sources.redhat.com with SMTP; 24 Feb 2002 11:26:23 -0000 Received: from gmx.at ([62.178.92.247]) by viefep11-int.chello.at (InterMail vM.5.01.03.06 201-253-122-118-106-20010523) with ESMTP id <20020224112621.AAY1155.viefep11-int.chello.at@gmx.at>; Sun, 24 Feb 2002 12:26:21 +0100 Message-ID: <3C78CDDC.DCEC0237@gmx.at> Date: Sun, 24 Feb 2002 03:26:00 -0000 From: Christoph Plattner Organization: private X-Mailer: Mozilla 4.76 [en] (X11; U; Linux 2.4.6 i686) X-Accept-Language: en MIME-Version: 1.0 To: Andrew Cagney CC: gdb@sources.redhat.com Subject: Re: `gdbserver' in cross compiled builds References: <3C5B3201.2F2FB670@gmx.at> <3C77D1F6.1020704@cygnus.com> <3C780221.CF27FBDA@gmx.at> <3C7808F9.3080106@cygnus.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-SW-Source: 2002-02/txt/msg00281.txt.bz2 Yes, that's clear for me. It is the same for glibc. With this point I have NO problems. The problem is simple in the tree setup ! In my built (objects) tree, there is NO "gdbserver" subdirectory created by configuring, in the gdb source tree, the configuration cannot be done, because all generated files (configs, header files, etc) are written to the build tree (OBJECT tree). So my problems are not in the config parameters, but simple, where (on which path) is called what ? And if I do some hacks manually, PPC support (for example) cannot be built. Why does the gdbserver directory work so bad ? I hope I could give you the point of my problem (reread last email also). With friendly regards Christoph Plattner Olt EMAIL: ------------------ Hello, thanks for you answer, but my questions aimed to another point. Why is the gdbserver not built automatically also in cross builds ? Why is gdbserver not configured in cross builds ? How to do the correct way to build and configure concerning the source tree and the build tree. For example $HOME/src/gdb ... is the current gdb source $HOME/build/gdb ... is the current build tree for gdb cd $HOME/build/gdb ../../src/gdb/configure ............. where the parameters for configure sets up a cross build, for example target is a powerpc architecture, host is i386-linux. GDB can be build for that without problem. But how to configure "gdbserver" now ? There is no directory under the build tree. To change to the source tree to do the setup is also wrong, as generated header files, etc, cannot be found there. What is the professional way here (not a hack or a workaround). I hope you can help here. With friendly regards Christoph Plattner Andrew Cagney wrote: > > > Hello, > > > > thanks for you answer, but my questions aimed to another point. > > > > Why is the gdbserver not built automatically also in cross builds ? > > Are you configuring with: > > ..../configure --target=powerpc-linux-gnu > > or > > ..../configure --host=powerpc-linux-gnu --target=powerpc-linux-gnu > --build=i386-linux-gnu > > the former configures to build a cross debugger. The latter configures > to build a debugger (and gdbserver) that will run on the target system. > The latter assumes that you have a powerpc-linux-gnu-gcc installed > somewhere while the former doesn't. > > Andrew -- ------------------------------------------------------- private: christoph.plattner@gmx.at company: christoph.plattner@alcatel.at