Well, "utimes" is actually only ever used to implement the
OS.FileSys.setTime basis library function so unless you use that you
could work round the problem by commenting out the line that says
if (utimes(buff, times) != 0)
It would then always execute the next line that raises an exception if
the call failed. I suspect, though, that even if you get past this
problem there will be others. It may be better just to find a different
machine.
Regards,
David
On 26/01/2011 15:45, [email protected] wrote:
Dave,
many thanks for your prompt response.
I found 5.0, 5.2.1 and 5.3 in my own backup. None of them compiles
on the SPARC. Line numbers vary but it's always
basicio.cpp:1379: error: `utimes' was not declared in this scope
basicio.cpp:1379: warning: unused variable 'utimes'
make[2]: *** [basicio.lo] Error 1
make[2]: Leaving directory `/export/home/mic1/temp/poly/polyml.5.3/libpolyml'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory `/export/home/mic1/temp/poly/polyml.5.3'
make: *** [all] Error 2
Let's leave it at that if this can't be fixed easily. I don't want to give you a
lot of trouble messing around with ancient workstations. I can change the
machine running PolyML at any time.
Regards,
Michael
David Matthews wrote:
Poly/ML 4.2.0 is very old now and I really wouldn't be surprised if something
like this was broken. Try with version 5.4 and see if that works. I did
remove support for older SparcStations at one point so it may be that you will
have to use 5.3 or 5.2. You can find them all on the SourceForge site.
Regards,
David
On 26/01/2011 12:30, [email protected] wrote:
Hi,
I'm running PolyML 4.2.0 on some recommissioned Sun SPARCstation 5 and 20 under
Solaris 2.6. I've got code - onced written on a Linux system - which depends
on the
CInterface. C-compiler is gcc 3.4.6, using the Sun 'as' and 'ld'. Creating a
shared object
file normally looks something like:
gcc -fPIC -c file.c -o file.o
ld -G -z text -o file.so file.o
Calling a function of this shared object file according to the CInterface
manual
simply
takes the cpu to the max. .
I greatly appreciate your help.
Regards,
Michael
_______________________________________________
polyml mailing list
[email protected]
http://lists.inf.ed.ac.uk/mailman/listinfo/polyml
_______________________________________________
polyml mailing list
[email protected]
http://lists.inf.ed.ac.uk/mailman/listinfo/polyml
_______________________________________________
polyml mailing list
[email protected]
http://lists.inf.ed.ac.uk/mailman/listinfo/polyml
_______________________________________________
polyml mailing list
[email protected]
http://lists.inf.ed.ac.uk/mailman/listinfo/polyml
