I found the reason for the compile error # ./aimk -no-secure -java -spool-classic ... configure: error: C compiler cannot create executables
although I must admit I don't understand the internals that much why it has to do with java. I had to set JAVA_HOME, then it contiunes to compile.. -- Nick -----Ursprüngliche Nachricht----- Von: Reuti [mailto:[email protected]] Gesendet: Donnerstag, 07. November 2013 11:53 An: Kraus, Niki Cc: [email protected] Betreff: Re: AW: [gridengine users] compiling question for Solaris 10 x86 - configure: error: C compiler cannot create executables Hi, Am 07.11.2013 um 08:35 schrieb Kraus, Niki: > I found these page - > http://gridengine.org/blog/2011/11/23/what-now/ > > telling us about two open source possibilities to follow - > > "Son of Grid Engine" https://arc.liv.ac.uk/trac/SGE "Open Grid > Scheduler" http://gridscheduler.sourceforge.net/ Yep. > so, today there are two SGE open source forks after Oracles closed > source decision, Orcale laid down their GridEngine business recently and their customers directed to Univa who hired the former team already some time before http://www.univa.com/about/ > and furthermore, these development codes are independent from each other, and > it's code is not merged together somehow ? Correct. -- Reuti > and I simply can decide upon my needs what to choose? > > -- Nick > > > -----Ursprüngliche Nachricht----- > Von: Reuti [mailto:[email protected]] > Gesendet: Mittwoch, 06. November 2013 13:54 > An: Kraus, Niki > Cc: [email protected] > Betreff: Re: [gridengine users] compiling question for Solaris 10 x86 > - configure: error: C compiler cannot create executables > > Hi, > > Am 06.11.2013 um 13:12 schrieb Kraus, Niki: > >> I try to compile the current release GE2011.11p1 under Solaris 10 x86 >> (in a Solaris zone), but I run into troubles > > you may also look into SoGE https://arc.liv.ac.uk/trac/SGE > > >> # ./aimk -no-secure -java -spool-classic >> if: Expression syntax >> >> or >> >> # csh -x ./aimk -no-secure -java -spool-classic . if ( SOLARISAMD64 >> == >> SOLARIS64 ) then if ( SOLARISAMD64 == SOLARISAMD64 ) then set CFLAGS >> = >> -D_LARGEFILE64_SOURCE=1 -DHAS_SOCKLEN_T -I/build/berkeleydb/include/ >> -DTARGET_64BIT -DSPOOLING_dynamic -DSOLARIS -DSOLARISAMD64 >> -D__EXTENSIONS__ -D_POSIX_C_SOURCE=199506L -DGETHOSTBYNAME_R5 >> -DGETHOSTBYADDR_R7 -DUSE_POLL -errwarn=%all set compversion = `cc -V >> | & head -1 | sed 's/[a-zA-Z :]*\([0-9].[0-9]*\).*$/\1/'` head -1 sed >> s/[a-zA-Z :]*\([0-9].[0-9]*\).*$/\1/ set major = `echo $compversion | cut >> -f1 -d"."` cut -f1 -d. >> echo cc -V >> set minor = `echo $compversion | cut -f2 -d"."` cut -f2 -d. >> echo cc -V >> if ( cc -V < = 5 && cc -V < = 8 ) then >> if: Expression syntax >> # >> >> I use CSWgcc4core from blastwave.org - is this a valid package? >> gcc from blastwave doesn't recognize -V : > > The default is to use the standard compiler on Solaris, which is aware of > "-V" (in fact, it would have been replaced by the major and minor version > already some lines above). In case you want to use gcc, you can try to > execute ./aimk with -gcc as additional option. > > -- Reuti > > >> # cc -V >> cc: error: unrecognized command line option '-V' >> cc: fatal error: no input files >> compilation terminated. >> >> correct usage: >> >> # cc --version >> cc (GCC) 4.8.0 >> Copyright (C) 2013 Free Software Foundation, Inc. >> This is free software; see the source for copying conditions. There >> is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR >> PURPOSE. >> >> >> So, if I look into the aimk script, the cause is simple, it's the checking >> of the gcc version. >> >> To overcome this, I simply hardcoded the version question into the aimk >> code, e.g. >> >> #set compversion = `cc -V |& head -1 | cut -f4 -d" "` set compversion >> = 4.8.0 >> >> which might not be perfect, but it worked. >> >> >> 2) >> but then .. >> >> # ./aimk -no-secure -java -spool-classic >> WARNING: >> Setting $JAVA_HOME to "/usr" causes problems on some systems, because >> the associated include path will be "/usr/include", which is a >> reserved system include path. >> >> Please either set $JAVA_HOME correctly or disable Java & JGDI support >> with aimk flags: -no-java -no-jni >> >> Contining without Java & JGDI support >> >> Building in directory: /Installer/SGE6u25/GE2011.11p1/source >> making in SOLARISAMD64/ for SOLARISAMD64 at host dbegkgrt1 >> _________3_r_d_p_a_r_t_y__H_W_L_O_C_______ >> >> ### >> ### Configuring hwloc distribution tarball ### Startup tests ### >> checking build system type... i386-pc-solaris2.10 checking host >> system type... i386-pc-solaris2.10 checking target system type... >> i386-pc-solaris2.10 checking for a BSD-compatible install... >> /opt/csw/bin/ginstall -c checking whether build environment is sane... >> yes checking for a thread-safe mkdir -p... /opt/csw/bin/gmkdir -p >> checking for gawk... gawk checking whether make sets $(MAKE)... yes >> checking how to create a ustar tar archive... gnutar checking for >> hwloc version... 1.2.2 checking for gcc... gcc checking whether the C >> compiler works... no >> configure: error: in >> `/Installer/SGE6u25/GE2011.11p1/source/3rdparty/hwloc/hwloc-1.2.2/SOLARISAMD64': >> configure: error: C compiler cannot create executables See >> `config.log' for more details >> make: Warning: Ignoring DistributedMake -j option >> make: Warning: Ignoring DistributedMake -o option >> make: Fatal error: Can't find `Makefile': No such file or directory >> not done >> >> >> so my question is simple - is there a overview of required Solaris or GNU >> packages which need to be installed before? >> Or something to watch out, like PATH=/usr/ccs/bin.., or SUNWsprot must be >> installed.., or which GNU compiler (again blastwave?) is perfect for >> compiling? >> >> Please share your ideas with me. >> >> Thank you >> >> Bye Niki >> >> >> 3 Banken EDV >> Infrastruktur & Applikationen >> Niki Kraus / System Integrator / Solaris, Linux Untere Donaulände 28, >> A-4020 Linz >> Tel.: +43 (732) 7802 32622 >> Mobil: +43 (664) 80556 3502 >> >> >> >> _______________________________________________ >> users mailing list >> [email protected] >> https://gridengine.org/mailman/listinfo/users > > _______________________________________________ users mailing list [email protected] https://gridengine.org/mailman/listinfo/users
