When I do make of buildroot appears this error
make: *** [package/pkg-generic.mk:293: /home/vitor/buildroots/buildroot/output/build/host-gcc-final-11.3.0/.stamp_built]
Error 2
Does anyone know the solution?
Thanks already for the time
Note: The first time I have do buildroot it worked fine, but for an work I needed to change some files and since that stop working, so I deleted that buildroot and tried to do a new ones and always appear this error.
Recommandation: don't use the current "master" of Buildroot if you're new to Buildroot, but instead use a release tag. As Arnout said, you did not post enough lines of the error to really know, but based on the package that failed I suspect you're encountering one of the issues we've had with the update of glibc to version 2.36, which is not yet part of any Buildroot stable release.
Use Buildroot 2022.02 or 2022.08, but not Buildroot master if you're interested in having something that "works" :-)
Related
This is my first time doing this. I need to recompile the kernel to change some settings to get a better performance out of a specific application I will run on this machine.
I followed this tutorial step by step and changed my settings in make menucofig.
After trying to build the rpm, I get the following error log: pastebin
This is really confusing as I haven't made any major changes to the config, which makes me thing there's something wrong with the tutorial. Will post all changes in menuconfig if requested.
Very often we need to install software from its source code. Most of the time I just hit "make world" or "make all" then it will work like a charm. But some other time we see make errors, and we need to install other packages in order to let the make go through. This is particularly a problem for compiling low-level systems, such as a Linux kernel or Xen hypervisor.
I have one experience with Xen 3.4. Maybe it has been documented in some corner documents, but it depends on udev-125 to work properly. The weird thing is it functions well most of the time when udev version is 160+, it only breaks in certain cases! It took me a few MONTHS to find out it was because of the wrong udev version!
To make developers' life easier, when a source code is made successfully in one machine, is there some tools to record the list of packages and versions of that machine? Such a 'snapshot' should be shipped with the source code as well, so that when someone meets the make error they at least have a successful 'snapshot' for reference.
Is there such a tool already?
If your software depends on a specific version of a dependency, you should write a check for your configure script/cmakefile/etc. that tests the version of the dependency and bails out if the wrong version was found.
Comparing the output of config.log (a file created by a configure script) can also help diagnose problems like you encountered.
I am working on a project that uses Cinder for graphics, and for image loading, we are using FreeImage mainly for loading HDR images.
It is all working fine under windows, but now I am trying to build an OSX version I am hitting a snag.
First I tried to download and build FreeImage, but the makefiles are hopelessly outdated and do not work. I managed to fudge them and build the library, but when adding to xcode it didn't seem to link. The error was that the library was ignored because it was built with a different architecture. (I couldn't figure out how to fix this, but it is an option to go back to if all else fails).
Anyway, my next attempt was to use macports to install and build FreeImage. This all worked without error and I was able to include the library in my project.
However, the problem now it that I get many std linking errors. After searching around, it seems my problem is that freeimage was built with libstdc++, but cinder complains if I dont build my project with C++11.
So, is there any way of fixing this? Can I modify the make files macports uses to build freeimage? Or is there some other sneaky way? Any suggestions appreciated.
Sorry if this question is a bit parochial, but in my searches I have seen others with similar problems (but unfortunately few answers).
When trying to install glibc-2.15 on Centos-5(Kernel version 2.6.18-238.9.1.el5, gcc-4.6.3), make install step fails with the error message cannot remove/var/db/Makefile'`
The configure command is /data1/downloads/gcc/utils/glibc-2.15/configure --prefix=/data1/downloads/gcc/utils/binutils
glibc-2.16+ solves this problem but I'm restricted by the kernel version. To fix this problem I made changes to glibc-2.15/(config*in|Makeconfig) as mentioned in http://sourceware.org/ml/libc-alpha/2012-06/msg00632.html but this results in configure error(caught signal 2).
Any pointers to help resolve the issue is much appreciated.
Newer Glibc should work with older kernels, shouldn't it? It just disables the optional features. Of course, that probably only goes so far ....
Anyway, the magic build option will be something like this:
/path/to/source/configure --enable-kernel=2.6.18 ...blah..
EDIT: It seems like no one knows the answer. New question: can anyone post a step by step tutorial how to create a mac project manually?? The answer to that question will of course get the "tick" as accepted answer..
I have the latest cocos2d version installed.
I made a new mac template and without changing anything I just build it. But I get 26 errors and 7 warnings.
The most important one (I think) is this one:
ld: warning: ignoring file /Developer/SDKs/MacOSX10.7.sdk/Library/Frameworks//OpenAL.framework/OpenAL, file was built for unsupported file format which is not the architecture being linked (x86_64)
I get lots of CDSoundEngine and audio stuff errors.
In the warning I copied above...before the "OpenAL.framework" is a double backslash..strange.
I tried to re-add the OpenAL framework but I get the same error.
I also tried to make a new one but I get the same errors..
I also reinstalled cocos2d..didn't work either.
This only happens with the mac templates...
Does anyone know how to fix this?
Edit: (Added screenshot)
link to screenshot: http://dl.dropbox.com/u/3951219/screenshot_mac_template_error.png
http://dl.dropbox.com/u/3951219/screenshot_mac_template_error.png
A tad late, but I just had the same problem.
For your original question, try this answer here...
My OpenAL Framework is broken
Oh, and btw, the // is normal. It happens when a program opens a directory like {Frameworks}/OpenAL.framework, and "Frameworks" is /Developer/SDKs/MacOSX10.7.sdk/Library/Frameworks/. The OS takes a // as a /