From owner-freebsd-ppc@FreeBSD.ORG Fri Mar 27 15:32:40 2015 Return-Path: <owner-freebsd-ppc@FreeBSD.ORG> Delivered-To: freebsd-ppc@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 25773C2B; Fri, 27 Mar 2015 15:32:40 +0000 (UTC) Received: from relay.mailchannels.net (ar-005-i207.relay.mailchannels.net [162.253.144.89]) by mx1.freebsd.org (Postfix) with ESMTP id DB910633; Fri, 27 Mar 2015 15:32:37 +0000 (UTC) X-Sender-Id: duocircle|x-authuser|hippie Received: from smtp5.ore.mailhop.org (ip-10-204-4-183.us-west-2.compute.internal [10.204.4.183]) by relay.mailchannels.net (Postfix) with ESMTPA id 2E9CB10119A; Fri, 27 Mar 2015 15:32:30 +0000 (UTC) X-Sender-Id: duocircle|x-authuser|hippie Received: from smtp5.ore.mailhop.org (smtp5.ore.mailhop.org [10.21.145.197]) (using TLSv1 with cipher DHE-RSA-AES256-SHA) by 0.0.0.0:2500 (trex/5.4.8); Fri, 27 Mar 2015 15:32:30 +0000 X-MC-Relay: Neutral X-MailChannels-SenderId: duocircle|x-authuser|hippie X-MailChannels-Auth-Id: duocircle X-MC-Loop-Signature: 1427470350342:4015143094 X-MC-Ingress-Time: 1427470350342 Received: from c-73-34-117-227.hsd1.co.comcast.net ([73.34.117.227] helo=ilsoft.org) by smtp5.ore.mailhop.org with esmtpsa (TLSv1.2:DHE-RSA-AES256-GCM-SHA384:256) (Exim 4.82) (envelope-from <ian@freebsd.org>) id 1YbWFC-0000AY-TW; Fri, 27 Mar 2015 15:32:23 +0000 Received: from revolution.hippie.lan (revolution.hippie.lan [172.22.42.240]) by ilsoft.org (8.14.9/8.14.9) with ESMTP id t2RFWE84050067; Fri, 27 Mar 2015 09:32:14 -0600 (MDT) (envelope-from ian@freebsd.org) X-Mail-Handler: DuoCircle Outbound SMTP X-Originating-IP: 73.34.117.227 X-Report-Abuse-To: abuse@duocircle.com (see https://support.duocircle.com/support/solutions/articles/5000540958-duocircle-standard-smtp-abuse-information for abuse reporting information) X-MHO-User: U2FsdGVkX1/p1dBeDX9zDoL90mYtO9pt Message-ID: <1427470334.91374.4.camel@freebsd.org> Subject: Re: 11.0-CURRENT: SCTP_MAX_CWND, lib/libc/net/sctp_sys_calls.c -r279859 vs. updating to head snaphot -r280598 From: Ian Lepore <ian@freebsd.org> To: Michael Tuexen <tuexen@freebsd.org> Date: Fri, 27 Mar 2015 09:32:14 -0600 In-Reply-To: <D6D9BF0F-64B4-4368-98E5-61C151BFB0FA@freebsd.org> References: <24B7C687-9147-42F1-AE49-92F93DC85AA8@dsl-only.net> <D6D9BF0F-64B4-4368-98E5-61C151BFB0FA@freebsd.org> Content-Type: text/plain; charset="us-ascii" X-Mailer: Evolution 3.12.10 FreeBSD GNOME Team Port Mime-Version: 1.0 Content-Transfer-Encoding: 7bit X-AuthUser: hippie Cc: freebsd-current@freebsd.org, FreeBSD PowerPC ML <freebsd-ppc@freebsd.org>, Mark Millard <markmi@dsl-only.net> X-BeenThere: freebsd-ppc@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Porting FreeBSD to the PowerPC <freebsd-ppc.freebsd.org> List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-ppc>, <mailto:freebsd-ppc-request@freebsd.org?subject=unsubscribe> List-Archive: <http://lists.freebsd.org/pipermail/freebsd-ppc/> List-Post: <mailto:freebsd-ppc@freebsd.org> List-Help: <mailto:freebsd-ppc-request@freebsd.org?subject=help> List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-ppc>, <mailto:freebsd-ppc-request@freebsd.org?subject=subscribe> X-List-Received-Date: Fri, 27 Mar 2015 15:32:40 -0000 On Fri, 2015-03-27 at 10:17 -0500, Michael Tuexen wrote: > > On 26 Mar 2015, at 21:36, Mark Millard <markmi@dsl-only.net> wrote: > > > > Basic context: > > > > # freebsd-version -ku; uname -apKU > > 11.0-CURRENT > > 11.0-CURRENT > > FreeBSD FBSDG5C0 11.0-CURRENT FreeBSD 11.0-CURRENT #1 r279514M: Sat Mar 21 05:15:23 PDT 2015 root@FBSDG5C0:/usr/obj/usr/srcC/sys/GENERIC64vtsc-NODEBUG powerpc powerpc64 1100062 1100062 > > > > > > The problem: > > > > Summary of the details that are listed later. Both of the following exist: > > > > /usr/src/sys/netinet/sctp.h > > /usr/include/netinet/sctp.h > > > > The first can be newer than the 2nd during buildworld. > > > > The buildworld compile of /head/lib/libc/net/sctp_sys_calls.c from an updated /usr/src can/does end up using the second instead of the first, at least for the powerpc64-xtoolchain-gcc style of buildworld activity that I am trying. > > > > The recent addition of SCTP_MAX_CWND ends up with its definition missing because of this: during the build /usr/include/netinet/sctp.h ends up being the file included and the compile fails from the missing additional definition. > > > > Either the #include paths in /head/lib/libc/net/sctp_sys_calls.c or the command line arguments should force the /usr/src/sys/netinet/sctp.h vintage file to be found. The 3 netinet/ relevant includes are shown below... > > > >> ... > >> #include <netinet/in.h> > >> #include <arpa/inet.h> > >> #include <netinet/sctp_uio.h> > >> #include <netinet/sctp.h> > > > > More than sctp.h might have such issues since there are 3 netinet/ include paths in /head/lib/libc/net/sctp_sys_calls.c . > > > > I have not checked for other .c files with similar issues for <netinet/...> usage during buildworld. > I guess there is something wrong with the build system / Makefiles such that the entries in the search > path for include files are in the wrong order. I don't think this is related to the concrete patch > you are referring to. It only exposes the problem. As I see, you experience similar problems in > other situations to. > > Maybe someone knowing the build system has to look into it. And it seems to be somewhat platform specific, > since I have not observed this problem when testing the build on amd64 and arm. > > Best regards > Michael This and the other similar reports on current@ appear to be problems with the xtoolchain ports, not the base build system, and probably should have been reported to the port's maintainer, or on ports@. Or perhaps it's some sort of usage error, I don't know anything about the xtoolchain stuff. In any case, there doesn't seem to be anything wrong with the base build using the supported build mechanisms. -- Ian