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

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

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

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

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

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,

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

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

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

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]: However, that manual has nothing about internals, such as 'LangEnabledBy()'. Then I checked