Re: [BUG] README: Reference to non-existent path?

[Joseph Myers]

On Mon, 14 Nov 2022, Alejandro Colomar via Gcc wrote:

> 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

That reference is for releases - those files are in release tarballs, but 
not in git or snapshots.

-- 
Joseph S. Myers
jos...@codesourcery.com

Re: [BUG] README: Reference to non-existent path?

[Alejandro Colomar via Gcc]

Hi Jonathan,

On 11/14/22 16:36, Jonathan Wakely wrote:

On Mon, 14 Nov 2022 at 15:03, Alejandro Colomar wrote:

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


"info gccint" already works fine on my distro. If it's not packaged
for yours, that's a distro issue.


It works.  I didn't know it existed :)

Maybe add a reference to it in the README?

Thanks!

Alex

--



OpenPGP_signature
Description: OpenPGP digital signature

Re: [BUG] README: Reference to non-existent path?

[Jonathan Wakely via Gcc]

On Mon, 14 Nov 2022 at 15:03, Alejandro Colomar wrote:
> 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

"info gccint" already works fine on my distro. If it's not packaged
for yours, that's a distro issue.

Re: [BUG] README: Reference to non-existent path?

[Jonathan Wakely via Gcc]

On Mon, 14 Nov 2022 at 15:03, Alejandro Colomar via Gcc  wrote:
>
> 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]: 

That's the user manual, for GCC internals see the gccint docs:
https://gcc.gnu.org/onlinedocs/gccint/Options.html#Options