HEAD amd64 seems unhappy

2018-02-03 Thread Josh Paetzel 
--- all_subdir_lib/libngatm ---
/usr/src/sys/contrib/ngatm/netnatm/api/cc_port.c:71:28: error: result of 
comparison 'u_int' (aka 'unsigned int') > 4294967295 is always fal
se [-Werror,-Wtautological-type-limit-compare]
if (portno == 0 || portno > 0x)
   ~~ ^ ~~
1 error generated.
*** [cc_port.o] Error code 1

This code hasn't changed in ages so I can only assume it's clang or such.

-- 

Thanks,

Josh Paetzel
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: CURRENT, CLANG 6: apache24, uid 80: exited on signal 11

2018-02-03 Thread Dimitry Andric 
On 3 Feb 2018, at 11:43, O. Hartmann  wrote:
> 
> Am Tue, 30 Jan 2018 00:09:07 +0100
> Dimitry Andric  schrieb:
>> On 30 Jan 2018, at 00:01, Dimitry Andric  wrote:
>>> On 29 Jan 2018, at 19:39, O. Hartmann  wrote:
 
 Last weekend I updated a CURRENT server to recent CURRENT, > r328400 and 
 performed
 updates of the ports tree. Since Sunday, I receive segmenatation faults 
 (SIG 11) when
 accessing the server, especially with setup of nextcloud, refdb, 
 phpldapadmin and any
 other access with LDAP backend (all https).
...
> Starting program: /usr/local/sbin/httpd -X
> [Sat Feb 03 11:41:27.704031 2018] [core:warn] [pid 59320:tid 3437628] 
> (2)No such file
> or directory: AH00075: Failed to enable the 'httpready' Accept Filter [Sat 
> Feb 03
> 11:41:27.704359 2018] [core:warn] [pid 59320:tid 3437628] (2)No such file 
> or
> directory: AH00075: Failed to enable the 'dataready' Accept Filter [New LWP 
> 101096 of
> process 59320] [New LWP 101105 of process 59320] [New LWP 101109 of process 
> 59320]
> [New LWP 101103 of process 59320]
> [New LWP 101102 of process 59320]
> [New LWP 101110 of process 59320]
> [New LWP 101107 of process 59320]
> [New LWP 101098 of process 59320]
> [New LWP 101099 of process 59320]
> [New LWP 101108 of process 59320]
> [New LWP 101112 of process 59320]
> [New LWP 101101 of process 59320]
> [New LWP 101104 of process 59320]
> [New LWP 101097 of process 59320]
> [New LWP 101106 of process 59320]
> [New LWP 10 of process 59320]
> [New LWP 101100 of process 59320]
> [LWP 101096 of process 59320 exited]
> 
> Thread 11 received signal SIGSEGV, Segmentation fault.
> [Switching to LWP 101108 of process 59320]
> 0x000802300382 in ?? () from /usr/local/lib/php/20131226-zts/opcache.so

Run the "backtrace" command there, please.  If it doesn't give any
function names, try setting WITH_DEBUG=1 in the environment, then
rebuilding the mod_php56 port (and optionally also the php56 and
apache24 ports themselves), to add debug info.

-Dimitry



signature.asc
Description: Message signed with OpenPGP

Re: buildkernel with PORTS_MODULES fails: Variable OBJTOP is recursive

2018-02-03 Thread O. Hartmann 
Am Sat, 3 Feb 2018 11:10:53 +0300
Vladimir Zakharov  schrieb:

