Compilation question

From: Jonathan Calloway 
------------------------------------------------------
Greetings!

I have gone off on a little compiling spree.  I'm doing this to begin 
preparation because I would like to do LFS (I never got started the 
first go-around!)  In any case, I'm trying to compile Abiword.  As 
expected, it ended with errors.  Is there a standard log that gets 
written or place where more human readable output will give me an idea 
of what happened, and why it didn't compile?

Right now, the last few lints of code look like this:

g++: error: unrecognized option '--no-undefined'
make[3]: *** [abiword] Error 1
make[3]: Leaving directory 
`/home/callowayj/Downloads/packages/abiword-2.8.6/src'
make[2]: *** [all-recursive] Error 1
make[2]: Leaving directory 
`/home/callowayj/Downloads/packages/abiword-2.8.6/src'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory 
`/home/callowayj/Downloads/packages/abiword-2.8.6'
make: *** [all] Error 2


Thanks!



=============================================================== From: Sean Brewer ------------------------------------------------------ Check config.log that was generated when you ran ./configure before the make process for warnings and/or errors. That could loop you into some issues.

=============================================================== From: Sean Brewer ------------------------------------------------------ Also, if you're running make (most likely you are), you can log the output. Run make >&log instead of just make. Stderr and stdout will be logged to a file called log. Check config.log that was generated when you ran ./configure before the

=============================================================== From: Stephen Haywood ------------------------------------------------------ Unfortunately, the output from Make is all you are going to get. It's time to hit Google.

=============================================================== From: William Wade ------------------------------------------------------ http://ubuntuforums.org/showthread.php?t=2064584 Apparently you are likely missing this patch: https://github.com/tongson/Gimokod/blob/master/desktop/abiword/abiword-2.8.6-no-undefined.patch

=============================================================== From: Jonathan Calloway ------------------------------------------------------

=============================================================== From: James Nylen ------------------------------------------------------ Patches need to be saved as text files, then run through the patch command. Try this (from the abiword directory): wget https://raw.github.com/tongson/Gimokod/master/desktop/abiword/abiword-2.8.6-no-undefined.patch patch -p1 < abiword-2.8.6-no-undefined.patch The -p1 means strip one directory from the pathnames in the patch (abiword-2.8.6.orig/src/Makefile.am and src/Makefile.am).

=============================================================== From: Jonathan Calloway ------------------------------------------------------ I tried this. I also tried hand-editing src/Makefile.am. I'm still getting the error: g++: error: unrecognized option '--no-undefined'

=============================================================== From: William Wade ------------------------------------------------------ You might want to try cloning the git repo and using that code. It has a lot of fixes that would not have been in the tarball you got from the abiword site. In a new directory: git clone https://github.com/hfiguiere/abiword.git Then configure and compile normally. Wil

=============================================================== From: James Nylen ------------------------------------------------------ I agree that this is probably the easiest way to go. You patched Makefile.am but there is some process you have to go through involving autotools to make it regenerate Makefile (which is the one that actually gets used). I don't know how to do that. More info: http://stackoverflow.com/questions/2531827/what-are-makefile-am-and-makefile-in

=============================================================== From: Jonathan Calloway ------------------------------------------------------ I tried that. The clone was successful, but the configuration script and al= l of its dependencies were missing. I think the maintainer really needs to update their stuff. Jonathan Calloway Sent from my iPad nvolving autotools to make it regenerate Makefile (which is the one that act= ually gets used). I don't know how to do that. More info: http://stackove= rflow.com/questions/2531827/what-are-makefile-am-and-makefile-in : ot of fixes that would not have been in the tarball you got from the abiword= site. ting the error: and. ord-2.8.6-no-undefined.patch ord-2.8.6.orig/src/Makefile.am d-2.8.6-no-undefined.patch s time to hit Google. =20 in preparation because I would like to do LFS (I never got started the first= go-around!) In any case, I'm trying to compile Abiword. As expected, it e= nded with errors. Is there a standard log that gets written or place where m= ore human readable output will give me an idea of what happened, and why it d= idn't compile? ord-2.8.6/src' ord-2.8.6/src' ord-2.8.6'

=============================================================== From: James Nylen ------------------------------------------------------ Run ./autogen.sh

=============================================================== From: Chad Smith ------------------------------------------------------ Run abiword-setup.exe or double click on abiword.dmg and drag the icon into the Applications folder. Oh, wait, they don't maintain AbiWord for Mac anymore. *- Chad W. Smith*

=============================================================== From: Jonathan Calloway ------------------------------------------------------ That worked! Thanks for your help!

=============================================================== From: James Nylen ------------------------------------------------------ The last time I tried to use AbiWord it mangled my document and then crashed repeatedly.

=============================================================== From: Jonathan Calloway ------------------------------------------------------ Well, quit frankly, it's not launching, but I really don't care. This was more of a study in compiling rather than a search for a new word processor!