From: Andrew Over <andrew@teknema.com>
To: Jon K Hellan <hellan@acm.org>
Cc: insight@sourceware.cygnus.com
Subject: Re: Build problem Linux/i386/Debian/Potato
Date: Thu, 10 Feb 2000 05:17:00 -0000 [thread overview]
Message-ID: <20000210231710.A9204@boh.localnet> (raw)
In-Reply-To: <20000210113220.A26876@parus.parus.no>
Hi Jon.
On Thu, Feb 10, 2000 at 11:32:20AM +0100, Jon K Hellan wrote:
> I have build problems on Linux i386 Debian Potato. I've managed to work
> around the compilation errors, but get quite a few segfaults from the
> resulting binary. I am trying to build insight-20000131.
You're not the only one. In fact, this isn't specifically an insight
problem. It's filed as bug 54738 against debian's gdb package (which
can't be compiled either).
[SNIP]
> The problems are:
>
> - lin-thread.c sees conflicting types for lwpid_t and psaddr_t. I
> could silence the compiler by removing these definitions from
> gdb_proc_service.h.
>
> - i386-linux-nat.c sees a definition of fpregset_t which does not
> contain the members it expects.
My guess as to what's going on is that the glibc people have tried to
make a type opaque. Unfortunately, this type is still needed by the
gdb people.
As a result, I'm not really sure who is ultimately responsible. I'd
considered just posting to both mailing lists and letting the internal
people sort it out :)
I'm also not really sure why this problem is only afflicting debian
people -- it might just be a case of having a hideously up to date
libc6-dev package in comparison to the other distributions (apt is
wonderful).
I've attached the patch that I wound up using to get this working. It
is very nasty, but makes for a short term solution. Credit to
whomever originally filed bug 54738 :)
Cheers,
--Andrew
prev parent reply other threads:[~2000-02-10 5:17 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-02-10 3:20 Jon K Hellan
2000-02-10 5:17 ` Andrew Over [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=20000210231710.A9204@boh.localnet \
--to=andrew@teknema.com \
--cc=hellan@acm.org \
--cc=insight@sourceware.cygnus.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).