-
Notifications
You must be signed in to change notification settings - Fork 32
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
Failure to compile 0.4.2 on Arch w/ gcc or clang #22
Comments
These compilation errors for gcc 6 and clang 3.8 have been fixed in version 0.4.3. |
Alas, the above errors are gone but with each compiler we have different errors now; I am snipping out only the top portions of them, as each one (each compiler) produces a huge list of errors starting with this part so I'm sure it's all related. NOTE: it looks like Arch updated to clang 3.9.0 now so that may be part of the clang issues, but it looks like gcc has not updated:
Here's the gcc output:
Here's the clang output:
Nothing else has changed in the build method used, same as before. Thx! By the way, I personally don't care if we use gcc or clang so getting just one to work would be OK. :-) |
PS: I would be happy to build you a basic Arch VirtualBox VM and upload it somewhere if you'd like a development instance to sort this out. |
Yes Arch VirtualBox VM where you have these errors would be helpful. |
Apologies for the delay - I used one of my scripts to create a VM (it has a basic MATE desktop) and recreated the nfstrace compile errors - everything is ready for you, just import this OVA into your VirtualBox - it's about 2.5G because I had all the GUI stuff added automatically (sorry - it's all scripted for me): The password for both root and 'archuser' is 'archtest' - the nfstrace setup is located in /home/archuser/nfstrace. Inside that directory is a file PKGBUILD, the standard arch packaging script (it's my in-progress work). If you look in this file at the bottom, you will see I have the gcc and clang compile lines commented out easily for you to test both. To trigger it to build, just change to the nfstrace directory and type "makepkg". The build method Arch uses stays all within that directory, and cleans up itself (so you can build as gcc, edit PKGBUILD to uncomment clang, and just type "makepkg" again) each run. This is the build file I will eventually upload to make a real package for everyone else once we sort out these issues. Please let me know once you've downloaded so I can delete the OVA from my side, thanks! |
I have downloaded the image so you can delete it. |
Thanks! I've removed it. |
I've updated cmake/FindJSON.cmake 2574031 Could you please update from master and let me know how it goes ? |
It all works! I tested both gcc and clang, no errors in either system now. Might we tag a 0.4.3.1 or a 0.4.4 with this commit so I don't have to use .patch files in my packaging? :-) PS: I am agnostic to which compiler is used, and read a lot of back-and-forth as to if clang or gcc is better, there's no clear winner. As project maintainer, which compiler would you recommend we use as the default to compile nfstrace, do you have a preference or experience to share? Thanks! |
I'd say gcc is the default compiler. |
Created 0.4.3.1 tag. |
Thank you - I went with gcc as it's usually installed by most folks (AUR is a compile-on-the-fly system, unlike precompiled official packages) and clang is a hefty download if you don't already have it installed. Everything is 100% now, package is live: Much appreciated for your help! |
I'm creating a package for Arch, here are the current versions of requirements we have:
When compiling with gcc I error out with:
When compiling with clang I error out with:
Both of these appear to be errors in what the compilers are looking for or expect, any advice on where to go from here? Nothing special about the compile, following the README instructions.
The text was updated successfully, but these errors were encountered: