From owner-freebsd-gecko@freebsd.org Wed Dec 19 15:53:58 2018 Return-Path: Delivered-To: freebsd-gecko@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 7F9BD133A638 for ; Wed, 19 Dec 2018 15:53:58 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id 0E7C486E63 for ; Wed, 19 Dec 2018 15:53:58 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: by mailman.ysv.freebsd.org (Postfix) id C6110133A637; Wed, 19 Dec 2018 15:53:57 +0000 (UTC) Delivered-To: gecko@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id A2144133A636 for ; Wed, 19 Dec 2018 15:53:57 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mxrelay.ysv.freebsd.org (mxrelay.ysv.freebsd.org [IPv6:2001:1900:2254:206a::19:3]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) server-signature RSA-PSS (4096 bits) client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "mxrelay.ysv.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 3856086E62 for ; Wed, 19 Dec 2018 15:53:57 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mxrelay.ysv.freebsd.org (Postfix) with ESMTPS id 7AC201B338 for ; Wed, 19 Dec 2018 15:53:56 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id wBJFru6R070628 for ; Wed, 19 Dec 2018 15:53:56 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id wBJFru8l070627 for gecko@FreeBSD.org; Wed, 19 Dec 2018 15:53:56 GMT (envelope-from bugzilla-noreply@freebsd.org) X-Authentication-Warning: kenobi.freebsd.org: www set sender to bugzilla-noreply@freebsd.org using -f From: bugzilla-noreply@freebsd.org To: gecko@FreeBSD.org Subject: [Bug 234080] devel/rust-cbindgen 0.6.7_1 segfaults during configure with *** Signal 11 on FreeBSD 12.0-RELEASE Date: Wed, 19 Dec 2018 15:53:56 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Ports & Packages X-Bugzilla-Component: Individual Port(s) X-Bugzilla-Version: Latest X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: kreinholz@gmail.com X-Bugzilla-Status: Closed X-Bugzilla-Resolution: Not A Bug X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: gecko@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-gecko@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Gecko Rendering Engine issues List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 19 Dec 2018 15:53:58 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D234080 --- Comment #14 from Kevin Reinholz --- (In reply to Jan Beich from comment #13) > In short, if you need handholding use poudriere. A lot (if not majority) = of=20 > issues reported by portmaster users are pilot errors. Well I think this is a little harsh, but I'll take your recommendation to u= se poudriere under advisement, and I do greatly appreciate your help troubleshooting which was, at the time, a non-obvious error from my perspective. If by "handholding" you mean that I (and presumably a lot of other portmast= er users who report issues) should join all of the freebsd- mailing lists and become developers clued in to all of the latest issues in order to use portmaster, then perhaps you're right. I use the Ports collection and portmaster IAW the documentation provided by= the FreeBSD Handbook: https://www.freebsd.org/doc/handbook/ports-using.html I check /usr/ports/UPDATING regularly before updating third-party installed software to check for advisories, and follow the advice written there. When I have difficulty updating an application via portmaster, I check https://www.freshports.org/ and look for any linked bug reports pertaining = to that application that might explain my issue. More often than not (e.g. unl= ess performing a system update to a new minor or major version of FreeBSD) I si= mply wait until portsnap fetches a new distinfo and Makefile for the troublesome application, and try again with portmaster. 90% of the time this resolves whatever update issue I was having. When I perform either a minor (e.g. FreeBSD 11.1-RELEASE to FreeBSD 11.2-RELEASE) or major (e.g. FreeBSD 11.2-RELEASE to FreeBSD 12.0-RELEASE) system update, I do so using the freebsd-update utility and the documentati= on provided in the FreeBSD Handbook: https://www.freebsd.org/doc/handbook/updating-upgrading-freebsdupdate.html I also read the release notes for the version of FreeBSD I'm updating to (e= .g. https://www.freebsd.org/releases/12.0R/relnotes.html) prior to updating, in= the hope of catching any issues or gotchas in the process. If all of this is unreasonable user behavior, I apologize, but I do not bel= ieve what I am doing is unreasonable as an average user. If I were a FreeBSD dev, probably, but then, I am not part of the dev team, I'm just a user and Free= BSD enthusiast. I follow the documentation in the FreeBSD Handbook, read /usr/ports/UPDATIN= G, and read the release notes provided by the Release Engineering team about a= new RELEASE before attempting to update. That to me seems like pretty reasonable user behavior. This sort of phenomenon is why we have form validation on mo= st web pages that require user input, through either html5 and/or JavaScript--because user behavior cannot always be predicted and sometimes = it is not obvious to the user what the developer/administrator expects of him/= her. If portmaster is not for the average user, who should instead be using poudriere, I wish the FreeBSD Handbook would just come out and say so. The = same goes for the freebsd-update utility. I quite happily used FreeBSD back in 2004~2008 and never had issues like these. Back then, system updates requir= ed rebuilding everything from source, 'make kernel', 'make world', etc. If tha= t's the better way to go, I'll happily go back to that. Incidentally, reinstall= ing or rebuilding third party installed software was not required at that time-= -it "just worked" under ABI compatibility, and subsequently got updated via portupgrade in the due course of time. Much more convenient than rebuilding 500~1,000 third party applications with each major FreeBSD version update u= nder the current system. After using OpenSolaris and then Solaris 11 from 2009~2015, when I returned= to FreeBSD for its opensource implementation of ZFS, I read the documentation = on the FreeBSD Handbook to get up to speed with the changes since my previous = time as a FreeBSD user. I discovered that portmaster was seemingly preferred to portupgrade, and began using it. I discovered that freebsd-update was seemi= ngly preferred to the old way of making world, so I began using it. In short, I tried to be a responsible user, follow the official documentation provided,= and only file bug reports when following the official documentation did not res= olve my problem or something non-obvious was going wrong on my system. I think FreeBSD is an absolutely wonderful operating system, and appreciate= its organization and layout in a way that I could never really get enthusiastic about various Linux distros. But I don't think it's fair to attack or dismi= ss "portmaster users" as though we're some kind of plague on FreeBSD, especial= ly when portmaster is the first option listed prominently in the FreeBSD Handb= ook for keeping Ports up to date. I will look at migrating to poudriere for third party software management, = as apparently portmaster is prone to "pilot errors" due to either the lack of timely warnings and official documentation, or innate foolishness on the pa= rt of portmaster users such as myself. Incidentally, I think it's a nice utili= ty and I've found I prefer it to portupgrade since coming back to FreeBSD. I'm sorry for wasting your time as an error-prone portmaster user. --=20 You are receiving this mail because: You are the assignee for the bug.=