Date: Wed, 15 Jan 2025 21:33:55 +0100 From: Rainer Duffner <rainer@ultra-secure.de> To: John Nielsen <lists@jnielsen.net> Cc: Current FreeBSD <freebsd-current@freebsd.org>, Dennis Clarke <dclarke@blastwave.org> Subject: Re: poudriere and the user ... is it mostly a lost idea? Message-ID: <477ED13E-453B-4F64-856C-D433812EDA5D@ultra-secure.de> In-Reply-To: <4187986C-3986-4813-91CE-3DA9F599BFC8@jnielsen.net> References: <befa59eb-b458-48c4-91f4-af326095557e@blastwave.org> <4187986C-3986-4813-91CE-3DA9F599BFC8@jnielsen.net>
index | next in thread | previous in thread | raw e-mail
[-- Attachment #1 --] > Am 15.01.2025 um 20:30 schrieb John Nielsen <lists@jnielsen.net>: > > > If you want to get a desktop up and running quickly then you can use the pre-built packages (which are signed and verified by default, clouds and unicorns notwithstanding). > > If you choose to build all of your software locally that is 100% a supported option but it does put more responsibility on you, the user. When you get a build failure you are welcome to report it to the maintainer (listed in every single port file) and/or the appropriate mailing list (which -current is not, btw). Include the commands you are running and other configuration details as well as the exact error output. > > Note, however, that the automated package build system already emails port maintainers on build failures and, choosing xfce as an example, I don’t see any such reports in the mailing list archives (https://lists.freebsd.org/archives/freebsd-xfce/). You can even view the results of the project’s package build system (which also uses poudriere) by following the instructions here: https://people.freebsd.org/~grahamperrin/pkg-status/ > > On a recent quarterly build I don’t see any failed or skipped ports related to the desktop environments you mentioned. (https://pkg-status.freebsd.org/beefy20/build.html?mastername=141amd64-quarterly&build=7b2027223baa) > > I’d advise you to do more troubleshooting on your local system and provide some better details if you decide to ask for help in an appropriate forum, such as the freebsd-questions mailing list or the online forums at https://forums.freebsd.org/ or the mailing list(s) listed as maintainers for the ports you are having problems building. > > Good luck, > > JN Recently, chromium got pulled in on my poudriere build as a dependency of some icinga sub-package. That pulled in llvm19, which took I think 18 or 22 hours on the meager HP Gen 8 that poudriere is running on. Then, after 24h, the build of chromium was erroring out. I think you need to have reasonably recent and powerful hardware to do a build of a „full“ desktop. My normal build is 20 hours for 2200 or so packages. Most time is spent on compiling llvm compilers…. [-- Attachment #2 --] <html><head><meta http-equiv="content-type" content="text/html; charset=utf-8"></head><body style="overflow-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;"><br><div><blockquote type="cite"><div>Am 15.01.2025 um 20:30 schrieb John Nielsen <lists@jnielsen.net>:</div><br class="Apple-interchange-newline"><div><meta http-equiv="content-type" content="text/html; charset=utf-8"><div style="overflow-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;"><br><div>If you want to get a desktop up and running quickly then you can use the pre-built packages (which are signed and verified by default, clouds and unicorns notwithstanding).</div><div><br></div><div>If you choose to build all of your software locally that is 100% a supported option but it does put more responsibility on you, the user. When you get a build failure you are welcome to report it to the maintainer (listed in every single port file) and/or the appropriate mailing list (which -current is not, btw). Include the commands you are running and other configuration details as well as the exact error output.</div><div><br></div><div>Note, however, that the automated package build system already emails port maintainers on build failures and, choosing xfce as an example, I don’t see any such reports in the mailing list archives (<a href="https://lists.freebsd.org/archives/freebsd-xfce/">https://lists.freebsd.org/archives/freebsd-xfce/</a>). You can even view the results of the project’s package build system (which also uses poudriere) by following the instructions here: <a href="https://people.freebsd.org/~grahamperrin/pkg-status/">https://people.freebsd.org/~grahamperrin/pkg-status/</a></div><div><br></div><div>On a recent quarterly build I don’t see any failed or skipped ports related to the desktop environments you mentioned. (<a href="https://pkg-status.freebsd.org/beefy20/build.html?mastername=141amd64-quarterly&build=7b2027223baa">https://pkg-status.freebsd.org/beefy20/build.html?mastername=141amd64-quarterly&build=7b2027223baa</a>)</div><div><br></div><div>I’d advise you to do more troubleshooting on your local system and provide some better details if you decide to ask for help in an appropriate forum, such as the freebsd-questions mailing list or the online forums at <a href="https://forums.freebsd.org/">https://forums.freebsd.org/</a> or the mailing list(s) listed as maintainers for the ports you are having problems building.</div><div><br></div><div>Good luck,</div><div><br></div><div>JN</div></div></div></blockquote></div><br><div><br></div><div>Recently, chromium got pulled in on my poudriere build as a dependency of some icinga sub-package.</div><div><br></div><div>That pulled in llvm19, which took I think 18 or 22 hours on the meager HP Gen 8 that poudriere is running on.</div><div><br></div><div>Then, after 24h, the build of chromium was erroring out.</div><div><br></div><div>I think you need to have reasonably recent and powerful hardware to do a build of a „full“ desktop.</div><div><br></div><div>My normal build is 20 hours for 2200 or so packages. Most time is spent on compiling llvm compilers….</div><div><br></div><div><br></div></body></html>home | help
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?477ED13E-453B-4F64-856C-D433812EDA5D>