OPUS Make 错误:OPUS MAKE:未知状态。停止
我们在构建基础设施中使用 OPUS Make。 (我猜基本上是传统的制作方式,周围有一些包装纸) 我们的代码库主要是 Java,我已经进行了几个月的更改和构建。没有问题。 突然,几天前,当我尝试构建时,我开始看到此错误:
OPUS MAKE: Unknown status. Stop.
无论我尝试构建什么,我都会看到此错误。更多imp - 看起来它甚至没有尝试实际编译我的代码,并且由于某种原因只是在出现上述错误之前停止。
我尝试进行干净的构建。甚至手动清理所有旧生成的构建文件。还是没有用。 我什至尝试重新启动我的环境本身。重新启动 Clearcase。还是没有用。
我看到有一种方法可以使用调试信息进行构建。这也是 make -d
然而,这也没有提供任何有用的信息。与上面的行相同。我希望它能提供一些调试日志或一些错误代码,我可以用它们来解决问题。
我看到有一个选项:make -n
。结果很干净。但从名称来看,它似乎甚至没有尝试运行构建本身。
请建议可能是什么问题。
谢谢 - 唵
We are using OPUS Make in our build infrastructure. (Basically traditional make with some wrappers around I guess)
Our codebase is mostly Java and I have been making changes and building for many months now. No issues.
Suddenly, a couple of days back, when I tried to build,i started seeing this error:
OPUS MAKE: Unknown status. Stop.
I see this error no matter what I try to build. More imp - it looks like it is not even trying to actually compile my code and for some reason just stops before with the above error.
I tried doing a clean build. Even manually cleaned up all old generated build files. Still did not work.
I even tried restarting my environment itself. Restarted Clearcase. Still no use.
I see there is a way to build with debug information. Did that also make -d
However, that did not give any useful info either. Just the same line as above. I was hoping that it would give some debug logs or some error code that I could use to solve the problem.
I see there is an option: make -n
. That comes out clean. But from the name, it looks like it does not even attempt to run the build itself.
Please suggest what the issue could be.
thx - Om
如果你对这篇内容有疑问,欢迎到本站社区发帖提问 参与讨论,获取更多帮助,或者扫码二维码加入 Web 技术交流群。

绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱,如果其他用户或者作者回复了您的评论,将不能在第一时间通知您!
发布评论
评论(1)
“未知状态”意味着目标中的 shell 命令返回了 make 无法理解的状态。使用
-d
运行以查看哪个命令失败。并调试该 shell 命令。"Unknown status" means that a shell command in a target returned a status that make did not understand. Run with
-d
to see which command is failing. And debug that shell command.