| View previous topic :: View next topic |
| Author |
Message |
jpsollie
Guru
Joined: 17 Aug 2013
Posts: 317
|
 Posted: Mon Sep 30, 2024 7:55 am Post subject: |
 |
|
| logrusx wrote: | | jpsollie wrote: |
*EDIT* : I assume you meant --builtpkgonly. |
| man emerge: | --buildpkg [ y | n ], -b
Tells emerge to build binary packages for all ebuilds processed in addition to actually merging the packages. Useful for maintainers or if you administrate multiple Gentoo Linux systems (build
once, emerge tbz2s or gpkgs everywhere) as well as disaster recovery. The package will be created in the PKGDIR directory (see make.conf(5)). An alternative for already-merged packages is to use
quickpkg(1) which creates a tbz2 or gpkg from the live filesystem.
...
--buildpkgonly, -B
Creates binary packages for all ebuilds processed without actually merging the packages. This comes with the caveat that all build-time dependencies must already be emerged on the system.
|
Buildpkgonly will break because portage needs the packages merged to link against them. Essentially you'll have almost identical copy of your laptop's system in that chroot. I think you could even synchronize it with rsync but it would be easier if you used binary packages.
Also, why are you not able to run emerge or compile distcc on the build server? How did you built it first place? It doesn't require gui. Only ssh.
Best Regards,
Georgi |
The build server is fine. However: it has no GUI and I'd like to keep it that way.
Compiling qtwebengine into a binary package requires some compile-time dependencies which need to be installed before the package can be compiled, eg qtbase.
If I need to install all this junk onto a no-gui system, binary packages may indeed be the fastest way out
_________________
The power of Gentoo optimization (not overclocked): [img]https://www.passmark.com/baselines/V10/images/503714802842.png[/img] |
|
| Back to top |
|
 |
jpsollie
Guru
Joined: 17 Aug 2013
Posts: 317
|
| Posted: Mon Sep 30, 2024 10:09 am Post subject: |
|
|
| Zucca wrote: | | Quote: | | Code: | | distcc[3974] (dcc_execvp) ERROR: failed to exec x86_64-pc-linux-gnu-g++: Argument list too long |
|
I think this a is bug. Bug in the upstream build process or in distcc.
It's quite rare to reach this limit. I mean, I think it's something like 2 megabytes or more arguments until this error is triggered. |
building without distcc took 6hrs, but compiled.
so far, so good.
Can the feature flag for distcc be turned off for a specific package?
_________________
The power of Gentoo optimization (not overclocked): [img]https://www.passmark.com/baselines/V10/images/503714802842.png[/img] |
|
| Back to top |
|
|
Goverp
Advocate
Joined: 07 Mar 2007
Posts: 2128
|
| Posted: Mon Sep 30, 2024 10:48 am Post subject: |
|
|
<Aside - as I've not followed this discussion - the problems with command line too long might be down to jumbo-build.
It might be worth creating an env file specifying: | Code: | | EXTRA_GN='jumbo_file_merge_limit=16' |
The law of diminishing returns applies for this>
_________________
Greybeard |
|
| Back to top |
|
|
jpsollie
Guru
Joined: 17 Aug 2013
Posts: 317
|
| Posted: Mon Sep 30, 2024 11:02 am Post subject: |
|
|
| Goverp wrote: | <Aside - as I've not followed this discussion - the problems with command line too long might be down to jumbo-build.
It might be worth creating an env file specifying: | Code: | | EXTRA_GN='jumbo_file_merge_limit=16' |
The law of diminishing returns applies for this> |
would this also be useful when the jumbo_build flag isn't set?
_________________
The power of Gentoo optimization (not overclocked): [img]https://www.passmark.com/baselines/V10/images/503714802842.png[/img] |
|
| Back to top |
|
|
logrusx
Advocate
Joined: 22 Feb 2018
Posts: 2247
|
| Posted: Mon Sep 30, 2024 12:05 pm Post subject: |
|
|
| jpsollie wrote: | | Goverp wrote: | <Aside - as I've not followed this discussion - the problems with command line too long might be down to jumbo-build.
It might be worth creating an env file specifying: | Code: | | EXTRA_GN='jumbo_file_merge_limit=16' |
The law of diminishing returns applies for this> |
would this also be useful when the jumbo_build flag isn't set? |
This is a parameter to jumbo built. It won't matter when jumbo is not enabled.
I'm curious, what are your arguments against building in a chroot. What are your arguments against using the binhost.
You're running circles around those and very rarely state your reasons.
Best Regards,
Georgi |
|
| Back to top |
|
|
|
Portage & Programming
