Try install Atom on archlinux (script/build) err

[e2fletcher]

atom (0a6da38)]$ script/build                                                           
Node: v0.12.7
npm: v2.14.0
Installing build modules...
Installing apm...
Native thread-sleep not available.
This will result in much slower performance, but it will still work.
You should re-install spawn-sync or upgrade to the lastest version of node if possible.
Check /home/fletcher/atom/apm/node_modules/atom-package-manager/node_modules/yargs/node_modules/os-locale/node_modules/exec-file-sync/node_modules/spawn-sync/error.log for more details
Native thread-sleep not available.
This will result in much slower performance, but it will still work.
You should re-install spawn-sync or upgrade to the lastest version of node if possible.
Check /home/fletcher/atom/apm/node_modules/atom-package-manager/node_modules/yargs/node_modules/os-locale/node_modules/exec-file-sync/node_modules/spawn-sync/error.log for more details
Installing modules ✓
Installing atom-dark-syntax@0.27.0 ✓                                                                                    
Installing atom-dark-ui@0.50.0 
dns.js:121
        callback(null, addresses[0], addresses[0].indexOf(':') >= 0 ? 6 : 4);

[izuzak]

Huh, that's interesting. Is that the full output that you get? If you run script/build again do you get the same output, i.e. does the build stop at the same place? Do you get more information when you run script/build --verbose?

Also cc @kevinsawicki

[kevinsawicki]

dns.js:121
       callback(null, addresses[0], addresses[0].indexOf(':') >= 0 ? 6 : 4);

Whoa, never seen this before.

[izuzak]

This might be a node issue, see: nodejs/node-v0.x-archive#25327 and nodejs/node-v0.x-archive#8698

[ghost]

FWIW, the aur package https://aur.archlinux.org/packages/atom-editor/ just finished building without errors for me without any modification to the pkgbuild.

My configuration:

4.1.5-1-ARCH #1 SMP PREEMPT Tue Aug 11 15:41:14 CEST 2015 x86_64 GNU/Linux
Node: v0.12.7
npm: 2.13.5
atom-editor: 1.0.7-2

I did get a spawn-sync warning, but I don't think that its related to this.

[klardotsh]

I get OP's bug with node 0.12.7, npm 2.14.0, and atom-editor 1.0.7-2 PKGBUILD. Uname: 4.2.0-rc8-mainline #1 SMP PREEMPT Mon Aug 24 12:13:13 CEST 2015 x86_64 GNU/Linux

[e2fletcher]

script/build --verbose
Node: v0.12.7
npm: v2.14.1
Installing build modules...
Installing apm...
Installing modules ✓
Installing atom-dark-syntax@0.27.0 ✓
Installing atom-dark-ui@0.51.0 
dns.js:121
        callback(null, addresses[0], addresses[0].indexOf(':') >= 0 ? 6 : 4);
                                                  ^
TypeError: Cannot call method 'indexOf' of undefined
    at Object.onanswer [as oncomplete] (dns.js:121:51)

Otros datos

atom (master)]$ npm version
{ atom: '1.0.12',
  npm: '2.14.1',
  http_parser: '2.3',
  modules: '14',
  node: '0.12.7',
  openssl: '1.0.2d',
  uv: '1.6.1',
  v8: '3.28.71.19',
  zlib: '1.2.8' }

atom (master)]$ uname -a
Linux coconut 4.1.6-1-ARCH #1 SMP PREEMPT Mon Aug 17 09:07:24 CEST 2015 i686 GNU/Linux

[CraZySacX]

Your version of npm looks suspicious (2.14.1). I believe I had to uninstall the npm package and let atom use it's own version (2.13.3).

remote: Counting objects: 75, done.
remote: Compressing objects: 100% (74/74), done.
remote: Total 75 (delta 43), reused 0 (delta 0), pack-reused 0
Unpacking objects: 100% (75/75), done.
From github.com:atom/atom
   daa38b2..4d77c92  master     -> origin/master
 * [new branch]      ns-remove-space-pen-shims -> origin/ns-remove-space-pen-shims
Updating daa38b2..4d77c92
Fast-forward
 spec/selection-spec.coffee   | 13 +++++++++++++
 spec/text-editor-spec.coffee |  9 ++++++++-
 src/selection.coffee         | 10 +++++++---
 3 files changed, 28 insertions(+), 4 deletions(-)
Node: v0.12.7
npm: v2.13.3
Installing build modules...
Installing apm...
Installing modules ✓
Deduping modules ✓
Running "download-atom-shell" task

Running "download-atom-shell-chromedriver" task

Running "build" task

Running "babel:dist" (babel) task

Running "coffee:glob_to_multiple" (coffee) task
>> 335 files created.

Running "prebuild-less:src" (prebuild-less) task

Running "cson:glob_to_multiple" (cson) task
>> 172 files compiled to JSON.

Running "peg:glob_to_multiple" (peg) task

Running "generate-license:save" (generate-license) task

Running "generate-module-cache" task

Running "compile-packages-slug" task

Running "set-version" task

Running "generate-asar" task
Done, without errors.
Running "install" task

jozias@jozias-aw-vm.ozias.net ~ $ uname -a
Linux jozias-aw-vm.ozias.net 4.1.6-1-ARCH #1 SMP PREEMPT Mon Aug 17 08:52:28 CEST 2015 x86_64 GNU/Linux

