[SOLVED] ERROR: Failed to extract chromium-17...

1archgamenon2 · 2012-01-02 22:41:00

couldn't install chromium-dev

um-17.0.963.12/chrome_frame'Can't create 'chromium-17.0.963.12/chrome_frame/tools/test/page_cycler/urllist'
chromium-17.0.963.12/chrome_frame/simple_resource_loader.h: Failed to create dir 'chromium-17.0.963.12/chrome_frame'Can't create 'chromium-17.0.963.12/chrome_frame/simple_resource_loader.h'
chromium-17.0.963.12/chrome_frame/bind_context_info.h: Failed to create dir 'chromium-17.0.963.12/chrome_frame'Can't create 'chromium-17.0.963.12/chrome_frame/bind_context_info.h'
chromium-17.0.963.12/chrome_frame/chrome_launcher_utils.h: Failed to create dir 'chromium-17.0.963.12/chrome_frame'Can't create 'chromium-17.0.963.12/chrome_frame/chrome_launcher_utils.h'
chromium-17.0.963.12/chrome_frame/urlmon_upload_data_stream.cc: Failed to create dir 'chromium-17.0.963.12/chrome_frame'Can't create 'chromium-17.0.963.12/chrome_frame/urlmon_upload_data_stream.cc'
chromium-17.0.963.12/chrome_frame/unittest_precompile.h: Failed to create dir 'chromium-17.0.963.12/chrome_frame'Can't create 'chromium-17.0.963.12/chrome_frame/unittest_precompile.h'
chromium-17.0.963.12/chrome_frame/cfproxy_test.cc: Failed to create dir 'chromium-17.0.963.12/chrome_frame'Can't create 'chromium-17.0.963.12/chrome_frame/cfproxy_test.cc'
chromium-17.0.963.12/chrome_frame/stream_impl.h: Failed to create dir 'chromium-17.0.963.12/chrome_frame'Can't create 'chromium-17.0.963.12/chrome_frame/stream_impl.h'
chromium-17.0.963.12/chrome_frame/chrome_frame_plugin.h: Failed to create dir 'chromium-17.0.963.12/chrome_frame'Can't create 'chromium-17.0.963.12/chrome_frame/chrome_frame_plugin.h'
chromium-17.0.963.12/chrome_frame/ie8_types.h: Failed to create dir 'chromium-17.0.963.12/chrome_frame'Can't create 'chromium-17.0.963.12/chrome_frame/ie8_types.h'
chromium-17.0.963.12/chrome_frame/cfproxy_proxy.cc: Failed to create dir 'chromium-17.0.963.12/chrome_frame'Can't create 'chromium-17.0.963.12/chrome_frame/cfproxy_proxy.cc'
bsdtar: Error exit delayed from previous errors.
==> ERROR: Failed to extract chromium-17.0.963.12.tar.bz2
    Aborting...
The build failed.

Last edited by 1archgamenon2 (2012-01-06 22:55:59)

samuvuo · 2012-01-03 04:18:32

Are you running the install command (packer, yaourt...) as root (with sudo)?

1archgamenon2 · 2012-01-03 11:44:42

Yep!

 sudo packer -S chromium-dev

1archgamenon2 · 2012-01-03 19:18:49

no one?

wonder · 2012-01-03 19:27:13

maybe /tmp is full

1archgamenon2 · 2012-01-04 16:44:48

wonder wrote:

maybe /tmp is full

and...how to know it? if it is possible...

DarkSniper · 2012-01-05 04:21:08

1archgamenon2 wrote:

wonder wrote:
maybe /tmp is full
and...how to know it? if it is possible...

You can check /tmp's free space with this command:

df -h /tmp

Wouldn't be all that surprising if this is the culprit, since Chromium's a huge package to compile. I had to bump my /tmp space up to 2GB in order to build it successfully with yaourt.

Last edited by DarkSniper (2012-01-05 04:22:13)

1archgamenon2 · 2012-01-05 14:02:01

DarkSniper wrote:

You can check /tmp's free space with this command:
df -h /tmp

$ df -h /tmp
Filesystem      Size  Used Avail Use% Mounted on
tmpfs           246M  8.0K  246M   1% /tmp

DarkSniper · 2012-01-05 18:32:11

1archgamenon2 wrote:

DarkSniper wrote:
You can check /tmp's free space with this command:
df -h /tmp
$ df -h /tmp
Filesystem      Size  Used Avail Use% Mounted on
tmpfs           246M  8.0K  246M   1% /tmp

Assuming du was run without the failed chrome build, and you or your AUR helper is building things in /tmp, you're definitely running out of space.
The compressed source code alone is about 170MB, and it peaks at around 1.8 GB of usage at the very end when it starts to compress the final package.

