-
Notifications
You must be signed in to change notification settings - Fork 13.2k
configure fails on NetBSD #1180
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
Comments
Does this still happen with current LLVM CVS? |
I checked llvm-1.9 and llvm-cvs and yes: it's the same. (Ok: The version number |
Wow, didn't even know about this one. Mine. |
Some "draft" |
Anton: I've already committed that, with these patches: http://lists.cs.uiuc.edu/pipermail/llvm-commits/Week-of-Mon-20070115/043007.html Christopher, Could you please update your configure script an lib/System/Mutex.cpp. We've Thanks, Reid. |
Great! But I found another (tiny) build problem: First line in GenLibDeps.pl is Therefore GenLibDeps.pl should be called with |
Fixed. Please let me know if there's anything else preventing a clean build. |
Christoph, Can this get closed now? Is the configure working on NetBSD? Reid. |
Hi Reid, sorry, i'm quite busy at the moment. I did a quick check this morning Christoph |
llvm#1180) This removes some NYI in CIRGenModule::tryEmitBaseDestructorAsAlias and similar to llvm/clangir#1179, use `assert(false)` to tell devs to add test. It is slightly verbose due to the difference between LLVM and CIR's type system. LLVM's pointer are opaque types while CIR's pointer are typed. So we need to handle these pointers when transforming the generated cir.
Extended Description
Here is the output of configure.
% ./configure
checking build system type... i386-unknown-netbsdelf3.0
checking host system type... i386-unknown-netbsdelf3.0
checking target system type... i386-unknown-netbsdelf3.0
checking type of operating system we're on... Unknown
configure: error: Operating system is unknown, configure can't continue
I think llvm should support NetBSD.
The text was updated successfully, but these errors were encountered: