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

mill 404 when building XiangShan tag v2.1 #4130

Open
3 tasks done
Liujiaqi-jlu opened this issue Jan 4, 2025 · 5 comments · May be fixed by OpenXiangShan/xs-env#54
Open
3 tasks done

mill 404 when building XiangShan tag v2.1 #4130

Liujiaqi-jlu opened this issue Jan 4, 2025 · 5 comments · May be fixed by OpenXiangShan/xs-env#54
Labels
problem Problem requiring help

Comments

@Liujiaqi-jlu
Copy link

Liujiaqi-jlu commented Jan 4, 2025

Before start

  • I have read the XiangShan Documents. 我已经阅读过香山文档。
  • I have searched the previous issues and did not find anything relevant. 我已经搜索过之前的 issue,并没有找到相关的。
  • I have searched the previous discussions and did not find anything relevant. 我已经搜索过之前的 discussions,并没有找到相关的。

Describe you problem

你好,我是按照文档的步骤来的。当我在执行make emu -j32想生成完整的香山核的时候,报错如下
4339639b-efe5-41ce-9fae-4a0faec1d038
不知道是什么资源访问出错,我也尝试去添加参数去打印出错的url,但是没有成功,在观察makfile和build.sbt后也没有找到结果。想请教下,这是什么原因呢。

What did you do before

之前的操作都是按照手册来的,都已经成功,用的是v2.1版本,尚未进行nemu相关的操作

Environment

  • XiangShan branch:
  • XiangShan commit id:
  • NEMU commit id:
  • SPIKE commit id:
  • Operating System:
  • gcc version: gcc (Ubuntu 13.3.0-6ubuntu2~24.04) 13.3.0
  • mill version: Mill Build Tool version 0.11.12
  • java version: 11.0.25

Additional context

No response

[TRANSLATION]

Describe you problem

Hello, I followed the steps in the documentation. When I tried to run make emu -j32 to generate the complete XiangShan core, I encountered the following error:4339639b-efe5-41ce-9fae-4a0faec1d038
I’m not sure what caused the resource access error. I also tried adding parameters to print the URL causing the issue, but it didn’t work. After inspecting the Makefile and build.sbt, I still couldn’t find the cause. Could you please help explain what might be the reason for this error?

What did you do before

The previous steps were all successfully completed by following the manual, and I am using version 2.1. I haven't performed any NEMU-related operations yet.

@Liujiaqi-jlu Liujiaqi-jlu added the problem Problem requiring help label Jan 4, 2025
@Tang-Haojin Tang-Haojin changed the title 生成香山核的仿真程序时出现404 404 when building XiangShan Jan 4, 2025
@Tang-Haojin
Copy link
Member

This is a known issue for older mill scripts. You may try to update your mill script from this url and replace your mill shown by which mill.

@Tang-Haojin Tang-Haojin linked a pull request Jan 4, 2025 that will close this issue
@Tang-Haojin
Copy link
Member

See also: com-lihaoyi/mill#1482 (comment).

@Liujiaqi-jlu
Copy link
Author

Liujiaqi-jlu commented Jan 4, 2025

This is a known issue for older mill scripts. You may try to update your mill script from this url and replace your mill shown by which mill.

谢谢回复,版本问题现在已经解决了,但是在构建的时候他说找不到构建的simtop.v,请问这个要怎么解决呢
e70d2308-33c4-4dad-9122-1e776f6823e7

[TRANSLATION]
Thanks for your response. The version issue has now been resolved, but during the build process, it reports that it cannot find simtop.v. How should I solve this issue?

@poemonsense
Copy link
Member

v2.1 requires mill 0.9.8. Newer Mill versions have different URLs for downloading the mill tool.

@poemonsense
Copy link
Member

This is a known issue for older mill scripts. You may try to update your mill script from this url and replace your mill shown by which mill.

谢谢回复,版本问题现在已经解决了,但是在构建的时候他说找不到构建的simtop.v,请问这个要怎么解决呢 e70d2308-33c4-4dad-9122-1e776f6823e7

You forgot to remove the -v argument. It is not in our script and may be added by yourself.

@poemonsense poemonsense changed the title 404 when building XiangShan mill 404 when building XiangShan tag v2.1 Jan 4, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
problem Problem requiring help
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants