-
Notifications
You must be signed in to change notification settings - Fork 1.9k
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
Compile patch for solaris #3456
Comments
At least some of this has already been included - would you be able to try against the current Git master? There is some work being done on Solaris-derived platforms in #3340. |
I am trying to compile from git master but i get an error in configure
Can anyone help? |
That's usually a permissions problem, from what I can see from Google. |
In order for configure to work i had to create a folder fish and put the src folder inside it.
|
@panosdim, That tells me you didn't install the source package correctly. Doing a simple |
It looks like he's working with a git checkout. |
I can reproduce the Probably a |
What if you |
Nope. Annoyingly |
Even with a fresh git clone i had the same problem with configure
|
The configure script should set the source dir to "." (that is, the cwd). There is either something wrong with the configure script created by autoconf or there is something weird with the permission bits of your fish-shell directory (or perhaps the ACLs, etc.). I'll be very surprised if this has anything to do with fish. Open the configure script in your editor. Find this block of code:
Insert
Your ac_pwd value will obviously be different. |
Here is the output
|
At this point everything looks fine:
Here is where things go wrong:
That's from this line in the configure script:
On my systems (macOS, various Linux, Cygwin, BSD) the Some googling suggests this was the behavior of old versions of autoconf; e.g., 2.13. On my systems it is much newer; e.g., 2.69. What does |
I have a new autoconf
Maybe it is some strange behaviour of autoconf in solaris. Nevermind with |
We'd love to modify fish so that hacks like |
No problem i can test any modification in Solaris environment, just tell me when and what you need to test. |
I have Solaris 11, with autoconf 2.68, and I don't get the same problem with requiring |
Could you try the patch in #3608? That gives me a clean, working build on Solaris 11. |
Still not working on
|
Right, it looks like those functions aren't available on Solaris 10. Can you try building from Git master? I am not sure that the GCC available on Solaris 10 is new enough to support C++11, so we might be SOL on that platform anyway. |
I build from master but same error. I have installed a newer version of GCC on Solaris 10. |
@panosdim: gcc 4.9.3 does support C++11 so that shouldn't be an issue for supporting Solaris 10. You only have three actual errors. It can't find |
Alternatively, a copy of your |
These functions are missing from solaris 10 (even the std::xxx functions) as you can see from the |
Yes. In fact we already have fallback implementations. Look for |
I finally managed to compile in Solaris 10 using the attached patch. |
Looks good to me. Tested on macOS, Ubuntu, and Cygwin on Windows 10. If you run |
I think this needs checking for 10.6 as well. |
@krader1961 It will be better if you can just merge the patch. |
The switch to require C++11 means we can no longer build fish on OS X 10.6 irrespective of this change. I confirmed this sad fact by starting up my VirtualBox OS X 10.6 instance, syncing the source, and running
I can't readily confirm but believe we are now limited to supporting OS X 10.8 or newer.
Okay, I will do so in a few minutes. |
#3138 has the SnowLeopard plans. The upshot is the official packages can probably be made to work via a MacPorts install of libc++; if not, a MacPorts package can certainly be made to work. So SnowLeopard users won't be left out in the, err, cold. |
I am trying to compile fish-2.3.1 in solaris
and the following patch is need in order to successful compile. Can this patch included in the source code for next release?
The text was updated successfully, but these errors were encountered: