On 12/27/2014 04:22 PM, Michele wrote:

Yeah, /bin/sh isn't /bin/bash on Solaris 10, so far as I can remember.
You will need to change #!/bin/sh to #!/bin/bash on the scripts. And
remember to source the environment script (as the entry on the wikibook
says).

To figure out what make you have, try "make -v". Should say "GNU Make"
right at the top if it's gnu make.

http://git-scm.com for source tarballs. Once that's compiled/installed,
checkout a copy of the master branch using the instructions at
http://en.wikibooks.org/wiki/OpenSCAD_User_Manual/Building_on_Linux/UNIX#Building_OpenSCAD_yourself
and start working your way down. The instructions assume you have sudo
installed. If not (and using sudo is a good idea in general), drop down
to root privs before running the install target for make.

You will probably have to build the dependencies yourself (details are
there on the wiki).

--
--Joseph Lenox, BS, MS
I'm an engineer. I solve problems.

/"I would use the latest master. I will be hard to troubleshoot an older
version."/

OK, I thought that's what I had.  Where do I get the latest version?

"I think most scripts assume that the system shell is also bash. Try forcing
bash by adding this to the top:
#!/bin/bash"

Well at least it gave me a different set of errors this time.

# ./check-dependencies.sh
depname    minimum    found      OKness      \033[0m
grep: illegal option -- q
Usage: grep -hblcnsviw pattern file . . .
grep: illegal option -- q
Usage: grep -hblcnsviw pattern file . . .
qt4        unknown    unknown    NotOK      \033[0m
grep: illegal option -- q
Usage: grep -hblcnsviw pattern file . . .
grep: illegal option -- q
Usage: grep -hblcnsviw pattern file . . .
cgal        unknown    unknown    NotOK      \033[0m
grep: illegal option -- q
Usage: grep -hblcnsviw pattern file . . .
grep: illegal option -- q
Usage: grep -hblcnsviw pattern file . . .
gmp        unknown    unknown    NotOK      \033[0m
grep: illegal option -- q
Usage: grep -hblcnsviw pattern file . . .
grep: illegal option -- q
Usage: grep -hblcnsviw pattern file . . .
mpfr        unknown    unknown    NotOK      \033[0m
grep: illegal option -- q
Usage: grep -hblcnsviw pattern file . . .
grep: illegal option -- q
Usage: grep -hblcnsviw pattern file . . .
boost      unknown    unknown    NotOK      \033[0m
grep: illegal option -- q
Usage: grep -hblcnsviw pattern file . . .
grep: illegal option -- q
Usage: grep -hblcnsviw pattern file . . .
opencsg    unknown    unknown    NotOK      \033[0m
grep: illegal option -- q
Usage: grep -hblcnsviw pattern file . . .
grep: illegal option -- q
Usage: grep -hblcnsviw pattern file . . .
glew        unknown    unknown    NotOK      \033[0m
grep: illegal option -- q
Usage: grep -hblcnsviw pattern file . . .
grep: illegal option -- q
Usage: grep -hblcnsviw pattern file . . .
eigen      unknown    unknown    NotOK      \033[0m
./check-dependencies.sh: line 81: [: =: unary operator expected
grep: illegal option -- q
Usage: grep -hblcnsviw pattern file . . .
grep: illegal option -- q
Usage: grep -hblcnsviw pattern file . . .
glib2      unknown    2.4.1      NotOK      \033[0m
awk: syntax error near line 1
awk: bailing out near line 1
awk: syntax error near line 1
awk: bailing out near line 1
grep: illegal option -- q
Usage: grep -hblcnsviw pattern file . . .
grep: illegal option -- q
Usage: grep -hblcnsviw pattern file . . .
gcc        unknown    unknown    NotOK      \033[0m
grep: illegal option -- q
Usage: grep -hblcnsviw pattern file . . .
grep: illegal option -- q
Usage: grep -hblcnsviw pattern file . . .
bison      unknown    unknown    NotOK      \033[0m
grep: illegal option -- q
Usage: grep -hblcnsviw pattern file . . .
grep: illegal option -- q
Usage: grep -hblcnsviw pattern file . . .
flex        unknown    unknown    NotOK      \033[0m
grep: illegal option -- q
Usage: grep -hblcnsviw pattern file . . .
grep: illegal option -- q
Usage: grep -hblcnsviw pattern file . . .
make        3          unknown    NotOK      \033[0m
#

/"You’re not supposed to execute that script, but source it:
$ . .scripts/setenv-unibuild.sh"/

OK, now I get this:
*

. scripts/setenv-unibuild.sh

test: argument expected
#*

/"I would strongly recommend teaming up with someone who has significant
experience with Solaris and build systems."/

Now /that /is an excellent suggestion.  Were I still working at my old
company that was loaded with Sun system programming talent, that would have
been no problem.  But being retired for some years and all, my circle of
Unix experts is now basically none.

/"Porting to a new platform could be challenging and take significant time.
..but who knows, you might get lucky :) "/

Sure, and I might win the Powerball too :-)  I probably have about the same
chance.  It's now painfully obvious to everyone that I haven't a clue.  I
feel like I'm stuck in a maze of twisty little passages, all of them
different.  If anyone reading this thread would like to help me on this
project, I'd be very grateful.  Otherwise, I guess it will just remain a
dream.

--
View this message in context: http://forum.openscad.org/Compiling-for-64-bit-Sparc-Solaris-10-tp10741p10761.html
Sent from the OpenSCAD mailing list archive at Nabble.com.

On Dec 27, 2014, at 17:39 PM, Michele denber@mindspring.com wrote:

You clone it (using git). See https://github.com/openscad/openscad

You have an old version of grep. I’d install a newer version, or GNU grep.
You can probably safely remove the -q option though.

Hmm, which version of bash are you using? I’d recommend at least 3.x. I’m using 3.2. Most Linux users should be on 4.

I’d say, if you enjoy it, keep going :)
I’ve done a lot of this sort of stuff for work, so I’ll back down early as I know how annoying it can be.

-Marius

His version of bash is 3.2. I know that his version of grep is not gnu. Awk
is going to be similarly different. Everything on Solaris is just different
enough to be frustrating to port stuff written for Linux on it; sun doing
things the Apple way. Although to be fair it was more like the Bad old days
of yore where you had to make your own cpu to be a Real computer company.

I worked a few years ago to get stuff compiled from source working on
Solaris 10 sparc. It was so painful that the machines were replaced with
Linux x86 systems as soon as we knew that the EDA tools we needed ran on
Linux x86. Newer core 2 systems were faster cheaper and more reponsive
anyway than the ultra45s.

Anyone who has such an old workstation and wants to use it is best advised
to become proficient in the black arts in order to keep it running. If I
had access to a system with your configuration I might be able to get it
compiled.
On Dec 27, 2014 4:56 PM, "Marius Kintel" marius@kintel.net wrote:

Sure, definitely won't be able to help until Monday. Internet connection is
lousy where I am now.
On Dec 27, 2014 7:24 PM, "Michele" denber@mindspring.com wrote:

I'm not a lisp person, can't really tell the difference.

Wonder if the source could be pried out of someone's hands...
On Dec 28, 2014 2:25 PM, "Michele" denber@mindspring.com wrote: