Can't compile after update buildtools from btrev43158 to btrev43161 (btrev43159, btrev43160, btrev43161)

1

Hi all.
Can’t compile after update buildtools from btrev43158 to btrev43161 (btrev43159, btrev43160, btrev43161)

For x64

checking whether strtoll is declared… yes
checking whether strtoull is declared… yes
checking whether strverscmp is declared… yes
checking whether strnlen is declared… yes
checking whether canonicalize_file_name must be declared… no
checking for stdlib.h… (cached) yes
checking for unistd.h… (cached) yes
checking for getpagesize… (cached) yes
checking for working mmap… yes
checking for working strncmp… yes
configure: updating cache ./config.cache
configure: creating ./config.status
config.status: creating Makefile
config.status: creating testsuite/Makefile
config.status: creating config.h
config.status: executing default commands
make[1]: Leaving directory ‘/home/greekboy/AAA/cross-tools-x86_64/cross-tools-x86_64-build/gcc’
make: *** [Makefile:908: all] Error 2
ERROR: Building gcc failed.
greekboy@SATELLITE-P70-B:~/AAA/cross-tools-x86_64$

For x86gcc2_hybrid

configure: creating ./config.status
config.status: creating Makefile
config.status: creating testsuite/Makefile
config.status: creating config.h
config.status: executing default commands
make[1]: Leaving directory ‘/home/greekboy/AAA/cross-tools-x86_gcc2-x86/cross-tools-x86-build/gcc’
make: *** [Makefile:908: all] Error 2
ERROR: Building gcc failed.
greekboy@SATELLITE-P70-B:~/AAA/cross-tools-x86_gcc2-x86$

2

What kind of system are you running on?

@tqh’s changes may be related here.

3

No, this is gcc2 as shown in the log.

4

That is the second half of the post, the first half clearly shows “cross-tools-x86_64”.

5

Both gcc2 and gcc fail in makefile at 908. Very unlikely to be a problem to my changes that is only affecting one gcc was what I was after.

6

My system is Ubuntu 20.04

7

There is something wrong with the Makefile(s) at 908. As config generates these I am not sure where they are, and for me doing a search for Makefiles in buildtools and haiku dir I can’t really find any good matches. Your dir’s seems like you are building the gcc’s directly? Is that what you are doing?

8

I have been making the haiku image for a few years, twice a week for a hobby.
For x86gcc2hybrid
run the command for cross-tools
…/haiku/configure -j4 --build-cross-tools x86_gcc2 …/buildtools --build-cross-tools x86

For x64
…/haiku/configure -j4 --build-cross-tools x86_64 …/buildtools

9

An important observation.
I think during the compilation, some files are lost.
Screenshot%202020-07-22%2000%3A10%3A57

10

From Google Translate
========= Update Buildtools ==========
88896a1144
Already fully informed.
88896a1144
In the master branch
Your industry is familiar with ‘origin / master’.

Changes not prepared for submission:
(use “git add …” to update what will be submitted)
(use “git restore …” to discard changes in working directory)
modification: binutils / missing
modification: gcc / isl / missing
modification: gcc / missing

no changes were submitted to the submission (use “git add” and / or “git commit -a”)
Your industry is familiar with ‘origin / master’.

11

I have this problem as well and it only showed up recently; I have built the buildtools before on this computer and still have an older copy that I can use. Using the configure script to build a x86_64 compiler from Arch Linux:

../configure -j12 --build-cross-tools x86_64 ../../buildtools
12
  1. please report bugs at dev.haiku-os.org
  2. please include a complete build log. Your extract does not look like it includes the actual problem.
  3. are you sure it is because of changes in the buildtools, or could it be because of other changes in your OS, like, did Ubuntu update their gcc or bison or some other thing like that?
13

I made the ticket

https://dev.haiku-os.org/ticket/16432

14

It might help forcing the language to English, try with:

export LANG=C