-
Notifications
You must be signed in to change notification settings - Fork 4
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
Need build instructions #2
Comments
I just updated the readme with some build instructions. Let me know if that works for you. Thanks! |
@rejohnst Thanks, but it'll need a bit more than that.
|
Yep - I know what that problem is. I just updated the readme with how to deal with this. Give it a look and let me know how it goes. |
Given that this is SmartOS, there is no If I override that to use pkgsrc, then I get this error.
It took a bit of digging, and comparing with two systems, where one had different errors, that the minimum PI to build this on is 20181122, because that's the first one that includes USB_DEVICE in Switching to a newer PI, I now get this error:
|
Sorry you're hitting so many issues. Yeah, there is one way around the minimum SmartOS PI issue - and that is to specify the path to the proto area from a smartos-live repo that was built with the prerequisite changes. make CC=/opt/local/bin/gcc PROTO=/path/to/built-smartos-live-repo/proto all My SmartOS build zone has /opt/onbld, but I don't recall if it came with it or I installed it after the fact. If you have a built smartos-live repo, there should be a copy of the CTF tools in there and you can point to it by overriding the CTFTOOLS macro. For example, if you have a built smartos-live repo at /home/user/smartos-live, you would point to it's CTF tools as follows:
On OpenIndiana you would simply install the |
FWIW, I tweaked the makefile to seach for gcc in your PATH. So now you only need to manually override the CC macro if gcc is not in your path. |
No description provided.
The text was updated successfully, but these errors were encountered: