tastytea:
> On 2022-07-07 00:19+0200 k...@aspodata.se wrote:
...
> > When emergings with --skipfirst (i.e. skip nodejs),
> > I get:
> > emerge: It seems we have nothing to resume...
> >
> > Checking dependancies:
> > # emerge -vc net-libs/nodejs
>
On 2022.07.06 19:34, k...@aspodata.se wrote:
tastytea:
> On 2022-07-07 00:19+0200 k...@aspodata.se wrote:
...
> > When emergings with --skipfirst (i.e. skip nodejs),
> > I get:
> > emerge: It seems we have nothing to resume...
> >
> > Checking dependancies:
Hi,
Lately I've been getting the following error while trying to emerge
nodejs:
>>> Install nodejs-8.11.1 into /var/tmp/portage/net-libs/nodejs-8.11.1/image/
>>> category net-libs
make -j9 -l8 install DESTDIR=/var/tmp/portage/net-libs/nodejs-8.11.1/image/
make -C ou
On Sunday, 5 March 2023 16:13:24 GMT Arve Barsnes wrote:
> On Sun, 5 Mar 2023 at 16:21, Peter Humphrey wrote:
> > Hello list,
> >
> > Am I the only one unable to install net-libs/nodejs-18.14.2? The log file
> > has>
> > some interesting entries:
> > *
Unfortunately it seems I cannon emerge nodejs due
to this error:
/usr/lib/gcc/x86_64-pc-linux-gnu/10.2.0/../../../../
x86_64-pc-linux-gnu/bin/ld:
failed to set dynamic section sizes: memory exhausted
I tried to stop every process except gettys and the login,
still the same, no MAKEOPTS (i.e. no
On Thu, 7 Jul 2022 00:51:18 +0200, tastytea wrote:
> > When emergings with --skipfirst (i.e. skip nodejs),
> > I get:
> > emerge: It seems we have nothing to resume...
> >
> > Checking dependancies:
> > # emerge -vc net-libs/nodejs
> >
> > Cal
On 2022-07-07 00:19+0200 k...@aspodata.se wrote:
> Unfortunately it seems I cannon emerge nodejs due
> to this error:
>
> /usr/lib/gcc/x86_64-pc-linux-gnu/10.2.0/../../../../
> x86_64-pc-linux-gnu/bin/ld:
> failed to set dynamic section sizes: memory exhausted
>
> I tri
On 2020-10-11 21:34, n952162 wrote:
Apparently after a long series of checks, my emerge simply ended. The
only hint of a problem was this message:
/>>> Running pre-merge checks for net-libs/nodejs-14.4.0//
// * ERROR: net-libs/nodejs-14.4.0::gentoo failed (pretend phase)://
// *
n952162 wrote:
>
> Apparently after a long series of checks, my emerge simply ended. The
> only hint of a problem was this message:
>
> />>> Running pre-merge checks for net-libs/nodejs-14.4.0//
> // * ERROR: net-libs/nodejs-14.4.0::gentoo failed (pretend phase):/
Just as a test set the 'icu inspector' USE FLAGS for net-libs/nodejs,
Then try this command, it should show how many packages would be pulled
in and their USE FLAGS :
emerge -pvt net-libs/nodejs
On 3/9/19 4:24 PM, allan gottlieb wrote:
> In trying to emerge chromium I received
On 2020-10-11 22:23, Dale wrote:
n952162 wrote:
Apparently after a long series of checks, my emerge simply ended.
The only hint of a problem was this message:
/>>> Running pre-merge checks for net-libs/nodejs-14.4.0//
// * ERROR: net-libs/nodejs-14.4.0::gentoo failed (pret
n952162 wrote:
> On 2020-10-11 22:23, Dale wrote:
>> n952162 wrote:
>>>
>>> Apparently after a long series of checks, my emerge simply ended.
>>> The only hint of a problem was this message:
>>>
>>> />>> Running pre-merge checks for
was this message:
>>>>>
>>>>> />>> Running pre-merge checks for net-libs/nodejs-14.4.0//
>>>>> // * ERROR: net-libs/nodejs-14.4.0::gentoo failed (pretend phase)://
>>>>> // * Your CPU doesn't support the required SSE2 ins
In trying to emerge chromium I received an error msg saying that
net-libs/nodejs needed the "inspector" USE flag.
I added
>=net-libs/nodejs-8.12.0 inspector
to
/etc/portage/package.use chromium
Now I receive the msg
!!! The ebuild selected to satisfy ">=
On 2020-10-11 22:57, Dale wrote:
n952162 wrote:
On 2020-10-11 22:23, Dale wrote:
n952162 wrote:
Apparently after a long series of checks, my emerge simply ended.
The only hint of a problem was this message:
/>>> Running pre-merge checks for net-libs/nodejs-14.4.0//
// * ERROR:
On 2020-10-11 22:23, Dale wrote:
n952162 wrote:
Apparently after a long series of checks, my emerge simply ended.
The only hint of a problem was this message:
/>>> Running pre-merge checks for net-libs/nodejs-14.4.0//
// * ERROR: net-libs/nodejs-14.4.0::gentoo failed (pret
Hi. I am having problems emerging nodejs 6.2.1 which happened on my
last update of world.I get the following error output:
[ -x ./node ] && ./node tools/doc/generate.js --node-version=v6.2.1
--format=html --template=doc/template.html doc/api/modules.md >
out/doc/api/modules.h
> On 2021-01-31, at 18:17, Aisha Tammy wrote:
>
> On 1/31/21 8:49 AM, Alessandro Barbieri wrote:
>> I'm trying to package nodejs software and I made an overlay for it here
>> https://github.com/Alessandro-Barbieri/node-overlay
>> <https://github.com/Alessan
Hello list,
When I try to update my system, I have many conflicts.
A first conflict which about I need help is this:
dev-libs/openssl:0
(dev-libs/openssl-1.0.2k:0/0::gentoo, installed) pulled in by
>=dev-libs/openssl-1.0.2g:0=[-bindist] required by
(net-libs/nodejs-7.10.0:0/0::gen
>=dev-libs/openssl-1.0.2g:0=[-bindist] required by
> (net-libs/nodejs-7.10.0:0/0::gentoo, installed)
>
>
>
> >=dev-libs/openssl-1.0.2g:0/0=[-bindist] required by
> (net-libs/nodejs-7.10.0:0/0::gentoo, installed)
>
>
>
> >=dev-libs/o
>>
>> (dev-libs/openssl-1.0.2k:0/0::gentoo, installed) pulled in by
>> >=dev-libs/openssl-1.0.2g:0=[-bindist] required by
>> (net-libs/nodejs-7.10.0:0/0::gentoo, installed)
>>
>> ^^^^
>>
>> >=dev-libs/openssl-1.0.2g:0/0=[-bindist]
I'm trying to package nodejs software and I made an overlay for it here
https://github.com/Alessandro-Barbieri/node-overlay
Could you try it and send feedback?
> On 2018-06-26, at 10:47, Christoph Böhmwalder
> wrote:
>
> Hi,
>
> Lately I've been getting the following error while trying to emerge
> nodejs:
>
>>>>
> * Failed to set XATTR_PAX markings -me
> /var/tmp/portage/net-libs/nodejs-8.11.1/image
ccs.covici.com> writes:
> Hi. I am having problems emerging nodejs 6.2.1
Ok, so you've looked and the real hint is
compile with use flag (-doc) and see what happens.
hth,
James
On 1/31/21 8:49 AM, Alessandro Barbieri wrote:
> I'm trying to package nodejs software and I made an overlay for it here
> https://github.com/Alessandro-Barbieri/node-overlay
> <https://github.com/Alessandro-Barbieri/node-overlay>
> Could you try it and send feedback?
I h
HOME points to /root.
I'm not sure what you mean by "emerge --config output"? Running
`emerge --config` just gives:
# emerge --config nodejs
Configuring pkg...
Warning: ccache requested but no masquerade dircan be found in
/usr/lib*/ccache/bin
* pkg_config() is not defined: 'nodejs-8.11.1.ebuild'
--
Regards,
Christoph
On Sunday, 5 March 2023 15:21:25 GMT Peter Humphrey wrote:
> Hello list,
>
> Am I the only one unable to install net-libs/nodejs-18.14.2? The log file
> has some interesting entries:
It was a typo in /etc/portage/env.
Apologies for the noise.
--
Regards,
Peter.
I agree with all of mjo's points below.
Nodejs is so bad that I don't think its worth investing
your effort into it. There is really very little hope
of fixing their crap. This is a case of its not
you, its them.
But if you do manage to get some sanity into this craziness
I might just
Il Lun 1 Feb 2021, 00:20 Aisha Tammy ha scritto:
> On 1/31/21 8:49 AM, Alessandro Barbieri wrote:
> > I'm trying to package nodejs software and I made an overlay for it here
> > https://github.com/Alessandro-Barbieri/node-overlay <
> https://github.com/Alessandro-Barbie
James wrote:
> ccs.covici.com> writes:
>
>
> > Hi. I am having problems emerging nodejs 6.2.1
>
> Ok, so you've looked and the real hint is
> compile with use flag (-doc) and see what happens.
I was wondering about that, but it did work before, so I thou
tastytea:
> On 2022-07-07 00:19+0200 k...@aspodata.se wrote:
...
> > /usr/lib/gcc/x86_64-pc-linux-gnu/10.2.0/../../../../
> > x86_64-pc-linux-gnu/bin/ld:
> > failed to set dynamic section sizes: memory exhausted
...
> I'm not familiar with nodejs in particular, but
On Wednesday, 6 July 2022 23:19:54 BST k...@aspodata.se wrote:
> Unfortunately it seems I cannon emerge nodejs due
> to this error:
>
> /usr/lib/gcc/x86_64-pc-linux-gnu/10.2.0/../../../../
> x86_64-pc-linux-gnu/bin/ld:
> failed to set dynamic section sizes: memory exhausted
&g
Hello list,
Am I the only one unable to install net-libs/nodejs-18.14.2? The log file has
some interesting entries:
* FEATURES: network-sandbox preserve-libs sandbox userpriv usersandbox
* Checking whether python3_11 is suitable ...
* >=dev-lang/python-3.11.1-r1:3.11[thre
On 27/06/2016 16:19, James wrote:
> ccs.covici.com> writes:
>
>> Hi. I am having problems emerging nodejs 6.2.1 which happened on my
>> last update of world.I get the following error output:
>
> OK, so, I'm "no java whiz" so keep that in mind...
On Sun, 5 Mar 2023 at 16:21, Peter Humphrey wrote:
>
> Hello list,
>
> Am I the only one unable to install net-libs/nodejs-18.14.2? The log file has
> some interesting entries:
>
> * FEATURES: network-sandbox preserve-libs sandbox userpriv usersandbox
> * Checki
ot.
I'm not sure what you mean by "emerge --config output"? Running
`emerge --config` just gives:
# emerge --config nodejs
Configuring pkg...
Warning: ccache requested but no masquerade dircan be found in
/usr/lib*/ccache/bin
* pkg_config() is not defined: 'nodejs-8.11.1.ebuild'
--
Regards,
Christoph
Jack
hy `use x86` is
returning true; surely `amd64` would be the appropriate flag? Strange...
https://gitweb.gentoo.org/repo/gentoo.git/tree/net-libs/nodejs/nodejs-14.4.0.ebuild#n50
--
Ashley Dixon
suugaku.co.uk
2A9A 4117
DA96 D18A
8A7B B0D2
A30E BF25
F290 A8AA
signature.asc
Description: PGP signature
On Sun, 2021-01-31 at 18:42 -0500, Andrew Udvare wrote:
>
> Our best option is to treat Nodejs stuff the way we treat Rust and Go
> packages. Pretend Nodejs 'binaries' are 'built' statically and
> therefore, grab all the dependencies in the main package ebuild.
.1.1:0= required by
(net-libs/nodejs-13.5.0:0/0::gentoo, ebuild scheduled for merge) USE="npm
snapshot ssl -debug -doc -icu -inspector -pax_kernel -sy
Is it possible to continue a failed emerge ?
///
With nodejs, I get:
/usr/lib/gcc/x86_64-pc-linux-gnu/10.2.0/../../../../x86_64-pc-linux-gnu/bin/ld:
failed to set dynamic section sizes: memory exhausted
so, instead of redoing the whole compile, can I, after reducing
current memory usage, set
Anyone here familiar with driving nodejs and npm?
I'm trying to write an ebuild for a musicbrainz mirror server and "npm
install" keeps erroring out with one of two errors:
1. The install does finish but npm doesn't get around to exiting,
verified by stopping the emerge,
On Thu, Sep 17, 2015 at 09:24:39PM +0200, Alan McKinnon wrote:
> On 17/09/2015 20:50, Michael Orlitzky wrote:
> > On 09/17/2015 10:03 AM, Alan McKinnon wrote:
> >> Anyone here familiar with driving nodejs and npm?
> >>
> >> I'm trying to write an ebuild
ccs.covici.com> writes:
> Hi. I am having problems emerging nodejs 6.2.1 which happened on my
> last update of world.I get the following error output:
OK, so, I'm "no java whiz" so keep that in mind
I was just able to install it::
Installed versions: 6.2.
serious than a simple request to add the icu USE flag to
nodejs.
That's actually exactly what that means. The ebuild states that if
"inspector" is set, then you also need to set "icu" and "ssl".
ncv no_tmpfs.conf
#net-libs/nodejs no_tmpfs.conf
#net-misc/openssh no_tmpfs.conf
#sci-libs/tensorflow no_tmpfs.conf
#sys-apps/iproute2 no_tmpfs.conf
#sys-devel/clang no_tmpfs.conf
#sys-devel/gcc no_tmpfs.conf
#www-client/chromium no_tmpfs.conf #throttle_make_emerge.conf
#www-cli
Am So., 5. Jan. 2020 um 19:11 Uhr schrieb :
>
> As far as my knowledge of portagese goes it means: Man, decide what
> you want: This software or that software...you cannot get both.
>
> So I have to decide, whether I want atpm or nodejs...
>
Portagese is funny, but sometimes
On 01/05 07:22, Franz Fellner wrote:
> Am So., 5. Jan. 2020 um 19:11 Uhr schrieb :
>
> >
> > As far as my knowledge of portagese goes it means: Man, decide what
> > you want: This software or that software...you cannot get both.
> >
> > So I have to d
Dnia 2022-07-06, o godz. 15:48:04
k...@aspodata.se napisał(a):
> Is it possible to continue a failed emerge ?
>
> ///
>
> With nodejs, I get:
>
> /usr/lib/gcc/x86_64-pc-linux-gnu/10.2.0/../../../../x86_64-pc-linux-gnu/bin/ld:
> failed to set dynamic section sizes:
On Wed, 6 Jul 2022 15:48:04 +0200 (CEST), k...@aspodata.se wrote:
> With nodejs, I get:
>
> /usr/lib/gcc/x86_64-pc-linux-gnu/10.2.0/../../../../x86_64-pc-linux-gnu/bin/ld:
> failed to set dynamic section sizes: memory exhausted
>
> so, instead of redoing the whole com
0:14, it's now 21:16 and still going so 9
hours at least on this machine to build a browser - almost as bad as
openoffice at it's worst (regularly took 12 hours). Nodejs also took a
while, but I didn't record time.
What other packages have huge build times?
--
Alan McKinnon
alan
llowing complete expression:
>> python_targets_python2_7 inspector? ( icu ssl ) npm? ( ssl )
>>
>> This seems more serious than a simple request to add the icu USE flag to
>> nodejs.
> That's actually exactly what that means. The ebuild states that if
> "inspector" is set, then you
make sense to me? Is SSE2 required for building/
running NodeJS on x86 machines?
--
Ashley Dixon
suugaku.co.uk
2A9A 4117
DA96 D18A
8A7B B0D2
A30E BF25
F290 A8AA
signature.asc
Description: PGP signature
which doesn't make sense to me? Is SSE2 required for building/
running NodeJS on x86 machines?
But how can my CPU be mistaken for a 32-bit machine?
/Intel(R) Core(TM)2 Duo CPU E7500 @ 2.93GHz/
are or that software...you cannot get both.
> > >
> > > So I have to decide, whether I want atpm or nodejs...
> > >
> >
> > Portagese is funny, but sometimes Ebuildian is more usefull.
> > Get the basics and dive into the tree of tears.
> > Look at the opposi
>
>
> -Original Message-
> From: Neil Bothwick
> Sent: Wednesday, July 6, 2022 7:05 AM
> To: gentoo-user@lists.gentoo.org
> Subject: Re: [gentoo-user] continuing an emerge
>
> On Wed, 6 Jul 2022 15:48:04 +0200 (CEST), k...@aspodata.se wrote:
>
> &g
but why didn't --load-average=32 take precedence?
--->8
> Some packages that I build with either a greatly reduced -j setting or
> a non-tmpfs build directory are:
> sys-cluster/ceph
> dev-python/scipy
> dev-python/pandas
> app-office/calligra
> net-libs/nodejs
> d
hing.
>
> chromium has been building since 10:14, it's now 21:16 and still going
> so 9 hours at least on this machine to build a browser - almost as bad
> as openoffice at it's worst (regularly took 12 hours). Nodejs also
> took a while, but I didn't record t
On Mon, 11 Sep 2023 21:19:27 +0200, Alan McKinnon wrote:
> chromium has been building since 10:14, it's now 21:16 and still going
> so 9 hours at least on this machine to build a browser - almost as bad
> as openoffice at it's worst (regularly took 12 hours). Nodejs also to
On 17/09/2015 22:53, Alec Ten Harmsel wrote:
> On Thu, Sep 17, 2015 at 09:24:39PM +0200, Alan McKinnon wrote:
>> On 17/09/2015 20:50, Michael Orlitzky wrote:
>>> On 09/17/2015 10:03 AM, Alan McKinnon wrote:
>>>> Anyone here familiar with driving nodejs and npm?
&g
fs.conf
#dev-lang/ghc no_tmpfs.conf
#dev-lang/ghc no_tmpfs.conf
#dev-lang/mono no_tmpfs.conf
#dev-lang/rust no_tmpfs.conf
#dev-lang/spidermonkey no_tmpfs.conf
#dev-libs/libpcre no_tmpfs.conf
#dev-qt/qtwebengine no_tmpfs.conf #throttle_make_emerge.conf
#mail-client/thunder
On 11/09/2023 22:19, Alan McKinnon wrote:
chromium has been building since 10:14, it's now 21:16 and still going
so 9 hours at least on this machine to build a browser - almost as bad
as openoffice at it's worst (regularly took 12 hours). Nodejs also took
a while, but I didn
RAM-hungry.
Right now my list includes:
calligra
qtwebengine
qtwebkit
ceph
nodejs
passwdqc
scipy
pandas
spidermonkey
(It has been ages since I've pruned the list, and of course what is
"too much RAM" will vary.)
The other thing I will tweak is avoiding building in a tmpfs.
Obvious
o me?
> > Is SSE2 required for building/ running NodeJS on x86 machines?
> >
>
> But how can my CPU be mistaken for a 32-bit machine?
>
> /Intel(R) Core(TM)2 Duo CPU E7500 @ 2.93GHz/
It's not your CPU type but the type of CPU you are building for. The key
informa
d as
> openoffice at it's worst (regularly took 12 hours). Nodejs also took a
> while, but I didn't record time.
>
>
> What other packages have huge build times?
>
> --
> Alan McKinnon
> alan dot mckinnon at gmail dot com
>
>
>
> I have some software y
s openoffice at it's worst (regularly took 12 hours). Nodejs also took
a while, but I didn't record time.
What other packages have huge build times?
--
Alan McKinnon
alan dot mckinnon at gmail dot com
FYI this info and use flags worked for me to get a clean *electron* build
(with also getting eg *nodejs *dependency). I think also works for
chromium. I doubt "static-libs" is making any difference:
*/etc/portage>* emerge --info electron
dev-libs/openssl-1.0.2l::gentoo was b
aroud her and want to use that one to run
capisuite directly on the Raspberry (i wrote some kind of messaging-server in
nodeJS...) to store calls and faxes... if this is impossible i would like to
use USBIP on the pi and use the FritzCard on my other gentoo Server... The Pi
sits right left to
t make sense to me?
Is SSE2 required for building/ running NodeJS on x86 machines?
But how can my CPU be mistaken for a 32-bit machine?
/Intel(R) Core(TM)2 Duo CPU E7500 @ 2.93GHz/
It's not your CPU type but the type of CPU you are building for. The key
information from emerge --inf
now 21:16 and still going so
> 9 hours at least on this machine to build a browser - almost as bad as
> openoffice at it's worst (regularly took 12 hours). Nodejs also took a
> while, but I didn't record time.
>
>
> What other packages have huge build times?
>
> --
; as openoffice at it's worst (regularly took 12 hours). Nodejs also took
> > a while, but I didn't record time.
>
> Chromium is definitely the worst, and strangely variable. The last few
> compiles have taken between 6 and 14 hours. Since it takes longer than
> everyth
On Mon, 2021-02-01 at 05:23 -0500, Andrew Udvare wrote:
> >
> > 1. Nothing is shared between packages so build time and disk
> > usage skyrockets.
>
> This is NodeJS and 99% of stuff is plain JavaScript. Many packages
> are tiny. More time will be spent unpa
> On 2018-06-26, at 15:44, Christoph Böhmwalder
> wrote:
>
> On Tue, Jun 26, 2018 at 03:15:09PM -0400, Andrew Udvare wrote:
>> It should not be accessing this location in any case. What is the
>> environment like? What does env show? emerge --config output?
>>
>> It would almost seem like y
e at it's worst (regularly took 12 hours). Nodejs also took
> > a while, but I didn't record time.
>
> What's your CPU and how much RAM? Even on my older system I had (an
> 4-core i5 2500K) libreoffice took like 2 hours or so to build.
>
>
> > What other pa
> On 2018-06-26, at 16:18, Jack wrote:
>
> On 2018.06.26 15:44, Christoph Böhmwalder wrote:
>> On Tue, Jun 26, 2018 at 03:15:09PM -0400, Andrew Udvare wrote:
>> > It should not be accessing this location in any case. What is the
>> > environment like? What does env show? emerge --config output
.env.
Also, RAM pressure could also come from the build directory if it is
on tmpfs, which of course many of us use.
Some packages that I build with either a greatly reduced -j setting or
a non-tmpfs build directory are:
sys-cluster/ceph
dev-python/scipy
dev-python/pandas
app-office/calligra
net
gt; it's building with -j2 which means this error is 1 back.
> > >
> > > No idea how to solve.
> >
> > OK, here it is with -j1, still not sure where the exact error is:
>
> I think it complains about the internationalisation components for unicode -
>
On 09/17/2015 10:03 AM, Alan McKinnon wrote:
> Anyone here familiar with driving nodejs and npm?
>
> I'm trying to write an ebuild for a musicbrainz mirror server and "npm
> install" keeps erroring out with one of two errors:
>
> 1. The install does finish but
s/icu:0
(dev-libs/icu-65.1:0/65.1::gentoo, ebuild scheduled for merge) conflicts with
>=dev-libs/icu-64.2:0/64.2= required by
(net-libs/nodejs-12.13.0:0/0::gentoo, installed)
dev-libs/icu:0/64.2= required by (app-text/libqxp-0.0.2:0/0::
> so 9 hours at least on this machine to build a browser - almost as bad
> > > as openoffice at it's worst (regularly took 12 hours). Nodejs also took
> > > a while, but I didn't record time.
> >
> > Chromium is definitely the worst, and strangely variable. The
/null -o /dev/null
> F: mkdir
> S: deny
> P: /root/.ccache/3
> A: /root/.ccache/3
> R: /root/.ccache/3
> C: x86_64-pc-linux-gnu-gcc -x c -v -c /dev/null -o /dev/null
> *
>
----
Has anyone else run into sporadic build failures like this?
I've had similar issues with vario
e many of us use.
>
> Some packages that I build with either a greatly reduced -j setting or
> a non-tmpfs build directory are:
> sys-cluster/ceph
> dev-python/scipy
> dev-python/pandas
> app-office/calligra
> net-libs/nodejs
> dev-qt/qtwebengine
> dev-qt/qtwebkit
&g
x86 is used and SSE2
is disabled, which doesn't make sense to me? Is SSE2 required for building/
running NodeJS on x86 machines?
But how can my CPU be mistaken for a 32-bit machine?
/Intel(R) Core(TM)2 Duo CPU E7500 @ 2.93GHz/
02~/adm/gentoo/emerged>less /proc/cpuinfo
proce
had any problems with it.
Could you explain a little bit more why "su -" should be used instead.
It's not so much needing the root environment, it's that sometimes
things in your own environment cause problems if not removed when
emerge runs. There is another recent thread abo
building since 10:14, it's now 21:16 and still
> going
> > > > so 9 hours at least on this machine to build a browser - almost as
> bad
> > > > as openoffice at it's worst (regularly took 12 hours). Nodejs also
> took
> > > > a while, but I
t;su" for already 3 years, since switched to Gentoo from
>> Ubuntu and never had any problems with it.
>>
>> Could you explain a little bit more why "su -" should be used instead.
>
> It's not so much needing the root environment, it's that sometimes thing
ith beyond just
> > figuring out what needs more RAM and making exceptions in package.env.
> >
> > Also, RAM pressure could also come from the build directory if it is
> > on tmpfs, which of course many of us use.
> >
> > Some packages that I build with either a gr
Nothing is shared between packages so build time and disk
> usage skyrockets.
This is NodeJS and 99% of stuff is plain JavaScript. Many packages are tiny.
More time will be spent unpacking tiny distfiles and re-arranging them the way
Node/Yarn/etc like to see them.
In Rust and Go, with Port
On Thu, Sep 17, 2015 at 11:13:10PM +0200, Alan McKinnon wrote:
> On 17/09/2015 22:53, Alec Ten Harmsel wrote:
> > Unfortunately, the right way with nodejs/ruby web stuff is to use the
> > tooling specific to the language. If this[1] is what you're trying to
> > depl
and
still going
> > > so 9 hours at least on this machine to build a browser -
almost as bad
> > > as openoffice at it's worst (regularly took 12 hours).
Nodejs also took
> > > a while, but I didn't record time.
> >
> > Chro
so, then od quickly dumps
51952 bytes of hex output, then another long pause before dumping
another 60480 bytes of hex. If I try this with "pigz -cd" instead of
"gunzip" then output starts flowing after just ~400 bytes, but sadly
that still doesn't work for build.log.
On 17/09/2015 20:50, Michael Orlitzky wrote:
> On 09/17/2015 10:03 AM, Alan McKinnon wrote:
>> Anyone here familiar with driving nodejs and npm?
>>
>> I'm trying to write an ebuild for a musicbrainz mirror server and "npm
>> install" keeps erroring out wi
23 21:19:27 +0200, Alan McKinnon wrote:
> > > > > chromium has been building since 10:14, it's now 21:16 and
> > still going
> > > > > so 9 hours at least on this machine to build a browser -
> > almost as bad
> > > > > as op
ebuild scheduled for merge)
dev-libs/openssl:0= required by (net-misc/mosh-1.3.2:0/0::gentoo, installed)
=dev-libs/openssl-1.0.2*:0=[-bindist] required by
(net-libs/nodejs-8.15.0:0/0::gentoo, ebuild scheduled for merge)
dev-libs/openssl:0= required by (dev-lang/php-5.6.40:5.6/5.6::gentoo,
o USE="acl apache2 bcmath
berkdb bzip2 cgi cli ctype curl fileinfo filter fpm ftp gd gdbm hash iconv imap
ipv6 json ldap mhash mysql mysqli nls odbc opcache pcntl pdo phar posix
postgres readline session sharedmem simplexml sockets spell sqlite ssl sysvipc
tokenizer truetype unicode xml xmlreade
ot;-clippy -debug (-doc) -libressl
(-miri) (-nightly) (-parallel-compiler) -rls -rustfmt
(-system-bootstrap) (-system-llvm) -test% -wasm" ABI_X86="(64) -32
(-x32)" CPU_FLAGS_X86="sse2" LLVM_TARGETS="(X86) -AArch64 -AMDGPU -ARM
-AVR% -BPF -Hexagon -Lanai -MSP430 -Mips -NVPTX -
ot;-clippy -debug (-doc) -libressl
(-miri) (-nightly) (-parallel-compiler) -rls -rustfmt
(-system-bootstrap) (-system-llvm) -test% -wasm" ABI_X86="(64) -32
(-x32)" CPU_FLAGS_X86="sse2" LLVM_TARGETS="(X86) -AArch64 -AMDGPU -ARM
-AVR% -BPF -Hexagon -Lanai -MSP430 -Mips -NVP
ython3_7 python3_8* -python3_6 -python3_9" 0 KiB
[ebuild U ] dev-lang/rust-1.47.0-r2:stable/1.47::gentoo
[1.46.0:stable/1.46::gentoo] USE="-clippy -debug (-doc) -libressl
(-miri) (-nightly) (-parallel-compiler) -rls -rustfmt
(-system-bootstrap) (-system-llvm) -test% -wasm" A
97 matches
Mail list logo
