This is what I get: Undefined symbols: __ZTVN10__cxxabiv117__class_type_infoE __ZTVN10__cxxabiv120__si_class_type_infoE __ZdlPv __Znwm ___cxa_pure_virtual ___gxx_personality_v0 There are six patches[1] available over at MacPorts and lot of modifications in the portfile[2]. OpenJade is not keyworded ~x86-macos but both glib and gnutls depend upon it with USE=doc (via gtk-doc). So this bug serves as a reference for why doc will be masked on glib and gnutls. [1] http://trac.macports.org/projects/macports/browser/trunk/dports/textproc/openjade/files?rev=27555 [2] http://trac.macports.org/projects/macports/browser/trunk/dports/textproc/openjade/Portfile?rev=27555
macports patches are dirty as hell, and not really an option for me. However, I tried for several hours to get the libtool horror here right, and I failed. It is weird that you only get these few, I got a lot more, and for OpenSP.
> macports patches are dirty as hell, and not really an option for me. I tried the patches but I could get openjade to build with them. To worry about clean patches, I'd first need the ebuild to actually compile ;) > It is weird that you only get these few, I got a lot more, and for OpenSP. OpenSP built without any problems for me. The amount of errors doesn't say much, though, I'd say - at least in this case - the error occurred almost immediately after configure had finished. I've pasted[1] the output. [1] http://paste.lisp.org/display/45803
I could *not* get (In reply to comment #2) > I tried the patches but I could get openjade to build with them. I meant I could *not* get openjade to build with them.
(In reply to comment #1) > It is weird that you only get these few, I got a lot more, and for OpenSP. Sorry, misunderstood you there - you mean errors when building openjade, related to linking against opensp, right? Could you please paste the exact error?
update: * just tried to compile openjade on my ppc mac and got exactly the same errors as on my intel mac. you do have opensp installed, right? ;) * got openjade to compile with the patches and custom configure parameters, flags from macports. cutting down on the changes now to see what's necessary/broken/etc.
Created attachment 127292 [details, diff] work-in-progress diff against ebuild openjade-1.3.2 Okay so I managed to compile openjade on my machine. That's good news, the bad news is how I did that. I've attached a diff against the ebuild. The diff is *only* meant to illustrate that openjade can be built, which I would like you too verify on ppc-macos (since I got the same errors on both my powerpc and my intel macs I don't think there's much of a point in testing if it works on my powerpc mac, you got a different error, though). You need the macports patches in the files dir in order for this patch to work. I cannot stress enough how far this diff is from something that's supposed to be committed ;)
Created attachment 127294 [details, diff] OpenJade mess I'll give you some insight in my kitchen. I think I sort of give up here, and go for a little bit of MacPorts patching to shut up the linker complaining about missing symbols. (which I think is really bad, but might be the only way out for the piece of crap software...)
Created attachment 127301 [details, diff] work-in-progress diff against ebuild openjade-1.3.2 interesting. I got a completely different set of patches to work ( one less of the ones we have and one macports patch )
the macports patch patch-configure adds this line, among others, to configure: CXX=$ac_ct_CXX for some reason this becomes CXX='' for me in its current state, if --host and --build are passed the way they are now. without them it becomes CXX=g++
that is because g++ is not a cross compiler, while Gentoo does cross-compiling even though build and host are the same.
fixed in r10943[1]. [1] http://overlays.gentoo.org/proj/alt/changeset/10943
Ugly, but let's hope this rids us from the thing
