public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Jonny Grant <jg@jguk.org>
To: Jonathan Wakely <jwakely.gcc@gmail.com>
Cc: GCC <gcc@gcc.gnu.org>
Subject: Re: host-x86_64-pc-linux-gnu/gcc/xgcc: No such file or directory
Date: Wed, 29 Nov 2023 14:44:43 +0000	[thread overview]
Message-ID: <8b1d2871-b1e1-4f6a-985a-a66d1b2fe40e@jguk.org> (raw)
In-Reply-To: <CAH6eHdQNRRQH09J_x+vUBF1WUXGEaVkBy+_gC8BWXZ3EkhKxFg@mail.gmail.com>



On 29/11/2023 13:05, Jonathan Wakely wrote:
> On Wed, 29 Nov 2023 at 12:59, Jonny Grant <jg@jguk.org> wrote:
>>
>> Hello
>>
>> Has anyone encountered this when compiling gcc from source? libgomp doesn't build due to xgcc missing
>>
>> I got latest git, did
>> ./configure --disable-multilib
> 
> Don't build in the source directory: https://gcc.gnu.org/wiki/FAQ#configure
> 
>> make html
> 
> Try make all-gcc before make html.


Sure. 

It gets stuck on genmodes.cc



../gcc_doc/configure --prefix=/home/jonny/code/repos/gcc_tests/gcc_install --disable-multilib

$ make all-gcc
<snip>
make[1]: Entering directory '/home/jonny/code/repos/gcc_tests/gcc_build/gcc'
g++ -std=c++11 -c   -g -O2   -DIN_GCC    -fno-exceptions -fno-rtti -fasynchronous-unwind-tables -W -Wall -Wno-narrowing -Wwrite-strings -Wcast-qual -Wmissing-format-attribute -Wconditionally-supported -Woverloaded-virtual -pedantic -Wno-long-long -Wno-variadic-macros -Wno-overlength-strings -fno-common  -DHAVE_CONFIG_H  -DGENERATOR_FILE -I. -Ibuild -I../../gcc_doc/gcc -I../../gcc_doc/gcc/build -I../../gcc_doc/gcc/../include  -I../../gcc_doc/gcc/../libcpp/include  \
	-o build/genmodes.o ../../gcc_doc/gcc/genmodes.cc
In file included from ../../gcc_doc/gcc/bconfig.h:3,
                 from ../../gcc_doc/gcc/genmodes.cc:20:
../../gcc_doc/gcc/auto-host.h:2717:16: error: declaration does not declare anything [-fpermissive]
 2717 | #define rlim_t long
      |                ^~~~
In file included from ../../gcc_doc/gcc/genmodes.cc:21:
../../gcc_doc/gcc/system.h:500:14: error: conflicting declaration of C function ‘void* sbrk(int)’
  500 | extern void *sbrk (int);
      |              ^~~~
In file included from ../../gcc_doc/gcc/system.h:302:
/usr/include/unistd.h:1076:14: note: previous declaration ‘void* sbrk(intptr_t)’
 1076 | extern void *sbrk (intptr_t __delta) __THROW;
      |              ^~~~
../../gcc_doc/gcc/system.h:508:14: error: ambiguating new declaration of ‘char* strstr(const char*, const char*)’
  508 | extern char *strstr (const char *, const char *);
      |              ^~~~~~
In file included from /usr/include/c++/13/cstring:42,
                 from ../../gcc_doc/gcc/system.h:241:
/usr/include/string.h:343:1: note: old declaration ‘const char* strstr(const char*, const char*)’
  343 | strstr (const char *__haystack, const char *__needle) __THROW
      | ^~~~~~
../../gcc_doc/gcc/system.h:556:20: error: conflicting declaration of C function ‘const char* strsignal(int)’
  556 | extern const char *strsignal (int);
      |                    ^~~~~~~~~
/usr/include/string.h:478:14: note: previous declaration ‘char* strsignal(int)’
  478 | extern char *strsignal (int __sig) __THROW;
      |              ^~~~~~~~~
In file included from ../../gcc_doc/gcc/system.h:729:
../../gcc_doc/gcc/../include/libiberty.h:112:14: error: ambiguating new declaration of ‘char* basename(const char*)’
  112 | extern char *basename (const char *) ATTRIBUTE_RETURNS_NONNULL ATTRIBUTE_NONNULL(1);
      |              ^~~~~~~~
/usr/include/string.h:537:26: note: old declaration ‘const char* basename(const char*)’
  537 | extern "C++" const char *basename (const char *__filename)
      |                          ^~~~~~~~
make[1]: *** [Makefile:2987: build/genmodes.o] Error 1
make[1]: Leaving directory '/home/jonny/code/repos/gcc_tests/gcc_build/gcc'
make: *** [Makefile:4996: all-gcc] Error 2


Kind regards, Jonny

  reply	other threads:[~2023-11-29 14:44 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-29 12:59 Jonny Grant
2023-11-29 13:05 ` Jonathan Wakely
2023-11-29 14:44   ` Jonny Grant [this message]
2023-11-29 15:55     ` Jonathan Wakely

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=8b1d2871-b1e1-4f6a-985a-a66d1b2fe40e@jguk.org \
    --to=jg@jguk.org \
    --cc=gcc@gcc.gnu.org \
    --cc=jwakely.gcc@gmail.com \
    /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).