public inbox for gdb@sourceware.org
 help / color / mirror / Atom feed
* Compiling error
@ 2004-08-04  8:41 Fabian Cenedese
  2004-08-04 16:38 ` Eli Zaretskii
  0 siblings, 1 reply; 6+ messages in thread
From: Fabian Cenedese @ 2004-08-04  8:41 UTC (permalink / raw)
  To: gdb

Hi

I'm new to the list and also quite new to gdb. I'm trying to use gdb to work
with an embedded PPC board. After some useless fiddling around it finally
came to my mind that I need to compile my own gdb which works with
--target=powerpc-elf32.

I have MSYS/MinGW/Cygwin. Configure went ok. But make gives this:

make[1]: Entering directory `/home/Fabi/gdb-6.1.1/ppc/readline'
rm -f rltty.o
gcc -c -DHAVE_CONFIG_H   -I. -I../../gdb-6.1.1/readline -DRL_LIBRARY_VERSION='"4.3"' -g -O2 ../../gdb-6.1.1/readline/rltty.c
In file included from ../../gdb-6.1.1/readline/rltty.c:44:
../../gdb-6.1.1/readline/rltty.h:42:21: sgtty.h: No such file or directory
../../gdb-6.1.1/readline/rltty.c:166: field `sgttyb' has incomplete type
../../gdb-6.1.1/readline/rltty.c:175: confused by earlier errors, bailing out
make[1]: *** [rltty.o] Error 1
make[1]: Leaving directory `/home/Fabi/gdb-6.1.1/ppc/readline'
make: *** [all-readline] Error 2

I couldn't find this sgtty.h neither in gdb nor in MSYS, MinGW
or Cygwin. What else do I need to compile gdb on Windows?
Or should I take the DJGPP road?

Thanks

bye  Fabi


^ permalink raw reply	[flat|nested] 6+ messages in thread

* Re: Compiling error
  2004-08-04  8:41 Compiling error Fabian Cenedese
@ 2004-08-04 16:38 ` Eli Zaretskii
  2004-08-05  6:34   ` Fabian Cenedese
  0 siblings, 1 reply; 6+ messages in thread
From: Eli Zaretskii @ 2004-08-04 16:38 UTC (permalink / raw)
  To: Fabian Cenedese; +Cc: gdb

> Date: Wed, 04 Aug 2004 10:41:37 +0200
> From: Fabian Cenedese <Cenedese@indel.ch>
> 
> I have MSYS/MinGW/Cygwin. Configure went ok. But make gives this:
> 
> make[1]: Entering directory `/home/Fabi/gdb-6.1.1/ppc/readline'
> rm -f rltty.o
> gcc -c -DHAVE_CONFIG_H   -I. -I../../gdb-6.1.1/readline -DRL_LIBRARY_VERSION='"4.3"' -g -O2 ../../gdb-6.1.1/readline/rltty.c
> In file included from ../../gdb-6.1.1/readline/rltty.c:44:
> ../../gdb-6.1.1/readline/rltty.h:42:21: sgtty.h: No such file or directory
> ../../gdb-6.1.1/readline/rltty.c:166: field `sgttyb' has incomplete type
> ../../gdb-6.1.1/readline/rltty.c:175: confused by earlier errors, bailing out
> make[1]: *** [rltty.o] Error 1
> make[1]: Leaving directory `/home/Fabi/gdb-6.1.1/ppc/readline'
> make: *** [all-readline] Error 2

Where did you get the GDB sources?  It sounds like you are trying to
compile sources that were not ported to MinGW.

If this doesn't give you any idea what to do, I suggest to ask the
question on some MinGW-related forum (sorry, no URL), because the
solution, if it exists, is probably MinGW-specific.

> I couldn't find this sgtty.h neither in gdb nor in MSYS, MinGW
> or Cygwin. What else do I need to compile gdb on Windows?
> Or should I take the DJGPP road?

The DJGPP port will build, allright (provided that you follow the
instructions in gdb/config/djgpp/README), but the resulting gdb.exe
will be unable to debug anything but DJGPP programs.  So this is not
what you want.

^ permalink raw reply	[flat|nested] 6+ messages in thread

* Re: Compiling error
  2004-08-04 16:38 ` Eli Zaretskii
@ 2004-08-05  6:34   ` Fabian Cenedese
  2004-08-05  9:48     ` Fabian Cenedese
  0 siblings, 1 reply; 6+ messages in thread
From: Fabian Cenedese @ 2004-08-05  6:34 UTC (permalink / raw)
  To: gdb


