Support FreeBSD #1073
Comments
Added to Accepted Feature Requests. |
I actually submitted some if not most of those to the old google code repo, some I could get around others not so much, I'm also not a c/c++ expert but what I can do is start over fresh from the git repo and maybe create a GHI as problems appear? or do you simply prefer to track it all here? |
@mike-pt We moved from google code to github because google code is going away, and separately I wanted to collect all the issues for FreeBSD support in one place. Now that we're on github, though, we can accept pull requests. So if you'd like to work on this, maybe figure out a code change and create a pull request? |
For example, I think #1009 would make sense as a pull request on its own. |
Yeah I know about google code, so only a matter of time, the exporter to GH is very handy though :) Ok then, I'll give a new look into the GHI and see what I can fix myself and send PR, I'm sure I'll bump into something it won't be easy for me to fix but lets leave that for later :) One thing I do remember is "gen/arch/" dirs are not created for freebsd, In my local version I jut copied over the linux one's where needed (I'll create a GHI about that later today, have to go now) |
Beyond compilation patches, the strategic barriers to FreeBSD functionality are mostly around our reliance on posix shared memory, for 3 reasons:
|
More specifically, the issue is that we use pthread_mutexattr_setpshared. memcached may be a good replacement for #1. On Mon, Oct 26, 2015 at 10:24 AM, Joshua Marantz notifications@github.com
|
Nice to see this is getting some attention again :) Does this mean you guys will be spending some time on it soon? I'll be happy to test, other then trying to fix some compilation issue like I did before (and I had some help there too) I'm afraid I can't do much more... But I would really love to see ngx_pagespeed support on FreeBSD. |
Sorry to get your hopes up, but this isn't something we're currently planning on working on. We're just documenting our increasing reliance on posix shared memory in case someone else is thinking of working on this. |
Well still better then nothing ;) tks |
You could implement interprocess mutexes using umtx. (Golang is doing this). Background: |
Sorry to annoy you, but are there any estimates on FreeBSD support? Thanks in advance! |
No one is currently working on this, or has told me they plan to work on it, so unless someone wants to pick this up and make this happen we're not going to see this anytime soon. Sorry! |
Right now, compiling of mod_pagespeed failed. In file included from third_party/chromium/src/base/third_party/dmg_fp/dtoa_wrapper.cc:46: gcc 4.2.1. attempt to build with gcc48 yielded lots of different errors. I guess I should try clang... |
Nope, clang fails with the same error... |
Probably just change that to [48]? gcc-4.2.1 isn't supported for recent versions, either way. |
@mmokhi contributed a FreeBSD port of mod_pagespeed: https://svnweb.freebsd.org/changeset/ports/452011
Thanks @mmokhi! |
11.1-RELEASE-p3 |
I noticed it recent days that it was marked by another committer as "broken" because it doesnt work with openssl of base because of nothaving pkgconf file in expected location (there are two openssl, one in ports and installable other is existing as default in base). |
at least it compiles for me flawless on latest 11.1-STABLE, further testing will follow i removed the broken marking inside the makefile, and changed the apache version to 24, and added DEFAULT_VERSIONS+=ssl=libressl to /etc/make.conf looks good so far further testing will follow |
[==========] 172 tests from 19 test cases ran. (12656 ms total) pagespeed automatic test looks a bit different [----------] Global test environment tear-down 52 FAILED TESTS |
@jserviceorg yeah it's supposed to work with libressl and openssl from ports (as opposite of base). |
Still no plans for ngx_pagespeed support FreeBSD? |
@mmokhi |
On FreeBSD there is a Nginx port in the port-tree which is very straightforward to build (
There are two problems with this (that I'm trying to solve 😃 😅 )
I guess the PSOL being copied is the shared-object being produced while building apache-pagespeed... It just depends on if my guess is right 😅 |
Hi! I have changed config to use mod_pagespeed.so
|
I seems mod_pagespeed on freebsd is no longer broken thanks to you @mmokhi? Do you have step on how to build nginx+pagespeed on freebsd? Its been a while since I tired this :D |
I didn't decide anything :D but the reason I said that is cause the port is in fact no longer marked broken https://svnweb.freebsd.org/ports?view=revision&revision=490804 Since that was one of the main problems I wonder if it should now be possible to build ngx_pagespeed, but Im not sure about what steps to take to do it. |
@mike-pt It shouldn't be super complicated but needs time. If you wanna start it I will be very happy if I can help you on any part. |
Ah yeah back when the code wasn't even on github I played with that and even submitted a few patches uptream, but my C knowledge wasn't good enough to to more then check a few ifdefs and adapt for freebsd, the fact that this is now all on github also makes things easier so maybe I'll take a look at that.... |
Good then, |
Apparently the file "mod_pagespeed_ap24.so" is missing from the install. I tried the pkg as well as the ports build. So currently this is broken. I'm on freebsd-version: 12.0-RELEASE-p5 and Apache/2.4.39 (FreeBSD) OpenSSL/1.1.1a-freebsd configured with event MPM.
|
At one point mod_pagespeed supported FreeBSD, but it hasn't worked since ~1.2. It also has never worked with ngx_pagespeed, because ngx_pagespeed is more recent than that, but the additional effort of getting it working there should be small.
We've had various bugs opened for this over time. Some of them have information about working around build failures, but we need to track this in one place. Closing them all as duplicates, and linking them here:
The text was updated successfully, but these errors were encountered: