public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "ro at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug modula2/105391] New: gm2 doesn't heed --with-gmp* Date: Tue, 26 Apr 2022 10:53:10 +0000 [thread overview] Message-ID: <bug-105391-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105391 Bug ID: 105391 Summary: gm2 doesn't heed --with-gmp* Product: gcc Version: 12.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: modula2 Assignee: gaius at gcc dot gnu.org Reporter: ro at gcc dot gnu.org Target Milestone: --- When building the current devel/modula-2 branch on i686-pc-linux-gnu for comparison's sake, the build failed like this In file included from /vol/gcc/src/hg/master/modula-2/gcc/m2/mc-boot/GAssertion.c:29: /vol/gcc/src/hg/master/modula-2/gcc/system.h:702:10: fatal error: gmp.h: No such file or directory 702 | #include <gmp.h> | ^~~~~~~ compilation terminated. and many many more similar errors. The system in question hadn't installed gmp.h in system directories, but only in a separate prefix specified with --with-gmp. However, gcc/m2/Make-lang.in doesn't heed GMPINC/GMPLIB. The attached patch fixes this by adding $(INCLUDES) in many places. It was enough to let the build succeed, but is certainly hacky in that it may add the variable in more places than necessary. I found the makefile extremely hard to deal with because it's extremely repetitive.
next reply other threads:[~2022-04-26 10:53 UTC|newest] Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-04-26 10:53 ro at gcc dot gnu.org [this message] 2022-04-26 10:53 ` [Bug modula2/105391] " ro at gcc dot gnu.org 2022-04-28 13:39 ` 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-105391-4@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: linkBe 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).