Bug 509978 – www-servers/nginx-1.4.7 in x32 ABIs - In file included from src/core/nginx.c:8: /usr/include/bits/sysctl.h:19:3: error: #error "sysctl system call is unsupported in x32 kernel"

• Status: RESOLVED FIXED
• Product: Gentoo Linux

[Description Thibaud CANALE 2014-05-10 15:17:29 UTC]

Hello,

When trying to emerge www-server/nginx-1.4.7, the compilation phase fails with this kind of message:

In file included from /usr/include/sys/sysctl.h:63:0,
                 from src/os/unix/ngx_linux_config.h:54,
                 from src/core/ngx_config.h:26,
                 from src/core/nginx.c:8:
/usr/include/bits/sysctl.h:19:3: error: #error "sysctl system call is unsupported in x32 kernel"

But I notice this is a "normal" behavior as explained on Debian's wiki about x32 ABI[1]

I tryed the hardmasked ebuild of version 1.5.13 and it works (I just notice this is not a legacy version, I understand why this version is now masked, then I work report any bug about this version) 

So, the ebuild for version 1.4.7 (and maybe for version 1.4.7-r1 too) should be masked in x32 profile with this explanation.

I notice version 1.6.0, the stable version in Nginx's release work [2], got released 2014-04-24, 16 days ago, maybe I should try to make an ebuild.
Reproductible: Always.

Step to reproduce:
Emerging nginx on x32 architecture.

Expected result:
Success compilation.

Thanks for support.

[1] https://wiki.debian.org/X32Port under "Use of sysctl(2)"
[2] http://nginx.org/

[Comment 1 Johan Bergström 2014-06-27 02:40:08 UTC]

Can you please confirm in later versions. I believe this is fixed upstream.

[Comment 2 Thibaud CANALE 2014-06-27 18:13:33 UTC]

Hello,

TL;DR: this bug is fixed in version >=1.5

(In reply to Johan Bergström from comment #1)
> Can you please confirm in later versions. I believe this is fixed upstream.

The compilation problem is fixed since the 1.5 branch. I didn't talk about it, because it is a dev branch (if I am not wrong).
But, there is another bug, this one does crash the nginx server, and it's still there in 1.7 branch (currently 1.7.2). I did wrong, when I wrote in the description “I tryed the hardmasked ebuild of version 1.5.13 and it works”, I was just talking about the compilation phase.

I didn't talk about this bug in versions >=1.5, because it's not related to this bug with the compilation, and the version 1.5.13 is hardmasked. I will fill another report to explain this.

Thanks for support.

[Comment 3 Johan Bergström 2014-07-10 23:45:16 UTC]

Thibauld: Thanks for the feedback.

As you might have seen, we've introduced nginx 1.7.x as our only supported version moving forward, based on upstream recommendation. Should you need older versions, we will maintain an overlay here: https://github.com/gentoo/nginx-overlay (layman -a nginx-overlay).

Can we close this bug and possibly open another for your compilation error?

[Comment 4 Johan Bergström 2014-07-10 23:45:46 UTC]

(In reply to Johan Bergström from comment #3)
> Thibauld: Thanks for the feedback.
> 
> As you might have seen, we've introduced nginx 1.7.x as our only supported
> version moving forward, based on upstream recommendation. Should you need
> older versions, we will maintain an overlay here:
> https://github.com/gentoo/nginx-overlay (layman -a nginx-overlay).
> 
> Can we close this bug and possibly open another for your compilation error?

(Sorry for the typo in your name, Thibaud)

[Comment 5 Thibaud CANALE 2014-07-13 14:04:50 UTC]

(In reply to Johan Bergström from comment #3)
> Can we close this bug and possibly open another for your compilation error?

You're right, the compilation bug is over (in version >=1.5), and I should have opened another report bug for the strange behaviour. My bad.

I am looking through the overlay, to see if nginx works.

[Comment 6 Johan Bergström 2014-07-15 02:17:19 UTC]

Closing this since it's fixed upstream.

[Comment 7 Thibaud CANALE 2014-07-15 09:27:07 UTC]

Sorry, there is a typography error in the title, but I don't know if we are allowed to correct it since this bug is closed ...

For the search engine, I think we should correct it, sorry if I am wrong or I am not allowed.