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

Client Compiles fine but install throws Error 1 #1761

Closed
Saegusae opened this issue Dec 28, 2016 · 5 comments
Closed

Client Compiles fine but install throws Error 1 #1761

Saegusae opened this issue Dec 28, 2016 · 5 comments

Comments

@Saegusae
Copy link

System Information

MultiMC version: git-develop

Operating System: Ubuntu GNOME 16.10

Summary of the issue or suggestion:

The client cloned from the latest develop branch compiles fine but the install always throws an error ID 1 with the description "fixup_bundle: not a valid bundle"

What should happen:

The client should install fine

Steps to reproduce the issue (Add more if needed):

  1. Do the steps as stated in BUILD.md

  2. Try to install the compiled code

  3. ???

  4. Profit.

Suspected cause:

Something wrong with my system setup, still worth mentioning tho.

Logs/Screenshots:

[100%] Built target MultiMC
Install the project...
-- Install configuration: ""
-- Installing: /home/saegusa/MultiMC/install/bin/MultiMC
-- Removed runtime path from "/home/saegusa/MultiMC/install/bin/MultiMC"
-- Up-to-date: /home/saegusa/MultiMC/install/./MultiMC
-- Installing: /home/saegusa/MultiMC/install/bin/jars/JavaCheck.jar
-- Installing: /home/saegusa/MultiMC/install/bin/jars/NewLaunch.jar
-- Up-to-date: /home/saegusa/MultiMC/install/plugins/imageformats
-- Up-to-date: /home/saegusa/MultiMC/install/plugins/imageformats/libqjpeg.so
-- Up-to-date: /home/saegusa/MultiMC/install/plugins/imageformats/libqico.so
-- Up-to-date: /home/saegusa/MultiMC/install/plugins/imageformats/libqsvg.so
-- Up-to-date: /home/saegusa/MultiMC/install/plugins/imageformats/libqgif.so
-- Up-to-date: /home/saegusa/MultiMC/install/plugins/iconengines
-- Up-to-date: /home/saegusa/MultiMC/install/plugins/iconengines/libqsvgicon.so
-- Up-to-date: /home/saegusa/MultiMC/install/plugins/platforms
-- Up-to-date: /home/saegusa/MultiMC/install/plugins/platforms/libqxcb.so
-- Up-to-date: /home/saegusa/MultiMC/install/plugins/platforms/libqeglfs.so
-- fixup_bundle
--   app='/home/saegusa/MultiMC/install/bin/MultiMC'
--   libs='/home/saegusa/MultiMC/install/plugins/platforms/libqxcb.so;/home/saegusa/MultiMC/install/plugins/platforms/libqeglfs.so;/home/saegusa/MultiMC/install/plugins/iconengines/libqsvgicon.so;/home/saegusa/MultiMC/install/plugins/imageformats/libqjpeg.so;/home/saegusa/MultiMC/install/plugins/imageformats/libqico.so;/home/saegusa/MultiMC/install/plugins/imageformats/libqsvg.so;/home/saegusa/MultiMC/install/plugins/imageformats/libqgif.so'
--   dirs='/usr/lib/x86_64-linux-gnu;/usr/lib/x86_64-linux-gnu/qt5/libexec;/home/saegusa/MultiMC/build;/home/saegusa/MultiMC/build'
-- warning: *NOT* handled - not .app dir, not executable file...
CMake Error at /home/saegusa/MultiMC/src/cmake/BundleUtilities.cmake:668 (message):
  error: fixup_bundle: not a valid bundle
Call Stack (most recent call first):
  application/install_prereqs.cmake:24 (fixup_bundle)
  application/cmake_install.cmake:84 (include)
  cmake_install.cmake:49 (include)


Makefile:85: recipe for target 'install' failed
make: *** [install] Error 1

@nikhiljha
Copy link

What version of cmake do you have? Try updating it and try to build again with latest source.

@Saegusae
Copy link
Author

I tried with both cmake 3.2.2 and cmake 3.7,1 though

@Arzte
Copy link
Member

Arzte commented Jan 3, 2017

Maybe this has some hold as to whats going on?
warning: *NOT* handled - not .app dir, not executable file...
Maybe it wants to be on windows/OSX and doesn't like linux. (if this is the case, why? It should install just fine on linux.) Will try to investigate once I get home.

@bearbin
Copy link

bearbin commented Aug 9, 2017

#1780 duplicates this issue. Perhaps this issue should be closed, as the other one has a fix.

@Arzte
Copy link
Member

Arzte commented Aug 26, 2017

Yep, that issue appears to be a dupe of this one, however seeing how that issue seems to figured out the cause I'll close this in favor of #1780

TD;LR Go to #1780 if your still experiencing this issue.

@Arzte Arzte closed this as completed Aug 26, 2017
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

4 participants