[ 
https://issues.apache.org/jira/browse/STORM-2629?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jungtaek Lim resolved STORM-2629.
---------------------------------
    Resolution: Fixed

Thanks [~Srdo], I merged into asf-site.

> Can't build site on Windows due to Nokogiri failing to install
> --------------------------------------------------------------
>
>                 Key: STORM-2629
>                 URL: https://issues.apache.org/jira/browse/STORM-2629
>             Project: Apache Storm
>          Issue Type: Bug
>          Components: asf-site
>            Reporter: Stig Rohde Døssing
>            Assignee: Stig Rohde Døssing
>            Priority: Minor
>              Labels: pull-request-available
>         Attachments: STORM-2629.patch
>
>
> I'm using Windows 10's bash support, and I'm having some trouble building the 
> site since Nokogiri won't install. 
> {code}
> Running 'configure' for libxml2 2.9.2... ERROR, review
> '/tmp/bundler20170714-31-159r6j1nokogiri-1.6.7.2/gems/nokogiri-1.6.7.2/ext/nokogiri/tmp/x86_64-pc-linux-gnu/ports/libxml2/2.9.2/configure.log'
> to see what happened. Last lines are:
> ========================================================================
> checking build system type... ./config.guess: line 4: $'\r': command not found
> ./config.guess: line 6: $'\r': command not found
> ./config.guess: line 33: $'\r': command not found
> {code}
> Upgrading Nokogiri fixes this issue, so I'd like to upgrade the gemfile to 
> the latest version of github-pages, i.e. run "bundler update". As far as I 
> can tell, we only need to make a small number of changes to get it working.
> * It seems like the meaning of the {{page}} variable in a layout has changed 
> in Jekyll. _layouts/about.html should use {{layout}} to refer to it's own 
> variables instead of {{page}} (which would belong to the concrete page being 
> rendered). The other layouts don't refer to their own front matter, so there 
> shouldn't be any issue there
> * Jekyll has made redcarpet an optional dependency, so the gemfile should 
> list that dependency explicitly



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Reply via email to