Re: [gentoo-user] chromium build failure

[allan gottlieb]

On Wed, Jan 31 2018, Canek Peláez Valdés wrote:

> On Wed, Jan 31, 2018 at 1:29 PM, allan gottlieb  wrote:
> [snip]
>> I have two questions, one trivial, one hopefully easy.
>>
>> 1. (trivial) In your recipe did you mean "rsync", not "sync"?
>
> I sync ("emerge --sync") only one machine, and then I rsync from there to
> my other computers. After the rsync is done, you need to do "emerge
> --metadata" in the recipient machine (--sync does that for you
> automatically).

So sync referred to an emerge command and when you copied files from
machine to machine you used rsync.  Thanks.
>
>> 2. I have a number of quickpkgs built.  Is it needed that
>>they all be updated and some removed or can I just do
>>the following command
>>
>>rsync -Pvase ssh machine1:/var/portage/packages/www-client \
>>  /var/portage/packages
>>
>>Notes: I use /var not /usr for portage
>>   machine2 has no dir /var/portage/packages/www-client
>
> I honestly don't know. There is a /usr/portage/packages/Packages with a lot
> of meta information, and I'm not 100% sure whether is absolutely required.
> Then again, creating binary packages is so fast that I usually delete
> /usr/portage/packages after updating my non-compiling machines. I know of
> people who maintain a large repository of binary packages (they can be
> built automatically with FEATURES="buildpkg" in make.conf), but I just
> create them when needed.

I have FEATURES="buildsyspkg" on all machines for safety.
It has worked in the sense that I have never needed to use
the resulting packages.

But I see your point that /var/portage/packages/Packages
may need to be updated on the target machine so it is probably
best to do your rsync of all of /var/portage/packages
>
> Regards.
> --
> Dr. Canek Peláez Valdés

thanks,
allan

Re: [gentoo-user] chromium build failure

[Neil Bothwick]

On Wed, 31 Jan 2018 15:38:27 -0600, Canek Peláez Valdés wrote:

> I sync ("emerge --sync") only one machine, and then I rsync from there
> to my other computers. After the rsync is done, you need to do "emerge
> --metadata" in the recipient machine (--sync does that for you
> automatically).

If you run the rsync daemon on the machine you --sync, you can set that
as the source for the other computers and emerge --sync on them, which
saves the extra step of updating the metadata.


-- 
Neil Bothwick

Men who go out with flat chested woman have reasons for feeling down


pgphioJRq5zKg.pgp
Description: OpenPGP digital signature

Re: [gentoo-user] chromium build failure

[Canek Peláez Valdés]

On Wed, Jan 31, 2018 at 1:29 PM, allan gottlieb  wrote:
[snip]
> I have two questions, one trivial, one hopefully easy.
>
> 1. (trivial) In your recipe did you mean "rsync", not "sync"?

I sync ("emerge --sync") only one machine, and then I rsync from there to
my other computers. After the rsync is done, you need to do "emerge
--metadata" in the recipient machine (--sync does that for you
automatically).

> 2. I have a number of quickpkgs built.  Is it needed that
>they all be updated and some removed or can I just do
>the following command
>
>rsync -Pvase ssh machine1:/var/portage/packages/www-client \
>  /var/portage/packages
>
>Notes: I use /var not /usr for portage
>   machine2 has no dir /var/portage/packages/www-client

I honestly don't know. There is a /usr/portage/packages/Packages with a lot
of meta information, and I'm not 100% sure whether is absolutely required.
Then again, creating binary packages is so fast that I usually delete
/usr/portage/packages after updating my non-compiling machines. I know of
people who maintain a large repository of binary packages (they can be
built automatically with FEATURES="buildpkg" in make.conf), but I just
create them when needed.

Regards.
--
Dr. Canek Peláez Valdés
Profesor de Carrera Asociado C
Departamento de Matemáticas
Facultad de Ciencias
Universidad Nacional Autónoma de México

Re: [gentoo-user] chromium build failure

[allan gottlieb]

On Wed, Jan 24 2018, Canek Peláez Valdés wrote:

