Skip to content
This repository has been archived by the owner on Apr 21, 2023. It is now read-only.

Add Solaris as a supported platform #668

Open
GoogleCodeExporter opened this issue Apr 6, 2015 · 8 comments
Open

Add Solaris as a supported platform #668

GoogleCodeExporter opened this issue Apr 6, 2015 · 8 comments

Comments

@GoogleCodeExporter
Copy link

What steps will reproduce the problem?
1. Download all the library and dependencies
2. Make to build the mod pages speed
3.
Command Run:
make -k AR.host=`pwd`/build/wrappers/ar.sh AR.target=`pwd`/build/wrappers/ar.sh 
BUILDTYPE=Release 

Error:
make: Fatal error in reader: Makefile, line 11: Unexpected end of line seen

What is the expected output? What do you see instead?
It should build the module for Apache

What version of the product are you using (please check X-Mod-Pagespeed
header)?

On what operating system?
SunOS xxxxx 5.10 Generic_144488-12 sun4v sparc SUNW,SPARC-Enterprise-T5220
Which version of Apache?
2.2
Which MPM?

URL of broken page: n/a


Original issue reported on code.google.com by huar...@gmail.com on 8 Apr 2013 at 9:54

@GoogleCodeExporter
Copy link
Author

I'm afraid we don't currently support Solaris. The problem is with our build 
system, gyp, which requires separate subdirectories for config files for each 
architecture type.

A quick look and I see about a dozen places:

$ find | grep "arch/linux$"
./third_party/google-sparsehash/gen/arch/linux
./third_party/httpd24/gen/arch/linux
./third_party/gflags/gen/arch/linux
./third_party/aprutil/gen/arch/linux
./third_party/opencv/gen/arch/linux
./third_party/mod_spdy/src/third_party/apache/aprutil/gen/arch/linux
./third_party/mod_spdy/src/third_party/apache/httpd/gen/arch/linux
./third_party/mod_spdy/src/third_party/apache/apr/gen/arch/linux
./third_party/httpd/gen/arch/linux
./third_party/apr/gen/arch/linux
./third_party/icu/genfiles/arch/linux

Right now this is not a priority for us to work on, but if you wanted to try 
and get it working yourself you could try copying those linux folders to 
solaris folders (or whatever string Solaris uses to identify its architecture). 
If that doesn't work, you may need to actually get the correct configurations 
for each of those packages (I got them with ./configure && make). But there's a 
good chance other things will still not work because we haven't tested on 
Solaris at all and AFAIK nobody has successfully installed it on Solaris.

Sorry about that. And good luck if you dive into this.

Original comment by sligocki@google.com on 8 Apr 2013 at 10:13

  • Changed title: Cannot build on Solaris

@GoogleCodeExporter
Copy link
Author

Issue 660 has been merged into this issue.

Original comment by sligocki@google.com on 8 Apr 2013 at 10:13

@GoogleCodeExporter
Copy link
Author

Summary was: Cannot build on Solaris

Original comment by jmara...@google.com on 11 Apr 2013 at 12:56

  • Changed title: Add Solaris as a supported platform
  • Changed state: Accepted
  • Added labels: Type-Enhancement
  • Removed labels: Type-Defect

@GoogleCodeExporter
Copy link
Author

Hi,

I am planning to compile this module for Solaris x86 servers. Can anyone please 
let me know where I can download the source code and steps for compilation?

SunOS 5.10 Generic_148889-01 i86pc i386 i86pc

Regards,
Ramesh

Original comment by godinara...@gmail.com on 17 Feb 2014 at 2:04

@GoogleCodeExporter
Copy link
Author

https://developers.google.com/speed/pagespeed/module/build_from_source

Original comment by matterb...@google.com on 17 Feb 2014 at 2:43

@GoogleCodeExporter
Copy link
Author

I don't know if this helps, but solaris 11 has the following packages available 
that may ease the porting burden:
* /web/server/apache-22, containing /usr/apache2/2.2/include/* suitable for 
building modules against
* /library/apr-13, containing /usr/apr/1.3/include/* and lib/*
* /library/apr-util, containing /usr/apr-util/1.3/include/* and lib/*
I'm currently trying to get mod_spdy built on the basis of these pages. I'm not 
done yet, so was looking at mod_pagespeed as a sharding option in case I was 
not successful. The application I'm porting is reliant on being able to obtain 
a large (>6) number of connections between server and client.

Original comment by fuzzy...@gmail.com on 14 Apr 2014 at 4:07

@GoogleCodeExporter
Copy link
Author

Was there an update on this. I am unable to find if solaris is a supported 
platform now .

Original comment by vihang.s...@gmail.com on 24 Jul 2014 at 9:59

@GoogleCodeExporter
Copy link
Author

Solaris is not a supported platform.  mod_pagespeed's build process is 
inherited from Chromium, and I don't believe Chrome works on Solaris.

I think if I were going to try to port mod_pagespeed to Solaris I'd start the 
build process on Linux so that you get a Makefile.  Then I'd copy the 
build-tree to your Solaris box and fix all the stuff that needs to be fixed, 
which you'll encounter when you run make.

There are a few subsystems that have specific include-files provided for mac, 
windows, and Linux, and you'd have to come up with versions of those that would 
work for Solaris.  In most of those cases, you might be able to go to the 
distribution for those subsystems (e.g. gflags, google-sparse-hash-map) and 
build it natively on Solaris with ./configure, and pull the files from those).

I know what you are going to ask -- why don't we just use the standard 
./configure flow for Unix open-source software to begin with?  The main reason 
as I see it is that we have many dependencies that need to be built first, and 
using our current build process (gyp, gclient) allows us to manage those 
dependencies as part of our build flow, making it essentially a one step 
process.  But in particular, some of our dependencies use gyp/gclient already 
so it's a lot easier for use to use it too, to capture all their transitive 
dependencies.


One thing I would *not* do is wait for Solaris to become a supported platform 
due to an initiative from Google.  However, please feel free to use this Issue 
report as a collaboration tool for those interested in doing this port.

It's also possible for you to submit patches that we could put into the trunk 
to maintain the port over time, but we don't plan on testing against Solaris as 
part of our already-burdensome release process.

Original comment by jmara...@google.com on 24 Jul 2014 at 12:07

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

1 participant