Opened 4 years ago

Closed 4 years ago

Last modified 4 years ago

#16428 closed bug (fixed)

[Build System] configure: error: no version of fib2m found in path: generic

Reported by: diver Owned by: tqh
Priority: normal Milestone: R1/beta3
Component: Build System Version: R1/beta2
Keywords: Cc:
Blocked By: Blocking: #16432
Platform: All

Description

I updated buildtools to btrev43161 just to see if they still build on macOS 10.14.6. I used the following steps:

brew install autoconf xorriso gawk git wget nasm less mpfr gmp libmpc bison mtools
brew link bison --force
git clone --depth=1 https://review.haiku-os.org/buildtools
git clone https://review.haiku-os.org/haiku
cd haiku
mkdir generated; cd generated
../configure --build-cross-tools x86_64 ../../buildtools

Which end with:

configure: error: no version of fib2m found in path: generic
make[1]: *** [configure-gmp] Error 1
make: *** [all] Error 2
ERROR: Building gcc failed.

Change History (8)

comment:1 by BillyBlaze, 4 years ago

I am experiencing the same issue building on Ubuntu 20.04 LTS from head. I had successfully built it with the same steps on July 12th but when I attempted to on July 19th it failed and is still failing. I assume the gmp changes in btrev43160 are responsible.

comment:2 by tqh, 4 years ago

Seems libgmp has some new requirement, I'll take a look, it does build on my rather stripped Debian box though, so do you do anything special?

comment:3 by tqh, 4 years ago

I know the problem:

buildtools/gcc/gmp/mpn/generic[master]$ git add fib2m.c 
The following paths are ignored by one of your .gitignore files:
gcc/gmp/mpn/generic/fib2m.c
Use -f if you really want to add them.

Our .gitignore made some files ignored in the upgrade. :(
And since it is in gitignore, I don't see it in git status..

Fix coming up..

comment:4 by tqh, 4 years ago

Blocking: 16432 added

comment:5 by tqh, 4 years ago

Can you please check btrev43162 or later?

comment:6 by diver, 4 years ago

Resolution: fixed
Status: assignedclosed

This one seems fixed. I opened follow up ticket #16434.

comment:7 by BillyBlaze, 4 years ago

Works perfectly again for me as well. Thanks!

comment:8 by nielx, 4 years ago

Milestone: UnscheduledR1/beta3

Assign fix to milestone:R1/beta3, as it looks like this fix will be part of that release.

As we started with the previous beta, we would like to use the Milestone field for fixed tickets to log from which release the improvement will be out. Therefore it is very much appreciated to assign the milestone when closing a ticket as fixed.

Note: See TracTickets for help on using tickets.