Hi Thomas,
> (Sorry for being late with this -- I'm listed as a GNU/Hurd OS Port
> Maintainer, but I have not been CCed in the original patch email, and I'm
> only able to read gcc-patches/the Git log at irregular times.)
sorry for not including you in the Cc: I must have simply overlooked it
and the Cc: list was too long already ;-)
> How should this be fixed? Probably my moving the md_unwind_header
> definitions outside of...
>
> case ${host} in
> # Support site-specific machine types.
>
> ... (where they currently reside), and create a new ``case $host'' as
> done just above for enable_execute_stack, for example?
No, I don't think this is appropriate. For enable_execute_stack, we
have only 3 cases, so it's easier to create its own case statement, one
with many labels.
For md_unwind_header on the other hand, you'd have almost as many cases
as in the general case. I fear it's hard to have the configuration
split over too many places. So I'd suggest to split the affected cases
into Linux and non-Linux ones, with the slight duplication necessary for
extra_parts and tmake_file.
Rainer
--
-----------------------------------------------------------------------------
Rainer Orth, Center for Biotechnology, Bielefeld University
