Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Build Failure: Debian sid gcc 11.2.0 #147

Open
beaglesnuf opened this issue Apr 18, 2022 · 4 comments
Open

Build Failure: Debian sid gcc 11.2.0 #147

beaglesnuf opened this issue Apr 18, 2022 · 4 comments

Comments

@beaglesnuf
Copy link

beaglesnuf commented Apr 18, 2022

not sure what the issue is here with the unknown option.

cc1: note: self-tests are not enabled in this build cc1plus: note: self-tests are not enabled in this build echo timestamp > s-selftest-c echo timestamp > s-selftest-c++ rm gcc.pod make[3]: Leaving directory '/tmp/build/musl-cross-make/build/local/x86_64-linux-musl/obj_gcc/gcc' make[2]: Leaving directory '/tmp/build/musl-cross-make/build/local/x86_64-linux-musl/obj_gcc' touch obj_gcc/gcc/.lc_built cd obj_musl && ../src_musl/configure --enable-optimize=yes --prefix= --host=x86_64-linux-musl CC="../obj_gcc/gcc/xgcc -B ../obj_gcc/gcc" LIBCC="../obj_gcc/x86_64-linux-musl/libgcc/libgcc.a" checking for C compiler... ../obj_gcc/gcc/xgcc -B ../obj_gcc/gcc checking whether C compiler works... no; compiler output follows: E: ../obj_gcc/gcc/as[108]: exec: --: unknown option make[1]: *** [Makefile:227: obj_musl/.lc_configured] Error 1 make[1]: Leaving directory '/tmp/build/musl-cross-make/build/local/x86_64-linux-musl' make: *** [Makefile:182: all] Error 2

@rofl0r
Copy link
Contributor

rofl0r commented Apr 18, 2022

musl's configure check whether the compiler works fails due to the built assembler having some problem with the passed command line. it would be useful if you could run the compile command musl's configure does using the same xgcc with strace -f. you may also want to join #musl irc on libera.chat so we can help you debug this in realtime.
in case you can't, it could be useful to provide the used binutils version, and please don't strip newlines from future pastes, this makes it really difficult to read your log.

@richfelker
Copy link
Owner

Something appears to be wrong with the as wrapper script gcc generated which is in obj_gcc/gcc/as under the build dir for your mcm run.

@beaglesnuf
Copy link
Author

beaglesnuf commented Apr 26, 2022

...provide the used binutils version, and please don't strip newlines from future pastes, this makes it really difficult to read your log.

2.38 and not sure why the newlines were stripped from a primary paste (but will correct in the future).

Something appears to be wrong with the as wrapper script gcc generated which is in obj_gcc/gcc/as under the build dir for your mcm run.

i'll try removing options one by one and see if that can narrow down the issue.

@rofl0r
Copy link
Contributor

rofl0r commented Apr 26, 2022

2.38

i'm not certain whether that version is actually supported. i think you should stick to one of the versions listed in patches/ directory.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants