On Wed, Sep 16, 2009 at 3:40 PM, Kostas Oikonomou <k...@research.att.com> wrote:
> Hi Gaby,
>
> Thanks for responding.

Thank *you* for taking the time to work the issue and
suggest possible fixes.  That is very much appreciated.

>
>> I used to have an old machine that was running OpenSolaris, but it died
>> about
>> two years ago :-(  Since then, I have not had access to an OpenSolaris box
>> even though I get all traffic on the OpenSolaris project.
>
> OpenSolaris has made a huge amount of progress since then!

I suspect I need to find a new machine and install opensolaris.

>
>> Many thanks for your feedback.  I have just checked in fixes based on
>> your suggestions.  There remains a few issues, and I would very
>> much appreciate your testing the branch 1.3.x to see whether
>> I got things right.  Thanks in advance.
>
>>> To get configure to do the right things, e.g. define
>>> SUNplatform for openpty.c, I edited it to replace "solaris*"
>>> with "*solaris*" everywhere.
>>
>> I'm a bit puzzled by this because the configure.ac file does not
>> contain bare "solaris*".  Rather, I based the tests on "*solaris*".
>> More specifically, the relevant portion of configure.ac reads:
>>
>>   *solaris*)
>>       AC_DEFINE([SUNplatform], [], [SunOS flavour])
>>       ;;
>
> I did not regenerate configure, just used the existing one.  The existing
> one had "solaris*".

I had a look at the 'configure' script automatically generated by
Autoconf from 'configure.ac'.  Indeed there are several tests that
pattern match only on 'solaris*' as opposed to '*solaris*'.
There at line 4243, 4699, 7341, 7903, 8570, 9546.  All of them
are Autoconf internal magics, and none of them is related to
the test for setting SUNplatform.

The test in 'configure.ac' for that test gets correctly expanded
in 'configure' and matches against '*solaris*'.



>
>>> 2. Next I tried building with Sun's compilers, which appears
>>> to be possible as far as I can tell by scanning configure.
>>
>> Wow!  I'm glad to hear that you can actually build OpenAxiom
>> with the Sun compiler. I've changed the complaint about GNU C
>> compiler.  See the patch below (checked in.)  I put in this check
>> in the very early days of the axiom.build-improvements effort because,
>> at the time, the assumption was that we were going to use GCL and
>> GCL critically depends on GNU extensions.
>>
>> Now we complain about lack of GCC only if we are building OpenAxiom
>> with the GCL runtime.
>
> Ok, very good.  I will re-try Sun's cc (which I prefer to gcc, anyway.)  You
> know that it is freely-available, correct?

Yes. (In the '90s my favorite compiler was Sun CC; then I got to work
on GCC, then, ... :-))

>
>>> Otherwise the compilation of openpty.c failed. �I don't
>>> really know if this hack is right.
>>
>> Basically, OpenAxiom needs openpty.  I think Solars should have
>> it could you look at config.log and tell me what the configure test
>> found?
>
> Unfortunately, neither Solaris nor OpenSolaris have pty.h. I am attaching
> config.log.gz.

Thanks.  Indeed, I just learnt that Python got into similar problem and they
had to write their own substitute.  I guess that is what I'll do for OpenAxiom
too.

>
>>
>> OK.  Please, could you check out a fresh copy of the 1.3.x
>> branch and test whether it builds correctly, or what remains to
>> be fixed?  I don't have access to an opensolaris box at the moment.
>
> Yes, I will.  How do I do that?  CVS or something?

OpenAxiom uses SVN repo at SourceForge.  The general information
for download is at

    http://www.open-axiom.org/download.html

In your case, you might want to issue

svn co https://open-axiom.svn.sf.net/svnroot/open-axiom/1.3.x  oa-1.3.x

Best,

-- Gaby

------------------------------------------------------------------------------
Come build with us! The BlackBerry&reg; Developer Conference in SF, CA
is the only developer event you need to attend this year. Jumpstart your
developing skills, take BlackBerry mobile applications to market and stay 
ahead of the curve. Join us from November 9&#45;12, 2009. Register now&#33;
http://p.sf.net/sfu/devconf
_______________________________________________
open-axiom-devel mailing list
open-axiom-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/open-axiom-devel

Reply via email to