From: Alejandro Colomar <alx.manpages@gmail.com>
To: gcc@gcc.gnu.org
Subject: [BUG] README: Reference to non-existent path?
Date: Mon, 14 Nov 2022 16:02:48 +0100 [thread overview]
Message-ID: <d3db7bbf-fc05-618d-51c8-cdecbbeab081@gmail.com> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 2619 bytes --]
Hi,
I'm trying to understand a few implementation details of gcc for implementing a
new warning. For that, I first read the GCC manual [1].
[1]: <https://gcc.gnu.org/onlinedocs/gcc-12.2.0/gcc.pdf>
However, that manual has nothing about internals, such as 'LangEnabledBy()'.
Then I checked what's in the root of the repo to see what I can read:
$ ls
ABOUT-NLS config-ml.in libcody libvtv
COPYING config.guess libcpp ltgcc.m4
COPYING.LIB config.rpath libdecnumber ltmain.sh
COPYING.RUNTIME config.sub libffi lto-plugin
COPYING3 configure libgcc ltoptions.m4
COPYING3.LIB configure.ac libgfortran ltsugar.m4
ChangeLog contrib libgo ltversion.m4
ChangeLog.jit depcomp libgomp lt~obsolete.m4
ChangeLog.tree-ssa fixincludes libiberty maintainer-scripts
INSTALL gcc libitm missing
MAINTAINERS gnattools libobjc mkdep
Makefile.def gotools liboffloadmic mkinstalldirs
Makefile.in include libphobos move-if-change
Makefile.tpl install-sh libquadmath multilib.am
README intl libsanitizer symlink-tree
ar-lib libada libssp test-driver
c++tools libatomic libstdc++-v3 ylwrap
compile libbacktrace libtool-ldflags zlib
config libcc1 libtool.m4
The only interesting file seems to be the README. Let's see what it says:
> The directory INSTALL contains copies of the installation information
> as HTML and plain text. The source of this information is
> gcc/doc/install.texi. The installation information includes details
> of what is included in the GCC sources and what files GCC installs.
>
> See the file gcc/doc/gcc.texi (together with other files that it
> includes) for usage and porting information. An online readable
> version of the manual is in the files gcc/doc/gcc.info*.
Okay, let's see the online readable version of the manual:
$ ls gcc/doc/gcc.info*
ls: cannot access 'gcc/doc/gcc.info*': No such file or directory
No files with that glob(7). BTW, it might be interesting to provide that manual
in a package, so that I could install it as something like:
apt-get install gcc-doc-internal
Cheers,
Alex
--
<http://www.alejandro-colomar.es/>
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next reply other threads:[~2022-11-14 15:02 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-14 15:02 Alejandro Colomar [this message]
2022-11-14 15:32 ` Jonathan Wakely
2022-11-14 15:36 ` Jonathan Wakely
2022-11-14 17:00 ` Alejandro Colomar
2022-11-14 18:24 ` Joseph Myers
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=d3db7bbf-fc05-618d-51c8-cdecbbeab081@gmail.com \
--to=alx.manpages@gmail.com \
--cc=gcc@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).