Date: Wed, 19 Dec 2018 15:53:56 +0000 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 Message-ID: <bug-234080-21738-93oDBKXV3j@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-234080-21738@https.bugs.freebsd.org/bugzilla/> References: <bug-234080-21738@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=234080 --- Comment #14 from Kevin Reinholz <kreinholz@gmail.com> --- (In reply to Jan Beich from comment #13) > In short, if you need handholding use poudriere. A lot (if not majority) of > issues reported by portmaster users are pilot errors. Well I think this is a little harsh, but I'll take your recommendation to use 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 portmaster 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. unless performing a system update to a new minor or major version of FreeBSD) I simply 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 documentation 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 believe 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 FreeBSD enthusiast. I follow the documentation in the FreeBSD Handbook, read /usr/ports/UPDATING, 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 most 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 required rebuilding everything from source, 'make kernel', 'make world', etc. If that's the better way to go, I'll happily go back to that. Incidentally, reinstalling 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 under 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 seemingly 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 resolve 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 dismiss "portmaster users" as though we're some kind of plague on FreeBSD, especially when portmaster is the first option listed prominently in the FreeBSD Handbook 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 part of portmaster users such as myself. Incidentally, I think it's a nice utility 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. -- You are receiving this mail because: You are the assignee for the bug.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-234080-21738-93oDBKXV3j>