From: Andrew Cagney <ac131313@ges.redhat.com>
To: Matthew H Bemis <bemis@iol.unh.edu>
Cc: Andrew Cagney <ac131313@cygnus.com>,
Elena Zannoni <ezannoni@redhat.com>,
Mike Cleary <mcleary@iol.unh.edu>,
gdb@sources.redhat.com, clp <clp@iol.unh.edu>
Subject: Re: *** [ser-tcp.o] Error 1 on alpha!
Date: Wed, 26 Jun 2002 20:28:00 -0000 [thread overview]
Message-ID: <3D1A8641.5020900@ges.redhat.com> (raw)
In-Reply-To: <DJEHKIJNENDCOJNKEBGKCELODFAA.bemis@iol.unh.edu>
> Hello,
> I agree it is not caused by the patch, but not many people test their
> patches on alpha.
> We download from cvs every day and build this. We have a stable build
> system. I can give you a cvs snapshot of when we took the source code from
> cvs if you'd like, and I can also provide any other information about the
> host machine upon request.
Would you have a time for the last successful build?
> I have all of the build logs available too if you'd like to see them got to:
> for alpha goto:
> ftp://alpha9.crl.dec.com/pub/autobuild/results/alpha6/basic-gcc_2.95.3/nativ
> e/toolchain/20020622-05:21:38-F/
> and click on the X-configure.blog log to see the configuration,and the
> X-make.blog for the compilation error
>
> to see alpha daily builds goto:
> http://handhelds.org/projects/toolchain/autobuild/build-results.php3
I suspect that the unfortunate reality is that someone is going to have
to roll up their sleeves and try to build GDB while logged into an Alpha
GNU/Linux system. Only that way can the look at the relevant headers
and figure out why things are going wrong. ser-*.c is pretty generic so
I'm puzzled as to why that doesn't build.
Anyway this:
> /mnt/buildsys/source/toolchain/gdb/ser-tcp.c: In function `net_open':
> /mnt/buildsys/source/toolchain/gdb/ser-tcp.c:67: warning: implicit declaration of function `strncmp'
> /mnt/buildsys/source/toolchain/gdb/ser-tcp.c:81: warning: implicit declaration of function `strncpy'
> /mnt/buildsys/source/toolchain/gdb/ser-tcp.c:83: warning: implicit declaration of function `atoi'
suggests that something is skewiff. ser-tcp.c unconditionally includes
"gdb_string.h" and that pulls in either <string.h> or <strings.h> so
should have those declarations visible?
Hmm, check the generated config.h for something strange.
Andrew
next prev parent reply other threads:[~2002-06-27 3:28 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-06-20 13:08 GDB *** [event-top.o] Error 1!! Mike Cleary
2002-06-20 14:00 ` Jim Blandy
2002-06-20 14:48 ` Elena Zannoni
2002-06-20 16:32 ` Andrew Cagney
2002-06-21 17:13 ` *** [ser-tcp.o] Error 1 on alpha! Matthew H Bemis
2002-06-22 10:09 ` Andrew Cagney
2002-06-22 10:23 ` Matthew H Bemis
2002-06-26 20:28 ` Andrew Cagney [this message]
2002-06-20 19:16 ` GDB *** [event-top.o] Error 1!! Matthew H Bemis
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3D1A8641.5020900@ges.redhat.com \
--to=ac131313@ges.redhat.com \
--cc=ac131313@cygnus.com \
--cc=bemis@iol.unh.edu \
--cc=clp@iol.unh.edu \
--cc=ezannoni@redhat.com \
--cc=gdb@sources.redhat.com \
--cc=mcleary@iol.unh.edu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
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).