On 2023-08-11 03:33, William Kenworthy wrote:
Will "ebuild /path/to/whatever.ebuild compile" work for what you are doing ?
Also, it works on some simpler builds to cd to the top of the src tree and just
issue a make.
In this particular case I'd like to also merge the compiled wine to my system
Thank you, Yixun.
On 2023-08-11 02:23, Yixun Lan wrote:
understanding git bisect should be enough to keep you going..
Yes, I actually just ended up doing what git bisect does but manually for now.
2) Can I tell emerge not to clean the build directory between bisects so it
only recompiles the
?
3) In the wiki's test-zfs.sh script, the EGIT_OVERRIDE_COMMIT variables are
poorly documented. What would the name of those be for app-emulation/wine-vanilla?
Regards
Morgan Wesström
On 2023-04-21 00:36, Dale wrote:
/var/tmp/portage/x11-drivers/nvidia-drivers-470.182.03/temp/environment:
line 1291:
/var/tmp/portage/x11-drivers/nvidia-drivers-470.182.03/files/nvidia-drivers-470.141.03-clang15.patch:
No such file or directory
Any thoughts? Ideas?
I couldn't reproduce the
On 2023-03-21 21:04, Jack wrote:
I'd suggest looking at ebuilds created by g-cpan, which produces ebuilds for
any module in CPAN.
I was looking at this early on but didn't think I would need it but it turned
out that there was one more dependency I had missed. g-cpan worked very well,
break the next time Perl gets updated)?
Regards
Morgan Wesström
I'd suggest looking at ebuilds created by g-cpan, which produces ebuilds for
any module in CPAN. I suspect the eclass(es) involved deal with the perl
version issue. I don't think you can savely ignore that, since there are
likely
in the
ebuild (which would naturally break the next time Perl gets updated)?
Regards
Morgan Wesström
Hidden options do not show up until precedents have been enabled. I had to
enable a couple of the HOTPLUG options and then it showed up.
You can press the letter Z to toggle the display of hidden items.
/Morgan
On 2022-01-10 07:44, Lee K wrote:
On Mon, Jan 10, 2022 at 01:59:13AM +0100, Morgan Wesström wrote:
Can someone please elaborate on what's going on here, what the difference is
between --changed-deps=y and @changed-deps, if that difference is intended and
what the recommended update procedure
On a freshly updated system (emerge -uDN @world):
"emerge @changed-deps" wants to reinstall 0 packages.
"emerge -u --changed-deps=y" wants to reinstall 24 packages.
"emerge -uD --changed-deps=y" wants to reinstall 181 packages.
A couple of years ago there was a build breakage in Portage
10 matches
Mail list logo
