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/101391] New: Unresolved reference to module getopt
Date: Fri, 09 Jul 2021 12:27:53 +0000 [thread overview]
Message-ID: <bug-101391-4@http.gcc.gnu.org/bugzilla/> (raw)
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101391
Bug ID: 101391
Summary: Unresolved reference to module getopt
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
Target Milestone: ---
Created attachment 51123
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=51123&action=edit
Mechanical patch
The next build error from the devel/modula-2 branch occured like this:
/vol/gcc/src/git/modula-2/libgm2/libm2pim/../../gcc/m2/gm2-libs/GetOpt.mod:213:11:
error: the file containing the definition module ‘getopt’ cannot be found
213 | END GetOpt.
| ^
make[5]: *** [Makefile:950: GetOpt.lo] Error 1
make[5]: Leaving directory
'/var/gcc/gcc-12.0.0-20210708/11.4-gm2/i386-pc-solaris2.11/libgm2/libm2pim'
The module has been renamed to cgetopt since. I'm attaching a patch for
gcc/m2/gm2-libs/GetOpt.mod for correct this.
While the Makefile.am's reflect the new name, the corresponding Makefile.in's
haven't been regenerated.
On top of that, the current files have been generated with automake 1.16.1,
while gcc requires automake 1.15.1 as documented in install.text. To get
around
this, one first needs to regenerate aclocal.m4 with aclocal 1.15.1 in order to
be able rerun automake.
next reply other threads:[~2021-07-09 12:27 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-09 12:27 ro at gcc dot gnu.org [this message]
2021-08-13 16:19 ` [Bug modula2/101391] " gaiusmod2 at gmail dot com
2021-08-14 9:42 ` gaiusmod2 at gmail dot com
2021-09-14 10:02 ` ro at gcc dot gnu.org
2021-09-14 10:03 ` ro at gcc dot gnu.org
2021-10-25 11:36 ` ro at gcc dot gnu.org
2022-01-20 17:33 ` gaius at gcc dot gnu.org
2022-01-20 22:03 ` ro at CeBiTec dot Uni-Bielefeld.DE
2022-01-28 16:52 ` gaius at gcc dot gnu.org
2022-04-23 12:02 ` 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-101391-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: 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).