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

make install fails (on fedora26) #629

Closed
DaanHoogland opened this issue Feb 6, 2018 · 14 comments
Closed

make install fails (on fedora26) #629

DaanHoogland opened this issue Feb 6, 2018 · 14 comments

Comments

@DaanHoogland
Copy link
Contributor

I'm a lurking user that has remacs as his standard emacs, on macos and fedora mostly. once in a while i pretend to develop and i have to re-install on my fedora, as I did last weekend. however the make install step failed with "error[E0554]: #![feature] may not be used on the stable release channel" I am using nightly but maybe not for one of the tools?
$ src/remacs -Q
starts a nice windows with a over featured editor but
$ sudo make install
gave me a very ugly

error[E0554]: #![feature] may not be used on the stable release channel
 --> /home/dahn/prj/remacs/rust_src/remacs-sys/lib.rs:1:1
  |
1 | #![feature(const_size_of)]
  | ^^^^^^^^^^^^^^^^^^^^^^^^^^

error: aborting due to previous error

error: Could not compile `remacs-sys`.
warning: build failed, waiting for other jobs to finish...
error: build failed
make[1]: *** [Makefile:610: ../rust_src/target/release/libremacs_lib.a] Error 101

make[1]:

 Leaving directory '/home/dahn/prj/remacs/src'
make: *** [Makefile:426: src] Error 2

I realize the problem might be between chair and keyboard, if so please help. it seems strange to me that a compilation error occurs during install and not during normal build.

@shaleh shaleh self-assigned this Feb 6, 2018
@shaleh
Copy link
Collaborator

shaleh commented Feb 6, 2018

I am looking at this currently.

@DaanHoogland
Copy link
Contributor Author

I may well close this myself soon; rustup installs the nightly version for the current user not available under sudo, which in turn is needed to install. remains the question why compile is needed during install.

@DaanHoogland
Copy link
Contributor Author

thanks @shaleh , I just did a sudo make and that didn't go as well as make so i tried sudo rustc --version showing part of the problem

@shaleh
Copy link
Collaborator

shaleh commented Feb 6, 2018

AH. yes, the annoyance of per user Rust toolchain setup.

Once you are satisfied with a working solution would you mind submitting a PR for updating the documentation?

@shaleh shaleh removed their assignment Feb 6, 2018
@DaanHoogland
Copy link
Contributor Author

of course, but can you shine a light as to why make install compiles even when make finished succesfully?

@shaleh
Copy link
Collaborator

shaleh commented Feb 6, 2018

No, I cannot. I was just about to look at that.

@shaleh
Copy link
Collaborator

shaleh commented Feb 6, 2018

hmmm.

If I run it like this (as me):

$ ./configure --prefix=~/tmp/remacs-install --enable-rust-debug
$ make -j8
$ make install  # works because it is my path so permissions are OK

I do not see a second compilation. However....

$ make -j8
$ sudo su -
$ cd back to repo
$ PATH=~me/.cargo/bin:$PATH make install

Now I do see a second compilation as root.

@shaleh
Copy link
Collaborator

shaleh commented Feb 6, 2018

I believe this is an issue with cargo. If you run both the build and the install as the same user the compile does not repeat. If you run the compile as a user and the install as root then cargo goes back through to ensure the dependencies are right and this can trigger a relink of the build.

@shaleh
Copy link
Collaborator

shaleh commented Feb 6, 2018

It looks like build and test as a user. Then when ready to install it build and install as root.

If you are the only user on the system, consider installing it into ~/opt (or ~/local) and adding that path to your PATH.

@DaanHoogland
Copy link
Contributor Author

ok, this is still not nice but i think we should close this with a enterprisial "won't fix".

@DaanHoogland
Copy link
Contributor Author

and thanks for the trouble @shaleh

@shaleh
Copy link
Collaborator

shaleh commented Feb 6, 2018

@DaanHoogland are you still going to submit a doc update?

@DaanHoogland
Copy link
Contributor Author

Yes @shaleh , i will tonight. What I can think of now are teh readme and the install file. Any other places this needs pointing out?

@shaleh
Copy link
Collaborator

shaleh commented Feb 7, 2018

That should cover it.

👍

DaanHoogland pushed a commit to DaanHoogland/remacs that referenced this issue Feb 7, 2018
DaanHoogland pushed a commit to DaanHoogland/remacs that referenced this issue Feb 7, 2018
shaleh pushed a commit to shaleh/remacs that referenced this issue Feb 8, 2018
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

2 participants