> Hello, Oliver!
> 
> On Fri, Feb 02, 2018, O. Hartmann wrote:
> > On Thu, 1 Feb 2018 12:10:30 +0300
> > Vladimir Zakharov  wrote:
> >   
> > > Hello!
> > > 
> > > For some time (about a week) building and installing kernel fails with
> > > the error "Variable OBJTOP is recursive." when going to build/install
> > > module from ports.
> > > 
> > > Last successful build was at r328426. Next build at r328527 failed and
> > > still broken at r328649.
> > > 
> > > Without PORTS_MODULES building and installing kernel succeeds. Another
> > > workaround: ignore error and build/install module directly from ports.
> > >   
> > 
> > I have had the very same issue!
> > 
> > You need to perform a "installworld" first (just comment out the 
> > PORTS_MODULES=
> > parts of /etc/src.conf or /etc/make.conf, buildworld and buildkernel (maybe 
> > not
> > a full buildworld, but I do not know the state of your source tree) and 
> > perform
> > a regular installation of the world.  It could be something easier by 
> > direkctly
> > install-only the mk-portions, but recently, some changes to world (LLVM) 
> > made
> > it worth anyway to buildworld.
> > 
> > As recommended by others earlier on this list according to this subject, 
> > this
> > procedure makes the problem go away.  
> 
> Thanks for your answer. Unfortunately, this didn't help.
> 

You are correct! I made a mistake and had the portions still commented out. I'm 
very
sorry.

This remains a bug!

-- 
O. Hartmann

Ich widerspreche der Nutzung oder Übermittlung meiner Daten für
Werbezwecke oder für die Markt- oder Meinungsforschung (§ 28 Abs. 4 BDSG).


pgpUOEYTcpLE6.pgp
Description: OpenPGP digital signature

Re: CURRENT, CLANG 6: apache24, uid 80: exited on signal 11

2018-02-03 Thread O. Hartmann 
Am Sat, 3 Feb 2018 11:43:25 +0100
"O. Hartmann"  schrieb:

> Am Tue, 30 Jan 2018 00:09:07 +0100
> Dimitry Andric  schrieb:
> 
> > On 30 Jan 2018, at 00:01, Dimitry Andric  wrote:  
> > > 
> > > On 29 Jan 2018, at 19:39, O. Hartmann  wrote:
> > >> 
> > >> Last weekend I updated a CURRENT server to recent CURRENT, > r328400 and 
> > >> performed
> > >> updates of the ports tree. Since Sunday, I receive segmenatation faults 
> > >> (SIG 11)
> > >> when accessing the server, especially with setup of nextcloud, refdb, 
> > >> phpldapadmin
> > >> and any other access with LDAP backend (all https).
> > >> 
> > >> The message on console is:
> > >> 
> > >> pid 23108 (httpd), uid 80: exited on signal 11
> > >> pid 32283 (httpd), uid 80: exited on signal 11
> > >> pid 21286 (httpd), uid 80: exited on signal 11
> > >> pid 10292 (httpd), uid 80: exited on signal 11
> > >> 
> > >> I do not see anything else! Neither in the log (no matter what log level 
> > >> I switch
> > >> on) nor elsewhere.
> > >> 
> > >> Configuration hasn't changed.
> > >> 
> > >> What the ... is up with the system? How can I dig into the problem?
> > > 
> > > Try debugging httpd, e.g.:
> > > 
> > > sudo /usr/local/sbin/httpd -X
> > 
> > I meant "sudo gdb /usr/local/sbin/httpd -X", sorry.
> > 
> > -Dimitry
> >   
> 
> I see this:
> 
> 
> Starting program: /usr/local/sbin/httpd -X
> [Sat Feb 03 11:41:27.704031 2018] [core:warn] [pid 59320:tid 3437628] 
> (2)No such
> file or directory: AH00075: Failed to enable the 'httpready' Accept Filter 
> [Sat Feb 03
> 11:41:27.704359 2018] [core:warn] [pid 59320:tid 3437628] (2)No such file 
> or
> directory: AH00075: Failed to enable the 'dataready' Accept Filter [New LWP 
> 101096 of
> process 59320] [New LWP 101105 of process 59320] [New LWP 101109 of process 
> 59320]
> [New LWP 101103 of process 59320]
> [New LWP 101102 of process 59320]
> [New LWP 101110 of process 59320]
> [New LWP 101107 of process 59320]
> [New LWP 101098 of process 59320]
> [New LWP 101099 of process 59320]
> [New LWP 101108 of process 59320]
> [New LWP 101112 of process 59320]
> [New LWP 101101 of process 59320]
> [New LWP 101104 of process 59320]
> [New LWP 101097 of process 59320]
> [New LWP 101106 of process 59320]
> [New LWP 10 of process 59320]
> [New LWP 101100 of process 59320]
> [LWP 101096 of process 59320 exited]
> 
> Thread 11 received signal SIGSEGV, Segmentation fault.
> [Switching to LWP 101108 of process 59320]
> 0x000802300382 in ?? () from /usr/local/lib/php/20131226-zts/opcache.so
> 
> 
I also filed a bug report:

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=225499

-- 
O. Hartmann

Ich widerspreche der Nutzung oder Übermittlung meiner Daten für
Werbezwecke oder für die Markt- oder Meinungsforschung (§ 28 Abs. 4 BDSG).


pgpOPdBRdj9lt.pgp
Description: OpenPGP digital signature

Re: CURRENT, CLANG 6: apache24, uid 80: exited on signal 11

2018-02-03 Thread O. Hartmann 
Am Tue, 30 Jan 2018 00:09:07 +0100
Dimitry Andric  schrieb:

> On 30 Jan 2018, at 00:01, Dimitry Andric  wrote:
> > 
> > On 29 Jan 2018, at 19:39, O. Hartmann  wrote:  
> >> 
> >> Last weekend I updated a CURRENT server to recent CURRENT, > r328400 and 
> >> performed
> >> updates of the ports tree. Since Sunday, I receive segmenatation faults 
> >> (SIG 11) when
> >> accessing the server, especially with setup of nextcloud, refdb, 
> >> phpldapadmin and any
> >> other access with LDAP backend (all https).
> >> 
> >> The message on console is:
> >> 
> >> pid 23108 (httpd), uid 80: exited on signal 11
> >> pid 32283 (httpd), uid 80: exited on signal 11
> >> pid 21286 (httpd), uid 80: exited on signal 11
> >> pid 10292 (httpd), uid 80: exited on signal 11
> >> 
> >> I do not see anything else! Neither in the log (no matter what log level I 
> >> switch
> >> on) nor elsewhere.
> >> 
> >> Configuration hasn't changed.
> >> 
> >> What the ... is up with the system? How can I dig into the problem?  
> > 
> > Try debugging httpd, e.g.:
> > 
> > sudo /usr/local/sbin/httpd -X  
> 
> I meant "sudo gdb /usr/local/sbin/httpd -X", sorry.
> 
> -Dimitry
> 

I see this:


Starting program: /usr/local/sbin/httpd -X
[Sat Feb 03 11:41:27.704031 2018] [core:warn] [pid 59320:tid 3437628] (2)No 
such file
or directory: AH00075: Failed to enable the 'httpready' Accept Filter [Sat Feb 
03
11:41:27.704359 2018] [core:warn] [pid 59320:tid 3437628] (2)No such file or
directory: AH00075: Failed to enable the 'dataready' Accept Filter [New LWP 
101096 of
process 59320] [New LWP 101105 of process 59320] [New LWP 101109 of process 
59320]
[New LWP 101103 of process 59320]
[New LWP 101102 of process 59320]
[New LWP 101110 of process 59320]
[New LWP 101107 of process 59320]
[New LWP 101098 of process 59320]
[New LWP 101099 of process 59320]
[New LWP 101108 of process 59320]
[New LWP 101112 of process 59320]
[New LWP 101101 of process 59320]
[New LWP 101104 of process 59320]
[New LWP 101097 of process 59320]
[New LWP 101106 of process 59320]
[New LWP 10 of process 59320]
[New LWP 101100 of process 59320]
[LWP 101096 of process 59320 exited]

Thread 11 received signal SIGSEGV, Segmentation fault.
[Switching to LWP 101108 of process 59320]
0x000802300382 in ?? () from /usr/local/lib/php/20131226-zts/opcache.so


-- 
O. Hartmann

Ich widerspreche der Nutzung oder Übermittlung meiner Daten für
Werbezwecke oder für die Markt- oder Meinungsforschung (§ 28 Abs. 4 BDSG).


pgp6VqYXNDlzN.pgp
Description: OpenPGP digital signature

Re: buildkernel with PORTS_MODULES fails: Variable OBJTOP is recursive

2018-02-03 Thread Vladimir Zakharov 
Hello, Oliver!

On Fri, Feb 02, 2018, O. Hartmann wrote:
> On Thu, 1 Feb 2018 12:10:30 +0300
> Vladimir Zakharov  wrote:
> 
> > Hello!
> > 
> > For some time (about a week) building and installing kernel fails with
> > the error "Variable OBJTOP is recursive." when going to build/install
> > module from ports.
> > 
> > Last successful build was at r328426. Next build at r328527 failed and
> > still broken at r328649.
> > 
> > Without PORTS_MODULES building and installing kernel succeeds. Another
> > workaround: ignore error and build/install module directly from ports.
> > 
> 
> I have had the very same issue!
> 
> You need to perform a "installworld" first (just comment out the 
> PORTS_MODULES=
> parts of /etc/src.conf or /etc/make.conf, buildworld and buildkernel (maybe 
> not
> a full buildworld, but I do not know the state of your source tree) and 
> perform
> a regular installation of the world.  It could be something easier by 
> direkctly
> install-only the mk-portions, but recently, some changes to world (LLVM) made
> it worth anyway to buildworld.
> 
> As recommended by others earlier on this list according to this subject, this
> procedure makes the problem go away.

Thanks for your answer. Unfortunately, this didn't help.

-- 
Regards, | "In theory there is no difference between theory
  Vladimir Zakharov  | and practice. In practice there is."- Yogi Berra
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"