Date: Fri, 31 Jan 2025 01:36:56 +0000 From: bugzilla-noreply@freebsd.org To: bugs@FreeBSD.org Subject: [Bug 270516] buildworld missing build dependency on libcrypt? Message-ID: <bug-270516-227-FuPPUVOSBO@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-270516-227@https.bugs.freebsd.org/bugzilla/> References: <bug-270516-227@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=3D270516 --- Comment #5 from Tim McIntosh <tkmcintosh@me.com> --- (In reply to Jessica Clarke from comment #4) > Where does libopenbsd depend on lib crypt?=20 I'm not claiming that it does--that's why I included a question mark in the title and simply described the change that allowed the build to proceed. I didn't mean to imply that it was the right thing to do--only that there was some kind of problem and this change at least masked it and allowed the bui= ld to proceed/succeed. I apologize for not including the actual build logs here. At the time, I ma= de a modification based on my best interpretation of the error messages and moved on. I later followed up and reported this issue. > libroken does, and the line that tries to set up that dependency is wrong= so doesn't work, but I can't see why libopenbsd needs it. Are you sure it = wasn't libroken failing? Your explanation seems reasonable to me. If this build was using parallel m= ake, I can imagine that I might have seen a mix of errors from libroken and para= llel log messages from the libopenbsd build, which could have confused me about = the source of the error. My presumed-incorrect change might have simply allowed libcrypt to be built, ultimately allowing buildworld to succeed. --=20 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-270516-227-FuPPUVOSBO>