From: Mark Kettenis <kettenis@chello.nl>
To: ac131313@redhat.com
Cc: msnyder@redhat.com, gdb-patches@sources.redhat.com
Subject: Re: [PATCH/RFC] Fix asm-source.exp on FreeBSD
Date: Fri, 30 May 2003 18:05:00 -0000 [thread overview]
Message-ID: <200305301805.h4UI5785012095@elgar.kettenis.dyndns.org> (raw)
In-Reply-To: <3EBD027F.8010403@redhat.com> (message from Andrew Cagney on Sat, 10 May 2003 09:45:35 -0400)
Date: Sat, 10 May 2003 09:45:35 -0400
From: Andrew Cagney <ac131313@redhat.com>
> Ever since asm-source.exp was changed to do the final link using
> gdb_compile, the tests have been failing for me. The problem is that
> FreeBSD's crt1.o defines some symbols (__progname, environ) that are
> referenced by libc.so, which makes the final link fail. Compiling
> statically fixes the problem.
>
> I'm fairly certain that NetBSD and probably OpenBSD suffer from the
> same problem, so perhaps I should change the regexp to *-*-*bsd*
> instead. Can someone check whether that's indeed the case.
>
> I've been using this patch in my local tree for quite some time now,
> so if I don't see any objections in the coming days, I'll check this
> in.
Honestly, I think it should be put back to using the linker directly.
The intent of the test was to exercise the assembler functionality, when
there was no C compiler. I confirmed this with Michael, the testsuite's
author.
I've never had the time to do it though :-(
Me neither :-(. Simply reverting to using the linker directly would
probably break quite a few targets. Fixing those problems would mean
making extensive changes to DejaGNU. Therefore I've checked my patch
in as a temporary workaround. These tests are pretty valuable, with
all the new unwinder stuff and such.
Mark
prev parent reply other threads:[~2003-05-30 18:05 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-10 11:05 Mark Kettenis
2003-05-10 14:24 ` Andrew Cagney
2003-05-30 18:05 ` Mark Kettenis [this message]
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=200305301805.h4UI5785012095@elgar.kettenis.dyndns.org \
--to=kettenis@chello.nl \
--cc=ac131313@redhat.com \
--cc=gdb-patches@sources.redhat.com \
--cc=msnyder@redhat.com \
/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