Linux From ScratchThis Forum is for the discussion of LFS.
LFS is a project that provides you with the steps necessary to build your own custom Linux system.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
I installed Gnome on a 4.1 system with no problems. So I know it can work. That said, I'd need to see the rest of make's output before I could tell you whether I can help or not. There should be some indication as to why the compile failed in the previous lines. Go ahead and post it, and I'll see if I can (at least) point you in the right direction.
here's the output (I ran make once, to get rid of any erroneous output and then ran make a second time (as displayed below) so as only to capture any applicable errors).
make all-recursive
make[1]: Entering directory `/home/jason/g-wrap-1.3.4'
Making all in doc
make[2]: Entering directory `/home/jason/g-wrap-1.3.4/doc'
make[2]: Nothing to be done for `all'.
make[2]: Leaving directory `/home/jason/g-wrap-1.3.4/doc'
Making all in rpm
make[2]: Entering directory `/home/jason/g-wrap-1.3.4/rpm'
make[2]: Nothing to be done for `all'.
make[2]: Leaving directory `/home/jason/g-wrap-1.3.4/rpm'
Making all in bin
make[2]: Entering directory `/home/jason/g-wrap-1.3.4/bin'
make[2]: Nothing to be done for `all'.
make[2]: Leaving directory `/home/jason/g-wrap-1.3.4/bin'
Making all in g-wrap
make[2]: Entering directory `/home/jason/g-wrap-1.3.4/g-wrap'
if /bin/sh ../libtool --mode=compile gcc -DHAVE_CONFIG_H -I. -I. -I.. -O2 -g -Wall -Werror -I/usr/include/glib-1.2 -I/usr/lib/glib/include -I/usr/include/glib-1.2 -I/usr/lib/glib/include -g -O2 -I /usr/include -MT gw-standard.lo -MD -MP -MF ".deps/gw-standard.Tpo" \
-c -o gw-standard.lo `test -f 'gw-standard.c' || echo './'`gw-standard.c; \
then mv ".deps/gw-standard.Tpo" ".deps/gw-standard.Plo"; \
else rm -f ".deps/gw-standard.Tpo"; exit 1; \
fi
rm -f .libs/gw-standard.lo
gcc -DHAVE_CONFIG_H -I. -I. -I.. -O2 -g -Wall -Werror -I/usr/include/glib-1.2 -I/usr/lib/glib/include -I/usr/include/glib-1.2 -I/usr/lib/glib/include -g -O2 -I /usr/include -MT gw-standard.lo -MD -MP -MF .deps/gw-standard.Tpo -c gw-standard.c -fPIC -DPIC -o .libs/gw-standard.lo
make[2]: Leaving directory `/home/jason/g-wrap-1.3.4/g-wrap'
make[1]: Leaving directory `/home/jason/g-wrap-1.3.4'
cc1: changing search order for system directory "/usr/include"
cc1: as it has already been specified as a non-system directory
make[2]: *** [gw-standard.lo] Error 1
make[1]: *** [all-recursive] Error 1
make: *** [all] Error 2
I'd be willing to be the glob is failing... Mainly because make returns with an error value of 1, and if you notice, the else clause of that big, honkin' statement says to exit with 1. Now, what is that command trying to do? I have no idea. I'd have to sit for a while to try and decipher it.
In the meantime, do me a favor: wipe out the source tree and give it another try. I'm sure it will fail again, but if it provides any other error messages, it might help shed more light;
yeah wish I knew schema (or is it scheme) programming language, would help in this matter. I'll give it another look see and get back to you. Thanks again for your help.
just think, all this fuss so I can install GNUCash ... nothing else ... just one app.
To be honest, I don't know schema either, but I'm not sure that's what's being used (maybe I'm REALLY showing ignorance there...)
Anyway, something else to try. Execute the command between the "if" and "then" parts of that mega-command. It may provide more information if it is, in fact, failing. Most of the arguments are to add paths to the list of directories to search for includes and preprocessor directives. So the portion of the command to compile looks ok; it's trying to create an object file (gw-standard.lo) from the gw-standard.c file. What I don't know about is what "libtool" does. However, it looks to be a shell script, and you may be able to open it and take a look. So, you could try issuing the compile command itself and see if you get any errors (I'd be willing to bet the problem is in the compile). If the compile works, then you can try the libtool script.
I'll have to take a look at libtool ... I tried the compile command and it ran without a hitch. I could possibly alter the Makefile too ... I've had problems before where something wouldn't compile right off the bat, so I would rerun the Makefile or execute the compile command by hand and reissue 'make' and everything would run fine afterward. I check out libtool and let you know what I find. Thanks again for all your help with this.
Dark_Helmet ... figured it out... take a look at the gcc command it was issuing the '-I /usr/include' is what was causing the compile to fail. Not sure why, I've seen that error message before with no problems, which is why I disregarded it this time however that was the root of the problem, so I edited the Makefile (and two others with the same problem) and away I went.
You're welcome. If that was the cause, then it's likely there was a declaration conflict between different header files the source was including. If it's working well, I wouldn't worry much about it. If it seems flaky, then it might be worth investigating why the "/usr/include" headers create problems.
I'm now compiling GNUCash and all its makefiles are causing complaints until I remove all references to /usr/include ... I'm beginning to think it might be an option that is being passed to gcc ... something that would cause gcc to become so sensitive that if / when /usr/include is added as an Include dir then gcc crashes out. Is there such an option? would make editing these Makefiles much easier.
No option that I'm aware of (I think you can ADD paths; not take them away). Here's a possible solution:
move your /usr/include diretory to /user/include.bak
create an empty /usr/include
compile GNUCash (no need to modify any of the makefiles)
restore the /usr/include.bak to its original spot
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.