This is the mail archive of the gdb-patches@sourceware.org mailing list for the GDB project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: [RFA 5/5] New patches to support --enable-targets=all for mingw64


> But shouldn't we then clearly state that we drop hpux 10.X versions
> support?

We can. I don't think this is necessary, but Eli might think differently.
In any case, it doesn't cost much to add a NEWS entry mentioning it.

>   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?

For a platform such as pa-hpux, I would do the strict minimum to make
it work. I think you can just remove the function and assume version
is 11 or higher.

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

It may sound harsh, but I personally think that the input from HP/UX
developers in general is only of moderate interest to us.  As long as
no one steps up to the plate to support version 10.x of pa-hpux, we don't
have the necessary means to do so.  In fact, pa-hpux in general hasn't
received much attention in the last few years.  The only reason why
I haven't discussed its removal is because I am still planning on
contributing support for ia64-hpux, which should share a lot of code
with pa-hpux support.

My suggestion in this case is to KISS. If it turns out that this affects
a developer who wants to upgrade to gdb-7.3, then we can think of
alternative strategies, such as the one you suggested, and have him
test it. Otherwise, the user should just stay with the older version
of GDB.

-- 
Joel


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]