-
Notifications
You must be signed in to change notification settings - Fork 26
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
Many errors while building the toolchain #4
Comments
Can you specify which version of Debian you're hitting the issue on? |
Of course. These are the full details of my virtual machine configuration: memory: 2.0 GiB The iso I used to install Debian was the debian-9.5.0-amd64-netinst.iso Prior to build the tool chain, I made the pre-requisite. I precise that I had to add the small fix suggested by ozzyyzzo4096 apt-get install gcc curl |
Hey thx for your report, I indeed found a bug during the end of the devkit compilation, that one is fixed in 565f7b6 However when I tested on a pristine Debian Stretch set up with virt-builder, I could not reproduce your specific error during gcc compilation, nor the missing dependency :/
Before compiling the entire devkit, I made sure to update to the very latest Debian packages:
Could you maybe try with that and make sure you have installed all the prerequisites? Then in the ngdevkit directory:
If you still have the issue, I'd appreciate to see the entire compilation log to spot the first error. |
Oh, when using the image you mentioned, I'm apparently hitting different mirrors and I can see now that package imagemagick is deprecated in favor of graphicsmagick and graphicsmagick-imagemagick-compat. I'll update README.md accordingly shortly. |
I decided to completly override my Debian installation so I am ready to restart from scratch. I will try again after your update. |
OK so, it turns out that graphicsmagick not really replaces imagemagick, it only "provides" (in the packaging sense) it via graphicsmagick-imagemagick-compat. imagemagick for some reason seems to be needed by one of the build dependencies that are being installed in the README. So in 8a81c19, I make sure to install it before everything else and graphicsmagick-imagemagick-compat is not required anymore. Could you update to this revision and try to rebuild the entire toolkit now?
I've used the same apt mirrors as your Debian image, and installing the deps in that new order seems to be sufficient for the building process to finish successfully. |
The result of apt-get build-dep sdcc (in pre-requisite) is the following: **Reading package lists... Done The following packages have unmet dependencies: Is it good sign ? I have stopped and will continue after your opinion. |
Hmm, I have no idea why the build succeeded on my VM and not on yours, but I know why apt wants to install graphicsmagick dependencies:
In fact, there are the only dependencies that we need to rebuild sdcc for ngdevkit are the 'Build-Depends" ones, we can get rid of the "Build-Depends-Indep" ones. So, I think you can fix your problem by replacing "apt-get build-dep sdcc" with "apt-get build-dep --arch-only sdcc". I just did that on a Debian 9 for WSL (windows 10), and the dependencies installed fine and the build process finished as expected. Could you give it a try? If that fixes the problem I'll push a commit with that change in the various README files. |
Yes it works with well "apt-get build-dep --arch-only sdcc" |
Pushed the according doc update, thanks for reporting the issue. |
Hi.
Using Debian running in a virtualbox, I face many issues when building the toolchain:
[...]
Makefile:11025: recipe for target 'install-target-libgcc' failed
make[2]: *** [install-target-libgcc] Error 2
make[2]: Leaving directory '/home/cedric/ngdevkit-master/build/nggcc'
Makefile:2249: recipe for target 'install' failed
make[1]: *** [install] Error 2
make[1]: Leaving directory '/home/cedric/ngdevkit-master/build/nggcc'
Makefile:125: recipe for target 'build/nggcc' failed
make: *** [build/nggcc] Error 2
I am not an experimented Linux user.
The text was updated successfully, but these errors were encountered: