Eric Hoch wrote:

This sounds good. Are you in IRC ooo-macport sometimes? I would really be willing to give this a try and see if I am able to build on Leopard and the build runs on Tiger. But be asured that I am just a more or less dump user without any programming skills so that I can only verify that it builds and runs but can't help integrating the needed code.

Yes, I'm usually on there as Dyrcona, same name I use on the OO.o wiki. I'm not on every day, but you can find me there two or three times a week, and I always do my best to make the Wednesday meeting.



OK a first run of .configure gives me:

configure: error: C compiler cannot create executables
See `config.log' for more details.


and in configure.log the error is:

configure:4826: checking for C compiler default output file name
configure:4853: gcc -isysroot /Developer/SDKs/MacOSX10.4u.sdk -isysroot /Developer/SDKs/MacOSX10.4u.sdk -W
ld: library not found for -lcrt1.10.5.o
collect2: ld returned 1 exit status

OK. That tells me something. I'll have to take a deeper look.

I am still getting up to speed on the OO.o build process. I have the basics down of build && deliver, but I need to take a look into the configure scripts, etc. Give me a few days (I have a "real" job and a family), and I should be able to get it working.

However, as James McKenzie mentioned in a previous message, it was tried with Tiger and Panther and didn't work then. My hunch is that may have something to do with using the X11 libraries. This *may* work in an Aqua build. I am willing to try anyway.

Also, it would be interesting to try getting universal binaries. There are some gotchas and these could easily be show stoppers in a project as large as OO.o (particularly one that relies so heavily on JNI).


If you need more informations, let me know.

I definitely will.


Eric


Cheers,
Jason

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to