Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

0.26.1 compilation fails at Arch Linux #6672

Closed
anatol opened this issue Sep 6, 2018 · 8 comments
Closed

0.26.1 compilation fails at Arch Linux #6672

anatol opened this issue Sep 6, 2018 · 8 comments

Comments

@anatol
Copy link
Contributor

anatol commented Sep 6, 2018

Trying to build 0.2.6.1 package in a clear build chroot environment at Arch Linux and I get following failure:

Using /usr/bin/llvm-config [version=6.0.1]
g++ -c -march=x86-64 -mtune=generic -O2 -pipe -fstack-protector-strong -fno-plt  -o src/llvm/ext/llvm_ext.o src/llvm/ext/llvm_ext.cc -I/usr/include -march=x86-64 -mtune=generic -O2 -pipe -fstack-protector-strong -fno-plt -fPIC -fvisibility-inlines-hidden -Werror=date-time -std=c++11 -Wall -W -Wno-unused-parameter -Wwrite-strings -Wcast-qual -Wno-missing-field-initializers -pedantic -Wno-long-long -Wno-maybe-uninitialized -Wdelete-non-virtual-dtor -Wno-comment -ffunction-sections -fdata-sections -O3 -DNDEBUG  -fno-exceptions -D_GNU_SOURCE -D__STDC_CONSTANT_MACROS -D__STDC_FORMAT_MACROS -D__STDC_LIMIT_MACROS
cc -march=x86-64 -mtune=generic -O2 -pipe -fstack-protector-strong -fno-plt -fPIC  -D_FORTIFY_SOURCE=2  -c -o src/ext/sigfault.o src/ext/sigfault.c
ar -rcs src/ext/libcrystal.a src/ext/sigfault.o
./bin/crystal build --release --no-debug --release --link-flags="-Wl,-O1,--sort-common,--as-needed,-z,relro,-z,now"  -o .build/crystal src/compiler/crystal.cr -D without_openssl -D without_zlib
Using /usr/bin/llvm-config [version=6.0.1]
./bin/crystal docs -b https://crystal-lang.org/api/latest src/docs_main.cr
Using compiled compiler at `.build/crystal'
Unhandled exception: fcntl() failed: Bad file descriptor (Errno)
  from ???
  from ???
  from __crystal_main
  from main
  from __libc_start_main
  from _start
  from ???
make: *** [Makefile:97: docs] Error 1
@Timbus
Copy link
Contributor

Timbus commented Sep 6, 2018

Almost definitely a duplicate of #6624
My apologies :(

@bararchy
Copy link
Contributor

bararchy commented Sep 7, 2018

@bcardiff @RX14 this is the official build package for Arch Linux, as long as @anatol fails to build Arch users won't get a new release.

@bararchy
Copy link
Contributor

bararchy commented Sep 7, 2018

@anatol it seems a fix landed in Master, @Timbus asked if you could retest using master branch (or @Timbus can you offer specific commit point?)

I guess we won't get an official 0.26.1 but at least we might get 0.26.2

@anatol
Copy link
Contributor Author

anatol commented Sep 7, 2018

I prefer to test a fix commit alone rather than master with many changes. If the fix is going to work then I can release 0.26.1 package to Arch repos.

@Timbus
Copy link
Contributor

Timbus commented Sep 7, 2018

I guess the fix commit is here: b697de0

You could possibly apply that as a patch, or check it out at that commit. Would recommend you try building master first and making sure it has been fixed.

@anatol
Copy link
Contributor Author

anatol commented Sep 7, 2018

Thanks for the pointer.

master branch builds fine, and 0.26.1 release with the patch above also builds fine. I just pushed 0.26.1 package to Arch [testing] repo. @bararchy please verify that it works as expected.

@bararchy
Copy link
Contributor

bararchy commented Sep 7, 2018

@anatol The testing package works great for me and the team, we tested on 6 different systems and compiled 9 internal + external projects.

@drosehn
Copy link

drosehn commented Sep 7, 2018

FWIW, I'm seeing the same result:

Unhandled exception: fcntl() failed: Bad file descriptor (Errno)
from ???
from ???
from __crystal_main
...etc...

When I tried to build crystal 0.26.1 on macOS 10.11.6 (El Capitan) using homebrew. I have not tried with the fix. (I had not noticed this PR until about 10 minutes ago...).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants