Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Stan Shebs <shebs@cygnus.com>
To: rodneybrown@pmsc.com
Cc: gdb@cygnus.com
Subject: Re: gdb-19990209 snapshot fails to build with missing all target
Date: Thu, 01 Apr 1999 00:00:00 -0000	[thread overview]
Message-ID: <199902232259.OAA08036@andros.cygnus.com> (raw)
In-Reply-To: <9902149190.AA919048273@cc.pmsc.com>

   From: rodneybrown@pmsc.com
   Date: Mon, 15 Feb 99 14:05:23 -0500

   Snapshot gdb-19990209 fails to build because of missing opcode/Makefile
   all target, when configured on AIX-4.2.0, UnixWare 2.1.1 and SunOS 4.1.3.
   NB - while I'm patching up rather than pulling down a full tar.gz, the brik -Cb
   < gdb.crc
   worked & I did (belatedly) run the postpatch scripts.

I think this is all resolved now.  There is some experimentation going on
in opcodes-land...

   Further look at missing SOLIB_.* externals building on AIX-4.2.0
   I think that the relevant defines could be copied straight from the
   coff-solib.h and the include for xcoffsolib.h be pushed into a
   config/ header file.

Copying the definitions should work, because they are just placeholders
until somebody besides HP defines them usefully for their OS.  Actually,
looking at all of the *solib.h stuff, I seem some candidates for
simplification - one file (coff-solib.h) is never used, some are used
in inappropriate places, and they all go to a lot of trouble to use
macros, when a function pointer would be just as easy and not require
a bunch of #define/#include trickery.

   The reason I haven't patched this in is that
   gdb/eval.c includes xcofflib.h for a struct vmap definition.

This whole thing is moderately tangled - it's ugly for AIX because
the main program can be in a dynamically loaded library, which makes
trouble for GDB algorithms that expect to know where to find _start
and suchlike.  I hear rumors of IBMers hacking on all this anyway,
so there's not much point in going to be a lot of trouble on xcoff
solib stuff until we hear more about what they're up to.

							Stan



      reply	other threads:[~1999-04-01  0:00 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-04-01  0:00 rodneybrown
1999-04-01  0:00 ` Stan Shebs [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=199902232259.OAA08036@andros.cygnus.com \
    --to=shebs@cygnus.com \
    --cc=gdb@cygnus.com \
    --cc=rodneybrown@pmsc.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