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

glibc-2.33.9000 Failed to adapt loongarch #28

Open
SevDaisy opened this issue Apr 20, 2022 · 2 comments
Open

glibc-2.33.9000 Failed to adapt loongarch #28

SevDaisy opened this issue Apr 20, 2022 · 2 comments

Comments

@SevDaisy
Copy link

SevDaisy commented Apr 20, 2022

while I run glibc-glibc-2.33.9000/configure --host=loongarch-linux-gnu, error happened as checking host system type... Invalid configuration 'loongarch-linux-gnu': machine 'loongarch-unknown' not recognized.

By reading the source code, I run as glibc-glibc-2.33.9000/scripts/config.sub loongarch-linux-gnu again, which is the line that directly caused the error. Throw adding set -x at glibc-glibc-2.33.9000/scripts/config.sub,I get the following msg:

root@9848f4ac5022:/build# /build/glibc-glibc-2.33.9000/scripts/config.sub loongarch-linux-gnu
+ timestamp=2019-01-01
+ echo /build/glibc-glibc-2.33.9000/scripts/config.sub
+ sed -e s,.*/,,
+ me=config.sub
+ usage=Usage: /build/glibc-glibc-2.33.9000/scripts/config.sub [OPTION] CPU-MFR-OPSYS or ALIAS

Canonicalize a configuration name.

Options:
  -h, --help         print this help, then exit
  -t, --time-stamp   print date of last modification, then exit
  -v, --version      print version number, then exit

Report bugs and patches to <[email protected]>.
+ version=GNU config.sub (2019-01-01)

Copyright 1992-2019 Free Software Foundation, Inc.

This is free software; see the source for copying conditions.  There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
+ help=
Try `config.sub --help' for more information.
+ test 1 -gt 0
+ break
+ IFS=- read field1 field2 field3 field4
+ maybe_os=linux-gnu
+ basic_machine=loongarch
+ os=linux-gnu
+ cpu=loongarch
+ vendor=unknown
+ unset -v basic_machine
+ echo Invalid configuration `loongarch-linux-gnu': machine `loongarch-unknown' not recognized
Invalid configuration `loongarch-linux-gnu': machine `loongarch-unknown' not recognized
+ exit 1

Those msgs lead me to line [1157~1252] of glibc-glibc-2.33.9000/scripts/config.sub.There has a so long supported cpu list, without any one seem like loongson

@SevDaisy
Copy link
Author

sorry, it's my fault.

how can I run it at tag glibc-2.33.9000....

@xen0n
Copy link

xen0n commented Apr 20, 2022

I don't know why you insist on using the 2.33 version when working 2.35 and trunk versions are available, and 2.33 having incompatible symbol versions, but you should be using loongarch64-unknown-linux-gnu as the triple.

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

2 participants