Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: "Pierre Muller" <pierre.muller@ics-cnrs.unistra.fr>
To: "'Joel Brobecker'" <brobecker@adacore.com>
Cc: <gdb-patches@sourceware.org>
Subject: RE: [RFA 5/5] New patches to support --enable-targets=all for mingw64
Date: Tue, 14 Sep 2010 11:44:00 -0000	[thread overview]
Message-ID: <000c01cb53e1$56476e60$02d64b20$@muller@ics-cnrs.unistra.fr> (raw)
In-Reply-To: <20100913181100.GC3845@adacore.com>



> -----Message d'origine-----
> De : gdb-patches-owner@sourceware.org [mailto:gdb-patches-
> owner@sourceware.org] De la part de Joel Brobecker
> Envoyé : Monday, September 13, 2010 8:11 PM
> À : Pierre Muller
> Cc : gdb-patches@sourceware.org
> Objet : Re: [RFA 5/5] New patches to support --enable-targets=all for
> mingw64
> 
> > 5) solib-som.c is a tdep file (it is listed in ALL_TARGET_OBS)
> > but it tries to get the hpux system version trough
> > a direct system call, which probably leads to wrong results
> > on other systems too.
> 
> Ugh!
> 
> I have a more radical suggestion: AFAIK, we have not supported pa-hpux
> version 10.x or older for quite a while.  According to HP, the first
> 11.x release was in 1997, and the l0.x release was also in 1997.

  I am not against as I have no interest in HPUX in general...
 
> Given that this version number is used to determine whether the OS
> version is 11 or more, we can assume that this is always true, and
> thus get rid of the function (and the associated include) entirely.

  But shouldn't we then clearly state that we drop hpux 10.X versions 
support?
 
  Should we remove the function get_hpux_major_release 
completely, or turn it into a function returning a variable,
that could be set by some command like
"set hpux-major-release-version XX"
that would allow people using it on an old HPUX 10.X
to still get old behavior?

  Does anyone know of a good mailing list for HPUX
developers to which we could forward that question?


Pierre Muller
Pascal language support maintainer for GDB




  reply	other threads:[~2010-09-14  7:49 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-09-10 15:43 Pierre Muller
2010-09-13 19:14 ` Joel Brobecker
2010-09-14 11:44   ` Pierre Muller [this message]
2010-09-14 15:24     ` [RFC] hpux code fix ( was [RFA 5/5] New patches to support --enable-targets=all for mingw64) Pierre Muller
2010-09-27 17:34       ` [PING][RFC] " Pierre Muller
2010-09-27 17:43         ` Pedro Alves
2010-09-14 19:39     ` [RFA 5/5] New patches to support --enable-targets=all for mingw64 Joel Brobecker

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='000c01cb53e1$56476e60$02d64b20$@muller@ics-cnrs.unistra.fr' \
    --to=pierre.muller@ics-cnrs.unistra.fr \
    --cc=brobecker@adacore.com \
    --cc=gdb-patches@sourceware.org \
    /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