> On Wed, Jan 24, 2018 at 10:11 PM, allan gottlieb  wrote:
>>
>> I ran the build failed twice, each time with MAKEOPTS="--jobs=1" and the
>> build logs are essentially identical.  After about 12 hours compiling and
>> 36MB of build.log, the error shown below occurs
>>
>> I have two laptops with *very* similar gentoo distributions.  The newer
>> machine had a successful build first try.  The second older (4 years)
>> machine had both failures.  Each machine has profile
>> default/linux/amd64/17.0/desktop/gnome/systemd
>
> If the USE flags for chromium on both machines are the same, simply create
> a binary package from the machine that already built it.
>
> machine1:
>
> $ quickpkg --include-config=y www-client/chromium
>
> machine2
>
> $ sync --delete -Pvase ssh machine1:/usr/portage/packages/
> /usr/portage/packages/
> $ emerge --nodeps -1Kv www-client/chromium

Canek,

Again thank you for your recipe.

I have two questions, one trivial, one hopefully easy.

1. (trivial) In your recipe did you mean "rsync", not "sync"?

2. I have a number of quickpkgs built.  Is it needed that
   they all be updated and some removed or can I just do
   the following command

   rsync -Pvase ssh machine1:/var/portage/packages/www-client \
 /var/portage/packages

   Notes: I use /var not /usr for portage
  machine2 has no dir /var/portage/packages/www-client

Thanks in advance,
allan

Re: [gentoo-user] chromium build failure

[allan gottlieb]

On Thu, Jan 25 2018, Neil Bothwick wrote:

> On Wed, 24 Jan 2018 22:29:59 -0600, Canek Peláez Valdés wrote:
>
>> > I have two laptops with *very* similar gentoo distributions.  The
>> > newer machine had a successful build first try.  The second older (4
>> > years) machine had both failures.  Each machine has profile
>> > default/linux/amd64/17.0/desktop/gnome/systemd  
>> 
>> If the USE flags for chromium on both machines are the same, simply
>> create a binary package from the machine that already built it.
>
> Good idea, as long as the CFLAGS are the same too.

Thank you both.  I will try it.
allan

Re: [gentoo-user] chromium build failure

[Neil Bothwick]

On Wed, 24 Jan 2018 22:29:59 -0600, Canek Peláez Valdés wrote:

> > I have two laptops with *very* similar gentoo distributions.  The
> > newer machine had a successful build first try.  The second older (4
> > years) machine had both failures.  Each machine has profile
> > default/linux/amd64/17.0/desktop/gnome/systemd  
> 
> If the USE flags for chromium on both machines are the same, simply
> create a binary package from the machine that already built it.

Good idea, as long as the CFLAGS are the same too.


-- 
Neil Bothwick

Like an atheist in a grave: all dressed up and no place to go.


pgpWxemlAMKhH.pgp
Description: OpenPGP digital signature

Re: [gentoo-user] chromium build failure

[Canek Peláez Valdés]

On Wed, Jan 24, 2018 at 10:11 PM, allan gottlieb  wrote:
>
> I ran the build failed twice, each time with MAKEOPTS="--jobs=1" and the
> build logs are essentially identical.  After about 12 hours compiling and
> 36MB of build.log, the error shown below occurs
>
> I have two laptops with *very* similar gentoo distributions.  The newer
> machine had a successful build first try.  The second older (4 years)
> machine had both failures.  Each machine has profile
> default/linux/amd64/17.0/desktop/gnome/systemd

If the USE flags for chromium on both machines are the same, simply create
a binary package from the machine that already built it.

machine1:

$ quickpkg --include-config=y www-client/chromium

machine2

$ sync --delete -Pvase ssh machine1:/usr/portage/packages/
/usr/portage/packages/
$ emerge --nodeps -1Kv www-client/chromium

I have two powerful desktop computers (home and office) and a laptop. Their
USE flags are identical; I just compile in one of them and generate binary
packages for the other two. It helps (but it's not 100% required) if the
/usr/portage tree is identical (I sync only with one and rsync the others,
followed by emerge --metadata).

Regards.
--
Dr. Canek Peláez Valdés
Profesor de Carrera Asociado C
Departamento de Matemáticas
Facultad de Ciencias
Universidad Nacional Autónoma de México