Here's a few things that could possibly fix the issue:

If you have less than 4GB of ram and cannot have a large ram-mounted /tmp:
- Use makepkg to build it somewhere on your hard drive without an AUR helper [if you use one]
- Make a /tmp partition on your hard drive as opposed to using tmpfs in your RAM
- If you use an AUR helper, edit its configuration to store temporary sources somewhere on your hard drive, as opposed to your ram-mounted /tmp

If you have 4GB or more of ram, you should make /tmp bigger with a line similar to this one in /etc/fstab

tmpfs		/tmp			tmpfs		defaults,noatime,nodev,nosuid,mode=1777,size=2048m		0	0

1archgamenon2 · 2012-01-05 21:03:16

Thx dude! anyway chromium is too fat...i'll stay quiet with firefox-aurora...

1archgamenon2 · 2012-01-06 16:27:01

Well...I can't install 'nada'(trying to install VLC-DEV):

c-dev/vlc-dev/pkg/)
libtool: install: /bin/install -c .libs/libxa_plugin.soT /tmp/packerbuild-0/vlc-dev/vlc-dev/pkg//usr/lib/vlc/plugins/demux/libxa_plugin.so
libtool: install: /bin/install -c .libs/libxa_plugin.lai /tmp/packerbuild-0/vlc-dev/vlc-dev/pkg//usr/lib/vlc/plugins/demux/libxa_plugin.la
libtool: install: warning: relinking `libimage_plugin.la'
libtool: install: (cd /tmp/packerbuild-0/vlc-dev/vlc-dev/src/vlc-1.2.0-pre3/modules/demux; /bin/sh /tmp/packerbuild-0/vlc-dev/vlc-dev/src/vlc-1.2.0-pre3/libtool  --silent --tag CC --mode=relink gcc -std=gnu99 -march=i686 -mtune=generic -O2 -pipe -fstack-protector --param=ssp-buffer-size=4 -D_FORTIFY_SOURCE=2 -Wall -Wextra -Wsign-compare -Wundef -Wpointer-arith -Wbad-function-cast -Wwrite-strings -Wmissing-prototypes -Wvolatile-register-var -Werror-implicit-function-declaration -fvisibility=hidden -ffast-math -funroll-loops -fomit-frame-pointer -mtune=pentium2 -rpath /usr/lib/vlc/plugins/demux -avoid-version -module -export-symbols-regex "^vlc_entry" -shrext .so -no-undefined -Wl,-O1,--sort-common,--as-needed,-z,relro,--hash-style=gnu -o libimage_plugin.la -rpath /usr/lib/vlc/plugins/demux libimage_plugin_la-image.lo ../../src/libvlccore.la ../../compat/libcompat.la -lpthread -inst-prefix-dir /tmp/packerbuild-0/vlc-dev/vlc-dev/pkg/)
libtool: install: /bin/install -c .libs/libimage_plugin.soT /tmp/packerbuild-0/vlc-dev/vlc-dev/pkg//usr/lib/vlc/plugins/demux/libimage_plugin.so
libtool: install: /bin/install -c .libs/libimage_plugin.lai /tmp/packerbuild-0/vlc-dev/vlc-dev/pkg//usr/lib/vlc/plugins/demux/libimage_plugin.la
libtool: install: warning: relinking `libdemux_stl_plugin.la'
libtool: install: (cd /tmp/packerbuild-0/vlc-dev/vlc-dev/src/vlc-1.2.0-pre3/modules/demux; /bin/sh /tmp/packerbuild-0/vlc-dev/vlc-dev/src/vlc-1.2.0-pre3/libtool  --silent --tag CC --mode=relink gcc -std=gnu99 -march=i686 -mtune=generic -O2 -pipe -fstack-protector --param=ssp-buffer-size=4 -D_FORTIFY_SOURCE=2 -Wall -Wextra -Wsign-compare -Wundef -Wpointer-arith -Wbad-function-cast -Wwrite-strings -Wmissing-prototypes -Wvolatile-register-var -Werror-implicit-function-declaration -fvisibility=hidden -ffast-math -funroll-loops -fomit-frame-pointer -mtune=pentium2 -rpath /usr/lib/vlc/plugins/demux -avoid-version -module -export-symbols-regex "^vlc_entry" -shrext .so -no-undefined -Wl,-O1,--sort-common,--as-needed,-z,relro,--hash-style=gnu -o libdemux_stl_plugin.la -rpath /usr/lib/vlc/plugins/demux libdemux_stl_plugin_la-stl.lo ../../src/libvlccore.la ../../compat/libcompat.la -lpthread -inst-prefix-dir /tmp/packerbuild-0/vlc-dev/vlc-dev/pkg/)
libtool: install: /bin/install -c .libs/libdemux_stl_plugin.soT /tmp/packerbuild-0/vlc-dev/vlc-dev/pkg//usr/lib/vlc/plugins/demux/libdemux_stl_plugin.so
libtool: install: /bin/install -c .libs/libdemux_stl_plugin.lai /tmp/packerbuild-0/vlc-dev/vlc-dev/pkg//usr/lib/vlc/plugins/demux/libdemux_stl_plugin.la
libtool: install: warning: relinking `libts_plugin.la'
libtool: install: (cd /tmp/packerbuild-0/vlc-dev/vlc-dev/src/vlc-1.2.0-pre3/modules/demux; /bin/sh /tmp/packerbuild-0/vlc-dev/vlc-dev/src/vlc-1.2.0-pre3/libtool  --silent --tag CC --mode=relink gcc -std=gnu99 -march=i686 -mtune=generic -O2 -pipe -fstack-protector --param=ssp-buffer-size=4 -D_FORTIFY_SOURCE=2 -Wall -Wextra -Wsign-compare -Wundef -Wpointer-arith -Wbad-function-cast -Wwrite-strings -Wmissing-prototypes -Wvolatile-register-var -Werror-implicit-function-declaration -fvisibility=hidden -ffast-math -funroll-loops -fomit-frame-pointer -mtune=pentium2 -rpath /usr/lib/vlc/plugins/demux -avoid-version -module -export-symbols-regex "^vlc_entry" -shrext .so -no-undefined -Wl,-O1,--sort-common,--as-needed,-z,relro,--hash-style=gnu -o libts_plugin.la -rpath /usr/lib/vlc/plugins/demux libts_plugin_la-ts.lo libts_plugin_la-csa.lo ../../src/libvlccore.la ../../compat/libcompat.la -lpthread -ldvbpsi -inst-prefix-dir /tmp/packerbuild-0/vlc-dev/vlc-dev/pkg/)
libtool: install: /bin/install -c .libs/libts_plugin.soT /tmp/packerbuild-0/vlc-dev/vlc-dev/pkg//usr/lib/vlc/plugins/demux/libts_plugin.so
/bin/install: writing `/tmp/packerbuild-0/vlc-dev/vlc-dev/pkg//usr/lib/vlc/plugins/demux/libts_plugin.so': No space left on device
/bin/install: failed to extend `/tmp/packerbuild-0/vlc-dev/vlc-dev/pkg//usr/lib/vlc/plugins/demux/libts_plugin.so': No space left on device
make[6]: *** [install-libvlcLTLIBRARIES] Error 1
make[6]: Leaving directory `/tmp/packerbuild-0/vlc-dev/vlc-dev/src/vlc-1.2.0-pre3/modules/demux'
make[5]: *** [install-am] Error 2
make[5]: Leaving directory `/tmp/packerbuild-0/vlc-dev/vlc-dev/src/vlc-1.2.0-pre3/modules/demux'
make[4]: *** [install-recursive] Error 1
make[4]: Leaving directory `/tmp/packerbuild-0/vlc-dev/vlc-dev/src/vlc-1.2.0-pre3/modules/demux'
make[3]: *** [install] Error 2
make[3]: Leaving directory `/tmp/packerbuild-0/vlc-dev/vlc-dev/src/vlc-1.2.0-pre3/modules/demux'
make[2]: *** [install-recursive] Error 1
make[2]: Leaving directory `/tmp/packerbuild-0/vlc-dev/vlc-dev/src/vlc-1.2.0-pre3/modules'
make[1]: *** [install-recursive] Error 1
make[1]: Leaving directory `/tmp/packerbuild-0/vlc-dev/vlc-dev/src/vlc-1.2.0-pre3'
make: *** [install] Error 2
==> ERROR: A failure occurred in package().
    Aborting...
The build failed.

what's going on people?

DarkSniper · 2012-01-06 18:20:06

Same issue as with chromium.
/bin/install: writing `/tmp/packerbuild-0/vlc-dev/vlc-dev/pkg//usr/lib/vlc/plugins/demux/libts_plugin.so': No space left on device
/bin/install: failed to extend `/tmp/packerbuild-0/vlc-dev/vlc-dev/pkg//usr/lib/vlc/plugins/demux/libts_plugin.so': No space left on device

If you're wanting to build these large packages, you could consider moving /tmp back to your hard drive. 246M of /tmp is adequate for most smaller aur packages, but simply won't cut it for bigger things.

Last edited by DarkSniper (2012-01-06 18:20:24)

1archgamenon2 · 2012-01-06 19:11:59

DarkSniper wrote:

If you're wanting to build these large packages, you could consider moving /tmp back to your hard drive

How homie? I just have 512mb ram!

DarkSniper · 2012-01-06 20:20:41

If I remember correctly, /tmp is mounted to tmpfs by default if you use the Arch installer. This gives you 50% of your usable ram as /tmp space if you don't specify the "size" option.
While tmpfs is a great thing, it usually doesn't work too well with lower-ram computers on which you need to compile big programs. I personally haven't been able to get away with using it on any of my machines that have less than 4 gigs of RAM.
While not an ideal solution, you could comment out the line mounting your /tmp space as tmpfs in your /etc/fstab, which would put /tmp on your root partition instead. However, it's usually a better practice to put /tmp on a separate partition [if your setup allows for it].

1archgamenon2 · 2012-01-06 22:55:01

DarkSniper wrote:

you could comment out the line mounting your /tmp space as tmpfs in your /etc/fstab

U rock dude!

karol · 2012-01-06 22:58:30

You can tell makepkg, yaourt etc. to compile somewhere else, not in /tmp. I have 512 MB of RAM and I don't have any problems building stuff (unless the PKGBUILD is broken ;P)
makepkg.conf:

#-- Specify a directory for package building.
#BUILDDIR=/tmp/makepkg
BUILDDIR=/home/karol/makepkg

DarkSniper · 2012-01-06 23:20:55

karol wrote:

You can tell makepkg, yaourt etc. to compile somewhere else, not in /tmp. I have 512 MB of RAM and I don't have any problems building stuff (unless the PKGBUILD is broken ;P)
makepkg.conf:
#-- Specify a directory for package building.
#BUILDDIR=/tmp/makepkg
BUILDDIR=/home/karol/makepkg

I was thinking that this was possible, but I couldn't find that option anywhere in the makepkg.conf man page or the wiki page for makepkg. Just wondering, where did you find out how to do that?

@1archgamenon2: It's definitely a better idea to do something like this than to just move your whole /tmp to your HDD.

Last edited by DarkSniper (2012-01-06 23:22:30)

karol · 2012-01-06 23:26:44

It is in the man page - with an important note:

man makepkg.conf wrote:

BUILDDIR="/path/to/folder"
If this value is not set, packages will by default be built in
subdirectories of the directory that makepkg is called from. This
option allows setting the build location to another folder.
Incorrect use of $startdir in a PKGBUILD may cause building with
this option to fail.

Emphasis mine - that was what I was alluding to when I wrote

karol wrote:

I don't have any problems building stuff (unless the PKGBUILD is broken ;P)

packer can use your default makepkg.conf or some alternative one. The choices are there, 1archgamenon2, you just need to get to know your tools.

Arch Linux

#1 2012-01-02 22:41:00

[SOLVED] ERROR: Failed to extract chromium-17...

#2 2012-01-03 04:18:32

Re: [SOLVED] ERROR: Failed to extract chromium-17...

#3 2012-01-03 11:44:42

Re: [SOLVED] ERROR: Failed to extract chromium-17...

#4 2012-01-03 19:18:49

Re: [SOLVED] ERROR: Failed to extract chromium-17...

#5 2012-01-03 19:27:13

Re: [SOLVED] ERROR: Failed to extract chromium-17...

#6 2012-01-04 16:44:48

Re: [SOLVED] ERROR: Failed to extract chromium-17...

#7 2012-01-05 04:21:08

Re: [SOLVED] ERROR: Failed to extract chromium-17...

#8 2012-01-05 14:02:01

Re: [SOLVED] ERROR: Failed to extract chromium-17...

#9 2012-01-05 18:32:11

Re: [SOLVED] ERROR: Failed to extract chromium-17...

#10 2012-01-05 21:03:16

Re: [SOLVED] ERROR: Failed to extract chromium-17...

#11 2012-01-06 16:27:01

Re: [SOLVED] ERROR: Failed to extract chromium-17...

#12 2012-01-06 18:20:06

Re: [SOLVED] ERROR: Failed to extract chromium-17...

#13 2012-01-06 19:11:59

Re: [SOLVED] ERROR: Failed to extract chromium-17...

#14 2012-01-06 20:20:41

Re: [SOLVED] ERROR: Failed to extract chromium-17...

#15 2012-01-06 22:55:01

Re: [SOLVED] ERROR: Failed to extract chromium-17...

#16 2012-01-06 22:58:30

Re: [SOLVED] ERROR: Failed to extract chromium-17...

#17 2012-01-06 23:20:55

Re: [SOLVED] ERROR: Failed to extract chromium-17...

#18 2012-01-06 23:26:44

Re: [SOLVED] ERROR: Failed to extract chromium-17...

Board footer