The two patches included in this bug report will enable antiword to build on ppc-macos. The patches will not affect any other platform, so it should be safe to apply. Reproducible: Always Steps to Reproduce: 1. 2. 3.
Created attachment 67301 [details, diff] antiword-0.36.1.ebuild.patch Ebuild patch.
Created attachment 67302 [details, diff] antiword-osx.patch antiword patch for OS X issues.
I made some changes using your changes. Please have a look at them in the attachments I will post below. A little list of things to look for: 1. make sure the patch patches when using epatch (the directory was one level too 'deep' in the source tree) 2. don't patch in the src_compile function, instead patch in src_unpack 3. I prefer not to remove flags like -pedantic if this is not necesary 4. if it is possible, avoid making a conditional patch, it is easier for other archs to test the patch if it is not conditional, as well as that it is more obvious if a patch is always applied. It also makes a patch more eligable to be submitted upstream if it is not conditional... (I think this one is) the one and only kde USE flag is masked. Tested on some doc files, and it appears to work. as ~ppc-macos in CVS
Created attachment 67334 [details, diff] changes made to the ebuild These are my changes made to the ebuild. Thanks for your efforts, by the way.
Created attachment 67335 [details, diff] antiword-0.36.1-ppc-macos.diff My (minimal) changes made to the antiword sources to get it compiling.
Hi, About your list of points there: 1. It applies just fine here when the patching is done in the src_compile function, but not in src_unpack. 2. Gotcha! That most certainly is better and explains number 1. 3. I agree. I was looking at the patch that darwinports uses, and they removed the "-pedantic". Goes to show that one shouldn't believe everything one reads. ;-) 4. Agree. Thanks!