>> I have MSYS/MinGW/Cygwin. Configure went ok. But make gives this:
>> 
>> make[1]: Entering directory `/home/Fabi/gdb-6.1.1/ppc/readline'
>> rm -f rltty.o
>> gcc -c -DHAVE_CONFIG_H   -I. -I../../gdb-6.1.1/readline -DRL_LIBRARY_VERSION='"4.3"' -g -O2 ../../gdb-6.1.1/readline/rltty.c
>> In file included from ../../gdb-6.1.1/readline/rltty.c:44:
>> ../../gdb-6.1.1/readline/rltty.h:42:21: sgtty.h: No such file or directory
>> ../../gdb-6.1.1/readline/rltty.c:166: field `sgttyb' has incomplete type
>> ../../gdb-6.1.1/readline/rltty.c:175: confused by earlier errors, bailing out
>> make[1]: *** [rltty.o] Error 1
>> make[1]: Leaving directory `/home/Fabi/gdb-6.1.1/ppc/readline'
>> make: *** [all-readline] Error 2
>
>Where did you get the GDB sources?  It sounds like you are trying to
>compile sources that were not ported to MinGW.

It's the official gdb source package. I thought with the help of cygwin I
wouldn't need any special version. But I will try the MinGW one as well.

>If this doesn't give you any idea what to do, I suggest to ask the
>question on some MinGW-related forum (sorry, no URL), because the
>solution, if it exists, is probably MinGW-specific.
>
>> I couldn't find this sgtty.h neither in gdb nor in MSYS, MinGW
>> or Cygwin. What else do I need to compile gdb on Windows?
>> Or should I take the DJGPP road?
>
>The DJGPP port will build, allright (provided that you follow the
>instructions in gdb/config/djgpp/README), but the resulting gdb.exe
>will be unable to debug anything but DJGPP programs.  So this is not
>what you want.

Even with DJGPP you can run configure and --target=powerpc-elf32
seemed to work fine. There were some files missing from the official
source package but after adding them make finished fine and produced
a gdb.exe. But that didn't seem to work as expected (unknown symbol
type when reading a symbol file, network didn't seem to work either).

So if I need a cross-target gdb (running on win32, debugging ppc) is
the MinGW variant the only one that works? I thought that there are
also cygwin versions of gdb... but maybe only win32-win32.
I found the sgtty.h, it's in the glibc, so it may work ok if I install that
as well. But I first try the MinGW one.

Thanks

bye  Fabi


^ permalink raw reply	[flat|nested] 6+ messages in thread

* Re: Compiling error
  2004-08-05  6:34   ` Fabian Cenedese
@ 2004-08-05  9:48     ` Fabian Cenedese
  2004-08-06  6:22       ` ser-win32.c (was Re: Compiling error) Fabian Cenedese
  2004-08-06  8:27       ` Compiling error Eli Zaretskii
  0 siblings, 2 replies; 6+ messages in thread
From: Fabian Cenedese @ 2004-08-05  9:48 UTC (permalink / raw)
  To: gdb


>>> I couldn't find this sgtty.h neither in gdb nor in MSYS, MinGW
>>> or Cygwin. What else do I need to compile gdb on Windows?
>>> Or should I take the DJGPP road?
>>
>>The DJGPP port will build, allright (provided that you follow the
>>instructions in gdb/config/djgpp/README), but the resulting gdb.exe
>>will be unable to debug anything but DJGPP programs.  So this is not
>>what you want.
>
>Even with DJGPP you can run configure and --target=powerpc-elf32
>seemed to work fine. There were some files missing from the official
>source package but after adding them make finished fine and produced
>a gdb.exe. But that didn't seem to work as expected (unknown symbol
>type when reading a symbol file, network didn't seem to work either).
>
>So if I need a cross-target gdb (running on win32, debugging ppc) is
>the MinGW variant the only one that works? I thought that there are
>also cygwin versions of gdb... but maybe only win32-win32.
>I found the sgtty.h, it's in the glibc, so it may work ok if I install that
>as well. But I first try the MinGW one.

So I tried (and fiddled a lot!) again with MSYS and MinGW and got
a gdb.exe. But it has the same problems as the one I built with DJGPP.

This is the official http://prdownloads.sf.net/mingw/gdb-5.2.1-1-src.tar.bz2,
configured with --target=powerpc-elf32.

GNU gdb 5.2.1
Copyright 2002 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and you are
welcome to change it and/or distribute copies of it under certain conditions.
Type "show copying" to see the conditions.
There is absolutely no warranty for GDB.  Type "show warranty" for details.
This GDB was configured as "--host=i686-pc-mingw32 --target=powerpc-elf32".
Setting up the environment for debugging gdb.
.gdbinit:5: Error in sourced command file:
No symbol table is loaded.  Use the "file" command.

(gdb) symbol-file n:/temp/ps2ism/ps2ism.x
Reading symbols from n:/temp/ps2ism/ps2ism.x...unknown symbol type 0x1e...done.

(gdb) target remote 127.0.0.1:10372
127.0.0.1:10372: Bad file descriptor.

So it doesn't seem to be able to read my binary (which the prebuilt gdb
has no problems with) and network seems also disfunctional. How can
I go on?

Thanks

bye  Fabi


^ permalink raw reply	[flat|nested] 6+ messages in thread

* ser-win32.c (was Re: Compiling error)
  2004-08-05  9:48     ` Fabian Cenedese
