<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	>
<channel>
	<title>Comments on: Adding mcrypt Support to Sun&#8217;s CoolStack</title>
	<atom:link href="http://blogs.everycity.co.uk/alasdair/2008/10/adding-mcrypt-support-to-suns-coolstack/feed/" rel="self" type="application/rss+xml" />
	<link>http://blogs.everycity.co.uk/alasdair/2008/10/adding-mcrypt-support-to-suns-coolstack/</link>
	<description></description>
	<pubDate>Tue, 07 Feb 2012 05:14:54 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.6.3</generator>
		<item>
		<title>By: Marc Lobelle</title>
		<link>http://blogs.everycity.co.uk/alasdair/2008/10/adding-mcrypt-support-to-suns-coolstack/#comment-621</link>
		<dc:creator>Marc Lobelle</dc:creator>
		<pubDate>Fri, 21 Oct 2011 16:50:06 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.everycity.co.uk/alasdair/?p=3#comment-621</guid>
		<description>Thinking about it, if I am just wanting to compile libmcript, it means I do not have it and thus not mcript.h either, so why does configure complain ?</description>
		<content:encoded><![CDATA[<p>Thinking about it, if I am just wanting to compile libmcript, it means I do not have it and thus not mcript.h either, so why does configure complain ?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Marc Lobelle</title>
		<link>http://blogs.everycity.co.uk/alasdair/2008/10/adding-mcrypt-support-to-suns-coolstack/#comment-620</link>
		<dc:creator>Marc Lobelle</dc:creator>
		<pubDate>Fri, 21 Oct 2011 13:49:32 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.everycity.co.uk/alasdair/?p=3#comment-620</guid>
		<description>Hello, 
I need mcrypt because it is used by phpldapadmin. I need in particular md5crypt that is used in LINUX and I need to import a set of users from a ldap running on a LINUX system to one running on solaris.
As you noticed mcrypt is missing from solaris distros.
I tried to compile libmcrypt according to your indications (by the way, I added md5 at the end of the list of algorithms, was that right) and got this result

tempest-[2]-mcrypt-2.6.8# ./configure --prefix=/opt/libs/libmcrypt --enable-dynamic-loading --with-included-algos=cast-128,gost,rijndael-128,twofish,arcfour,cast-256,loki97,rijndael-192,saferplus,wake,blowfish-compat,des,rijndael-256,serpent,xtea,blowfish,enigma,rc2,tripledes
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/sfw/bin/install -c
checking whether build environment is sane... yes
checking for a thread-safe mkdir -p... /opt/sfw/bin/mkdir -p
checking for gawk... gawk
checking whether make sets $(MAKE)... yes
checking for style of include used by make... GNU
checking for gcc... cc
checking for C compiler default output file name... a.out
checking whether the C compiler works... yes
checking whether we are cross compiling... no
checking for suffix of executables...
checking for suffix of object files... o
checking whether we are using the GNU C compiler... no
checking whether cc accepts -g... yes
checking for cc option to accept ISO C89... none needed
checking dependency style of cc... none
checking for a sed that does not truncate output... /opt/csw/bin/sed
checking for grep that handles long lines and -e... /opt/csw/bin/ggrep
checking for egrep... /opt/csw/bin/ggrep -E
checking for fgrep... /opt/csw/bin/ggrep -F
checking for non-GNU ld... /usr/ccs/bin/ld
checking if the linker (/usr/ccs/bin/ld) is GNU ld... yes
checking for BSD- or MS-compatible name lister (nm)... /usr/ccs/bin/nm -p
checking the name lister (/usr/ccs/bin/nm -p) interface... BSD nm
checking whether ln -s works... yes
checking the maximum length of command line arguments... 786240
checking whether the shell understands some XSI constructs... yes
checking whether the shell understands "+="... no
checking for /usr/ccs/bin/ld option to reload object files... -r
checking how to recognize dependent libraries... pass_all
checking for ar... ar
checking for strip... strip
checking for ranlib... ranlib
checking command to parse /usr/ccs/bin/nm -p output from cc object... ok
checking how to run the C preprocessor... cc -E
checking for ANSI C header files... yes
checking for sys/types.h... yes
checking for sys/stat.h... yes
checking for stdlib.h... yes
checking for string.h... yes
checking for memory.h... yes
checking for strings.h... yes
checking for inttypes.h... yes
checking for stdint.h... yes
checking for unistd.h... yes
checking for dlfcn.h... yes
checking for objdir... .libs
checking for cc option to produce PIC... -KPIC -DPIC
checking if cc PIC flag -KPIC -DPIC works... yes
checking if cc static flag -Bstatic works... no
checking if cc supports -c -o file.o... yes
checking if cc supports -c -o file.o... (cached) yes
checking whether the cc linker (/usr/ccs/bin/ld) supports shared libraries... yes
checking dynamic linker characteristics... solaris2.10 ld.so
checking how to hardcode library paths into programs... immediate
checking whether stripping libraries is possible... no
checking if libtool supports shared libraries... yes
checking whether to build shared libraries... yes
checking whether to build static libraries... yes
checking for gcc... (cached) cc
checking whether we are using the GNU C compiler... (cached) no
checking whether cc accepts -g... (cached) yes
checking for cc option to accept ISO C89... (cached) none needed
checking dependency style of cc... (cached) none
checking for libmcrypt-config... no
checking for libmcrypt - version &#62;= 2.5.0... no
*** Could not run libmcrypt test program, checking why...
*** The test program failed to compile or link. See the file config.log for the
*** exact error that occured. This usually means LIBMCRYPT was incorrectly installed
*** or that you have moved LIBMCRYPT since it was installed. In the latter case, you
*** may want to edit the libmcrypt-config script: no
configure: error: *** libmcrypt was not found
tempest-[3]-mcrypt-2.6.8# glocate libmcrypt
tempest-[4]-mcrypt-2.6.8# ls /opt/libs/
./   ../
tempest-[5]-mcrypt-2.6.8#


actually, if I check config.log, it appears that /usr/include/ mcrypt.h is missing

and I do not have it anywhere

Do you have it and where did you get it ?

Thanks

Marc</description>
		<content:encoded><![CDATA[<p>Hello,<br />
I need mcrypt because it is used by phpldapadmin. I need in particular md5crypt that is used in LINUX and I need to import a set of users from a ldap running on a LINUX system to one running on solaris.<br />
As you noticed mcrypt is missing from solaris distros.<br />
I tried to compile libmcrypt according to your indications (by the way, I added md5 at the end of the list of algorithms, was that right) and got this result</p>
<p>tempest-[2]-mcrypt-2.6.8# ./configure &#8211;prefix=/opt/libs/libmcrypt &#8211;enable-dynamic-loading &#8211;with-included-algos=cast-128,gost,rijndael-128,twofish,arcfour,cast-256,loki97,rijndael-192,saferplus,wake,blowfish-compat,des,rijndael-256,serpent,xtea,blowfish,enigma,rc2,tripledes<br />
checking build system type&#8230; i386-pc-solaris2.10<br />
checking host system type&#8230; i386-pc-solaris2.10<br />
checking target system type&#8230; i386-pc-solaris2.10<br />
checking for a BSD-compatible install&#8230; /opt/sfw/bin/install -c<br />
checking whether build environment is sane&#8230; yes<br />
checking for a thread-safe mkdir -p&#8230; /opt/sfw/bin/mkdir -p<br />
checking for gawk&#8230; gawk<br />
checking whether make sets $(MAKE)&#8230; yes<br />
checking for style of include used by make&#8230; GNU<br />
checking for gcc&#8230; cc<br />
checking for C compiler default output file name&#8230; a.out<br />
checking whether the C compiler works&#8230; yes<br />
checking whether we are cross compiling&#8230; no<br />
checking for suffix of executables&#8230;<br />
checking for suffix of object files&#8230; o<br />
checking whether we are using the GNU C compiler&#8230; no<br />
checking whether cc accepts -g&#8230; yes<br />
checking for cc option to accept ISO C89&#8230; none needed<br />
checking dependency style of cc&#8230; none<br />
checking for a sed that does not truncate output&#8230; /opt/csw/bin/sed<br />
checking for grep that handles long lines and -e&#8230; /opt/csw/bin/ggrep<br />
checking for egrep&#8230; /opt/csw/bin/ggrep -E<br />
checking for fgrep&#8230; /opt/csw/bin/ggrep -F<br />
checking for non-GNU ld&#8230; /usr/ccs/bin/ld<br />
checking if the linker (/usr/ccs/bin/ld) is GNU ld&#8230; yes<br />
checking for BSD- or MS-compatible name lister (nm)&#8230; /usr/ccs/bin/nm -p<br />
checking the name lister (/usr/ccs/bin/nm -p) interface&#8230; BSD nm<br />
checking whether ln -s works&#8230; yes<br />
checking the maximum length of command line arguments&#8230; 786240<br />
checking whether the shell understands some XSI constructs&#8230; yes<br />
checking whether the shell understands &#8220;+=&#8221;&#8230; no<br />
checking for /usr/ccs/bin/ld option to reload object files&#8230; -r<br />
checking how to recognize dependent libraries&#8230; pass_all<br />
checking for ar&#8230; ar<br />
checking for strip&#8230; strip<br />
checking for ranlib&#8230; ranlib<br />
checking command to parse /usr/ccs/bin/nm -p output from cc object&#8230; ok<br />
checking how to run the C preprocessor&#8230; cc -E<br />
checking for ANSI C header files&#8230; yes<br />
checking for sys/types.h&#8230; yes<br />
checking for sys/stat.h&#8230; yes<br />
checking for stdlib.h&#8230; yes<br />
checking for string.h&#8230; yes<br />
checking for memory.h&#8230; yes<br />
checking for strings.h&#8230; yes<br />
checking for inttypes.h&#8230; yes<br />
checking for stdint.h&#8230; yes<br />
checking for unistd.h&#8230; yes<br />
checking for dlfcn.h&#8230; yes<br />
checking for objdir&#8230; .libs<br />
checking for cc option to produce PIC&#8230; -KPIC -DPIC<br />
checking if cc PIC flag -KPIC -DPIC works&#8230; yes<br />
checking if cc static flag -Bstatic works&#8230; no<br />
checking if cc supports -c -o file.o&#8230; yes<br />
checking if cc supports -c -o file.o&#8230; (cached) yes<br />
checking whether the cc linker (/usr/ccs/bin/ld) supports shared libraries&#8230; yes<br />
checking dynamic linker characteristics&#8230; solaris2.10 ld.so<br />
checking how to hardcode library paths into programs&#8230; immediate<br />
checking whether stripping libraries is possible&#8230; no<br />
checking if libtool supports shared libraries&#8230; yes<br />
checking whether to build shared libraries&#8230; yes<br />
checking whether to build static libraries&#8230; yes<br />
checking for gcc&#8230; (cached) cc<br />
checking whether we are using the GNU C compiler&#8230; (cached) no<br />
checking whether cc accepts -g&#8230; (cached) yes<br />
checking for cc option to accept ISO C89&#8230; (cached) none needed<br />
checking dependency style of cc&#8230; (cached) none<br />
checking for libmcrypt-config&#8230; no<br />
checking for libmcrypt - version &gt;= 2.5.0&#8230; no<br />
*** Could not run libmcrypt test program, checking why&#8230;<br />
*** The test program failed to compile or link. See the file config.log for the<br />
*** exact error that occured. This usually means LIBMCRYPT was incorrectly installed<br />
*** or that you have moved LIBMCRYPT since it was installed. In the latter case, you<br />
*** may want to edit the libmcrypt-config script: no<br />
configure: error: *** libmcrypt was not found<br />
tempest-[3]-mcrypt-2.6.8# glocate libmcrypt<br />
tempest-[4]-mcrypt-2.6.8# ls /opt/libs/<br />
./   ../<br />
tempest-[5]-mcrypt-2.6.8#</p>
<p>actually, if I check config.log, it appears that /usr/include/ mcrypt.h is missing</p>
<p>and I do not have it anywhere</p>
<p>Do you have it and where did you get it ?</p>
<p>Thanks</p>
<p>Marc</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Martin Ramos</title>
		<link>http://blogs.everycity.co.uk/alasdair/2008/10/adding-mcrypt-support-to-suns-coolstack/#comment-239</link>
		<dc:creator>Martin Ramos</dc:creator>
		<pubDate>Thu, 22 Apr 2010 17:07:36 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.everycity.co.uk/alasdair/?p=3#comment-239</guid>
		<description>It worked for me, I used a T2000 server SPARC, solaris 10 SPARC, in a Solaris 10 zone.

I just change:
libmcrypt-2.5.7 instead of libmcrypt-2.5.8
gcc instead of cc, because I had not cc installed.</description>
		<content:encoded><![CDATA[<p>It worked for me, I used a T2000 server SPARC, solaris 10 SPARC, in a Solaris 10 zone.</p>
<p>I just change:<br />
libmcrypt-2.5.7 instead of libmcrypt-2.5.8<br />
gcc instead of cc, because I had not cc installed.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Chris</title>
		<link>http://blogs.everycity.co.uk/alasdair/2008/10/adding-mcrypt-support-to-suns-coolstack/#comment-164</link>
		<dc:creator>Chris</dc:creator>
		<pubDate>Tue, 13 Oct 2009 19:18:49 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.everycity.co.uk/alasdair/?p=3#comment-164</guid>
		<description>Hi, just wanted to say thanks! Your directions saved me a lot of time.</description>
		<content:encoded><![CDATA[<p>Hi, just wanted to say thanks! Your directions saved me a lot of time.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Gavin</title>
		<link>http://blogs.everycity.co.uk/alasdair/2008/10/adding-mcrypt-support-to-suns-coolstack/#comment-94</link>
		<dc:creator>Gavin</dc:creator>
		<pubDate>Mon, 30 Mar 2009 21:22:50 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.everycity.co.uk/alasdair/?p=3#comment-94</guid>
		<description>I've successfully compiled the mcrypt modules for php - however when I view the php info via browser it does not display the support ciphers and modes for mcrypt.
Please advise</description>
		<content:encoded><![CDATA[<p>I&#8217;ve successfully compiled the mcrypt modules for php - however when I view the php info via browser it does not display the support ciphers and modes for mcrypt.<br />
Please advise</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Mark</title>
		<link>http://blogs.everycity.co.uk/alasdair/2008/10/adding-mcrypt-support-to-suns-coolstack/#comment-81</link>
		<dc:creator>Mark</dc:creator>
		<pubDate>Thu, 19 Feb 2009 17:32:58 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.everycity.co.uk/alasdair/?p=3#comment-81</guid>
		<description>old post, but just to note, if your shell is zsh, you'll encounter problems during the configure phase when it switches to configuring libltdl and you have set the compilers via CC and CXX env variables.

changing to bash for the configure and compile worked for me.</description>
		<content:encoded><![CDATA[<p>old post, but just to note, if your shell is zsh, you&#8217;ll encounter problems during the configure phase when it switches to configuring libltdl and you have set the compilers via CC and CXX env variables.</p>
<p>changing to bash for the configure and compile worked for me.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Alasdair</title>
		<link>http://blogs.everycity.co.uk/alasdair/2008/10/adding-mcrypt-support-to-suns-coolstack/#comment-80</link>
		<dc:creator>Alasdair</dc:creator>
		<pubDate>Sun, 08 Feb 2009 13:12:50 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.everycity.co.uk/alasdair/?p=3#comment-80</guid>
		<description>Hi Andy,

I'm afraid not - looks Sparc specific. The Sun Forums have a Webstack section and may be able to help. Unfortunately we don't have any Sparc boxes I can test things on.

Paul - You'll need GNU Autoconf and Automake. They're included on the Solaris 10 Companion DVD/CD, and have the names SFWaconf and SFWamake. If they're already installed you just need to add them to your path, by doing:

export PATH=$PATH:/opt/sfw/bin

(Note the SFW Companion CD/DVD packages install to /opt/sfw NOT /usr/sfw (at least in Zones anyway)).</description>
		<content:encoded><![CDATA[<p>Hi Andy,</p>
<p>I&#8217;m afraid not - looks Sparc specific. The Sun Forums have a Webstack section and may be able to help. Unfortunately we don&#8217;t have any Sparc boxes I can test things on.</p>
<p>Paul - You&#8217;ll need GNU Autoconf and Automake. They&#8217;re included on the Solaris 10 Companion DVD/CD, and have the names SFWaconf and SFWamake. If they&#8217;re already installed you just need to add them to your path, by doing:</p>
<p>export PATH=$PATH:/opt/sfw/bin</p>
<p>(Note the SFW Companion CD/DVD packages install to /opt/sfw NOT /usr/sfw (at least in Zones anyway)).</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Paul</title>
		<link>http://blogs.everycity.co.uk/alasdair/2008/10/adding-mcrypt-support-to-suns-coolstack/#comment-79</link>
		<dc:creator>Paul</dc:creator>
		<pubDate>Sat, 07 Feb 2009 21:18:16 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.everycity.co.uk/alasdair/?p=3#comment-79</guid>
		<description>Hi,
When running the phpize command i got this error
# /opt/coolstack/php5/bin/phpize
Configuring for:
PHP Api Version:         20041225
Zend Module Api No:      20060613
Zend Extension Api No:   220060519
Cannot find autoconf. Please check your autoconf installation and the $PHP_AUTOCONF
environment variable is set correctly and then rerun this script.</description>
		<content:encoded><![CDATA[<p>Hi,<br />
When running the phpize command i got this error<br />
# /opt/coolstack/php5/bin/phpize<br />
Configuring for:<br />
PHP Api Version:         20041225<br />
Zend Module Api No:      20060613<br />
Zend Extension Api No:   220060519<br />
Cannot find autoconf. Please check your autoconf installation and the $PHP_AUTOCONF<br />
environment variable is set correctly and then rerun this script.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Andy</title>
		<link>http://blogs.everycity.co.uk/alasdair/2008/10/adding-mcrypt-support-to-suns-coolstack/#comment-78</link>
		<dc:creator>Andy</dc:creator>
		<pubDate>Fri, 06 Feb 2009 21:53:49 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.everycity.co.uk/alasdair/?p=3#comment-78</guid>
		<description>Alasdair,

Thanks for your help so far.  I downloaded and installed SunStudio 12.  Now I can compile and install libmcrypt! Yay!

However, I am getting an error when doing the second part.

[root@shem : mcrypt]$ /opt/coolstack/php5/bin/phpize 
Configuring for:
PHP Api Version:         20041225
Zend Module Api No:      20060613
Zend Extension Api No:   220060519
NONE:0: /usr/sfw/bin/gm4: `__program__' from frozen file not found in builtin table!
autom4te: /usr/sfw/bin/gm4 failed with exit status: 1

Any ideas?

I looked at your pre-compiled packages, but unfortunately they are for Solaris x86 not Sparc.

Thanks,
Andy</description>
		<content:encoded><![CDATA[<p>Alasdair,</p>
<p>Thanks for your help so far.  I downloaded and installed SunStudio 12.  Now I can compile and install libmcrypt! Yay!</p>
<p>However, I am getting an error when doing the second part.</p>
<p>[root@shem : mcrypt]$ /opt/coolstack/php5/bin/phpize<br />
Configuring for:<br />
PHP Api Version:         20041225<br />
Zend Module Api No:      20060613<br />
Zend Extension Api No:   220060519<br />
NONE:0: /usr/sfw/bin/gm4: `__program__&#8217; from frozen file not found in builtin table!<br />
autom4te: /usr/sfw/bin/gm4 failed with exit status: 1</p>
<p>Any ideas?</p>
<p>I looked at your pre-compiled packages, but unfortunately they are for Solaris x86 not Sparc.</p>
<p>Thanks,<br />
Andy</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Alasdair</title>
		<link>http://blogs.everycity.co.uk/alasdair/2008/10/adding-mcrypt-support-to-suns-coolstack/#comment-71</link>
		<dc:creator>Alasdair</dc:creator>
		<pubDate>Sat, 31 Jan 2009 18:34:09 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.everycity.co.uk/alasdair/?p=3#comment-71</guid>
		<description>Hi Andy,

Do you have Sun Studio 12 installed? Typing "which cc" should show something along the lines of:

# which cc
/opt/SUNWspro/bin/cc

The error message is a bit obscure and not terribly helpful, not having a "cc" is the first thing that springs to mind.

Generally an up to date and patched Sun Studio 12 produces "better" binaries than gcc (or so advocates tell me). However the main reason I do it is that we package up most of the things we compile for deployment to other servers, and I prefer to not have packages depend on libgcc. Quite often if you compile something with gcc it ends up linking against /usr/sfw/lib/libgcc_s.so.1

Generally I'll try with Sun Studio first, then revert to gcc if it fails.


Murray - sorry for missing your comment. I'm not sure about your issue, if you're still having problems, drop me an email: al at everycity dot co.uk.

Cheers!</description>
		<content:encoded><![CDATA[<p>Hi Andy,</p>
<p>Do you have Sun Studio 12 installed? Typing &#8220;which cc&#8221; should show something along the lines of:</p>
<p># which cc<br />
/opt/SUNWspro/bin/cc</p>
<p>The error message is a bit obscure and not terribly helpful, not having a &#8220;cc&#8221; is the first thing that springs to mind.</p>
<p>Generally an up to date and patched Sun Studio 12 produces &#8220;better&#8221; binaries than gcc (or so advocates tell me). However the main reason I do it is that we package up most of the things we compile for deployment to other servers, and I prefer to not have packages depend on libgcc. Quite often if you compile something with gcc it ends up linking against /usr/sfw/lib/libgcc_s.so.1</p>
<p>Generally I&#8217;ll try with Sun Studio first, then revert to gcc if it fails.</p>
<p>Murray - sorry for missing your comment. I&#8217;m not sure about your issue, if you&#8217;re still having problems, drop me an email: al at everycity dot co.uk.</p>
<p>Cheers!</p>
]]></content:encoded>
	</item>
</channel>
</rss>

