public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "gaiusmod2 at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug modula2/101388] Unconditional use of __MAX_BAUD
Date: Sun, 15 Aug 2021 13:38:27 +0000	[thread overview]
Message-ID: <bug-101388-4-ysmorgkAaW@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-101388-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101388

--- Comment #1 from Gaius Mulley <gaiusmod2 at gmail dot com> ---
"ro at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> writes:

> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101388
>
>             Bug ID: 101388
>            Summary: Unconditional use of __MAX_BAUD
>            Product: gcc
>            Version: 12.0
>             Status: UNCONFIRMED
>           Severity: normal
>           Priority: P3
>          Component: modula2
>           Assignee: unassigned at gcc dot gnu.org
>           Reporter: ro at gcc dot gnu.org
>                 CC: gaiusmod2 at gmail dot com
>   Target Milestone: ---
>             Target: *-*-solaris2.11
>
> Building the devel/modula-2 branch on Solaris 11 fails with undefined
> references
> to __MAX_BAUD in two places:
>
> /vol/gcc/src/git/modula-2/gcc/m2/mc-boot-ch/Gtermios.c: In function
> 'termios_GetFlag':
> /vol/gcc/src/git/modula-2/gcc/m2/mc-boot-ch/Gtermios.c:872:27: error:
> '__MAX_BAUD' undeclared (first use in this function)
>        *b = ((t->c_cflag & __MAX_BAUD) == __MAX_BAUD);
>                            ^~~~~~~~~~
>
> /vol/gcc/src/git/modula-2/gcc/m2/gm2-libs-ch/termios.c: In function
> 'termios_GetFlag':
> /vol/gcc/src/git/modula-2/gcc/m2/gm2-libs-ch/termios.c:877:27: error:
> '__MAX_BAUD' undeclared (first use in this function)
>   877 |       *b = ((t->c_cflag & __MAX_BAUD) == __MAX_BAUD);
>       |                           ^~~~~~~~~~
> __MAX_BAUD seems to be Linux/glibc specific, but the current problem is
> obviously
> cause by a wrong guard which checks for defined(MAX) instead of
> defined(__MAX_BAUD).
>
> Correcting this lets the build continue.

many thanks for the report - now fixed in the git repro,


regards,
Gaius

  reply	other threads:[~2021-08-15 13:38 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-07-09 12:18 [Bug modula2/101388] New: " ro at gcc dot gnu.org
2021-08-15 13:38 ` gaiusmod2 at gmail dot com [this message]
2021-08-15 21:29 ` [Bug modula2/101388] " pinskia at gcc dot gnu.org
2021-09-14 10:05 ` ro at gcc dot gnu.org
2021-09-14 10:08 ` ro at gcc dot gnu.org
2021-10-13 17:04 ` gaiusmod2 at gmail dot com
2022-01-18 11:32 ` gaius at gcc dot gnu.org

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=bug-101388-4-ysmorgkAaW@http.gcc.gnu.org/bugzilla/ \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@gcc.gnu.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).