@ 2004-08-06  6:22       ` Fabian Cenedese
  2004-08-06  8:27       ` Compiling error Eli Zaretskii
  1 sibling, 0 replies; 6+ messages in thread
From: Fabian Cenedese @ 2004-08-06  6:22 UTC (permalink / raw)
  To: gdb


>>So if I need a cross-target gdb (running on win32, debugging ppc) is
>>the MinGW variant the only one that works? I thought that there are
>>also cygwin versions of gdb... but maybe only win32-win32.
>>I found the sgtty.h, it's in the glibc, so it may work ok if I install that
>>as well. But I first try the MinGW one.
>
>So I tried (and fiddled a lot!) again with MSYS and MinGW and got
>a gdb.exe. But it has the same problems as the one I built with DJGPP.
>
>This is the official http://prdownloads.sf.net/mingw/gdb-5.2.1-1-src.tar.bz2,
>configured with --target=powerpc-elf32.
>
>GNU gdb 5.2.1
>Copyright 2002 Free Software Foundation, Inc.
>GDB is free software, covered by the GNU General Public License, and you are
>welcome to change it and/or distribute copies of it under certain conditions.
>Type "show copying" to see the conditions.
>There is absolutely no warranty for GDB.  Type "show warranty" for details.
>This GDB was configured as "--host=i686-pc-mingw32 --target=powerpc-elf32".
>Setting up the environment for debugging gdb.
>.gdbinit:5: Error in sourced command file:
>No symbol table is loaded.  Use the "file" command.
>
>(gdb) symbol-file n:/temp/ps2ism/ps2ism.x
>Reading symbols from n:/temp/ps2ism/ps2ism.x...unknown symbol type 0x1e...done.
>
>(gdb) target remote 127.0.0.1:10372
>127.0.0.1:10372: Bad file descriptor.
>
>So it doesn't seem to be able to read my binary (which the prebuilt gdb
>has no problems with) and network seems also disfunctional. How can
>I go on?

(Changing --target to powerpc-eabi didn't change anything btw)

After looking through the sources I found that serial/TCP connection
won't work when built with MinGW. Are there better chances if I build
it with cygwin? Or what would it take to create a "ser-win32.c"? I'm
only interested in network connection right now, and the socket stuff
is quite similar between unix and win32. Or has anybody already
created one?

Thanks

bye  Fabi


^ permalink raw reply	[flat|nested] 6+ messages in thread

* Re: Compiling error
  2004-08-05  9:48     ` Fabian Cenedese
  2004-08-06  6:22       ` ser-win32.c (was Re: Compiling error) Fabian Cenedese
@ 2004-08-06  8:27       ` Eli Zaretskii
  1 sibling, 0 replies; 6+ messages in thread
From: Eli Zaretskii @ 2004-08-06  8:27 UTC (permalink / raw)
  To: Fabian Cenedese; +Cc: gdb

> Date: Thu, 05 Aug 2004 11:49:20 +0200
> From: Fabian Cenedese <Cenedese@indel.ch>
> 
> (gdb) symbol-file n:/temp/ps2ism/ps2ism.x
> Reading symbols from n:/temp/ps2ism/ps2ism.x...unknown symbol type 0x1e...done.
> 
> (gdb) target remote 127.0.0.1:10372
> 127.0.0.1:10372: Bad file descriptor.
> 
> So it doesn't seem to be able to read my binary (which the prebuilt gdb
> has no problems with) and network seems also disfunctional. How can
> I go on?

I'd try the Cygwin build.  I don't think any other DOS/Windows based
port supports anything but the native debugging.

^ permalink raw reply	[flat|nested] 6+ messages in thread

end of thread, other threads:[~2004-08-06  8:27 UTC | newest]

Thread overview: 6+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2004-08-04  8:41 Compiling error Fabian Cenedese
2004-08-04 16:38 ` Eli Zaretskii
2004-08-05  6:34   ` Fabian Cenedese
2004-08-05  9:48     ` Fabian Cenedese
2004-08-06  6:22       ` ser-win32.c (was Re: Compiling error) Fabian Cenedese
2004-08-06  8:27       ` Compiling error Eli Zaretskii

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).