[CraZySacX]

Well now I'm baffled. I do have 2.14.1 installed, but it appears the log output from the build script is saying 2.13.3.

jozias@jozias-aw-vm.ozias.net ~/p/atom (master|) $ which npm
/usr/bin/npm
jozias@jozias-aw-vm.ozias.net ~/p/atom (master|) $ npm version
{ atom: '1.0.12',
  npm: '2.14.1',
  http_parser: '2.3',
  modules: '14',
  node: '0.12.7',
  openssl: '1.0.2d',
  uv: '1.6.1',
  v8: '3.28.71.19',
  zlib: '1.2.8' }
jozias@jozias-aw-vm.ozias.net ~/p/atom (master|) $ script/build --build-dir /home/jozias/projects/atom-build
Node: v0.12.7
npm: v2.13.3
Installing build modules...
Installing apm...
Installing modules ✓
Deduping modules ✓
Running "download-atom-shell" task

Running "download-atom-shell-chromedriver" task

Running "build" task

Running "babel:dist" (babel) task

Running "coffee:glob_to_multiple" (coffee) task

As a side note, you should probably specify a build-dir. By default, atom installs in the /tmp directory and Arch cleans out the directory on restart by default.

[e2fletcher]

I'm not installing atom from aur. but try and produced the same error

 yaourt -S atom-editor --tmp ./tmp --noconfirm

==> Descargando PKGBUILD para atom-editor desde AUR...
x .SRCINFO
x PKGBUILD
x atom-python.patch
Comment by toddpi314  (2015-08-12 14:18)
There are a few people reporting successful pacman install with a error at runtime:
/usr/share/atom/atom: error while loading shared libraries: libchromiumcontent.so: cannot open shared object file: No such file or directory

If you hit this, looks like the short term resolve is: 
sudo chmod +r -R /usr/share/atom/atom

Reference: https://github.com/atom/atom/issues/6633

Comment by toddpi314  (2015-08-13 18:55)
The update today made the "/usr/share/atom/atom: error while loading shared libraries: libchromiumcontent.so: cannot open shared object file: No such file or directory" issue pop back up.

Executing the following fixed:
sudo chmod +r -R /usr/share/atom

Comment by razvanz  (2015-08-27 20:05)
The package is failing to build due to an outdate build dependency. With the fix described described in issue #8525 I managed to succesfuly build it. Issue link: https://github.com/atom/atom/issues/8525

Comment by johanzebin  (2015-09-02 14:54)
I think there's a typo in the version number: It should NOT read v1.1.0 but v1.0.10?

Comment by jugs  (2015-09-02 14:55)
yes you're right sorry... will correct

atom-editor 1.0.11-1  (2015-09-02 22:55)
(Paquete sin soporte: ¡podría ser peligroso!)
==> dependencias de atom-editor:
 - alsa-lib (ya instalado)
 - gconf (ya instalado)
 - gtk2 (ya instalado)
 - libgnome-keyring (ya instalado)
 - libnotify (ya instalado)
 - libxtst (ya instalado)
 - nodejs (ya instalado)
 - nss (ya instalado)
 - python2 (ya instalado)
 - git (ya instalado)
 - npm (ya instalado)


==> Continuar compilando atom-editor? [S/n]
==> ---------------------------------------
==> 
==> Compilando e instalando el paquete
==> Creando el paquete: atom-editor 1.0.11-1 (jue sep  3 10:25:40 VET 2015)
==> Comprobando dependencias mientras se ejecuta...
==> Comprobando dependencias mientras se compila...
==> Recibiendo las fuentes...
  -> Descargando v1.0.11.tar.gz...
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
100   118    0   118    0     0     63      0 --:--:--  0:00:01 --:--:--    63
100 4201k  100 4201k    0     0  74127      0  0:00:58  0:00:58 --:--:--  106k
  -> atom-python.patch ha sido encontrado 
==> Validando las fuentes con sha256sums...
    v1.0.11.tar.gz ... Aprobado
    atom-python.patch ... Aprobado
==> Extrayendo las fuentes...
  -> Extrayendo v1.0.11.tar.gz con bsdtar
==> Iniciando prepare()...
patching file atom.sh
==> Iniciando build()...
Node: v0.12.7
npm: v2.14.1
Installing build modules...
Installing apm...
Installing modules ✓
Installing atom-dark-syntax@0.27.0 ✓                                                                                    
Installing atom-dark-ui@0.51.0 
dns.js:121
        callback(null, addresses[0], addresses[0].indexOf(':') >= 0 ? 6 : 4);
                                                  ^
TypeError: Cannot call method 'indexOf' of undefined
    at Object.onanswer [as oncomplete] (dns.js:121:51)
==> ERROR: Se produjo un fallo en build().
    Cancelando...
==> ERROR: Makepkg no ha podido compilar atom-editor.
==> ¿Reiniciar la compilación de atom-editor? [s/N]
==> -----------------------------------------------

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[lock]

This issue has been automatically locked since there has not been any recent activity after it was closed. If you can still reproduce this issue in Safe Mode then please open a new issue and fill out the entire issue template to ensure that we have enough information to address your issue. Thanks!