Re: Is Solaris 10 a good home os?

abuse@xxxxxxxxx wrote:

*Most* can be compiled from source and even packaged as SYSV packages if
you are pedantic. :-)

Of course, you must set up proper CC, CFLAGS, LD_OPTIONS, CPPFLAGS, you
must know some tricks like -Du_intXX_t=uintXX_t etc ...

Come back to me when you build the current version of Cyrus-IMAP
(for example) with -xtarget=opteron -xarch=amd64 (or is the other
way around). Pkgmk/pkgtrans is optional, that I can do myself.

Huh! This one was nasty ... I'm administering 4 cyrus servers around,
but on Linux. I had never tried to compile it on Solaris. I had cyrus
sasl, OpenLDAP and krb5, and bdb libs on system, so I tried ... HUH! it
took me an hour, but I have compiled it in 64-bit mode WITH Sun cc and
CFLAGS you gave me. Nasty problem with berkeley DB, applied patch from
developers mailing list (not Solaris specific), problem with MIT krb5
libcom_err - recreated .et files with compile_et (again, not Solaris
specific problem), perl modules problem - read ExtUtils::MakeMaker docs
to figure out how to fix Makefile generator (to put proper LDFLAGS and
CFLAGS) (marginally Solaris problem - 64-bit problem on every 64-bit
system with this version of ExtUtils::MakeMaker), and of course couple
of Makefile editing by "perl -pi -e ..." and with vi ...

What a nasty build procedure!

It even works (master, imapd pop3d ...) without making poo poo in my
/var/coredumps ...

(mzubcic!hegel:cyrus-imapd-2.2.12)$ ldd imap/imapd
libsasl2.so.2 => /opt/lsw/lib/amd64/libsasl2.so.2
libresolv.so.2 => /lib/64/libresolv.so.2
libsocket.so.1 => /lib/64/libsocket.so.1
libnsl.so.1 => /lib/64/libnsl.so.1
libdb-4.5.so => /opt/lsw/lib/amd64/libdb-4.5.so
libssl.so.0.9.7 => /usr/sfw/lib/amd64/libssl.so.0.9.7
libcrypto.so.0.9.7 => /usr/sfw/lib/amd64/libcrypto.so.0.9.7
librt.so.1 => /lib/64/librt.so.1
libcom_err.so.3 => /opt/lsw/lib/amd64/libcom_err.so.3
libc.so.1 => /lib/64/libc.so.1
libdl.so.1 => /lib/64/libdl.so.1
libdoor.so.1 => /lib/64/libdoor.so.1
libmp.so.2 => /lib/64/libmp.so.2
libmd5.so.1 => /lib/64/libmd5.so.1
libscf.so.1 => /lib/64/libscf.so.1
libpthread.so.1 => /lib/64/libpthread.so.1
libaio.so.1 => /lib/64/libaio.so.1
libkrb5support.so.0 => /opt/lsw/lib/amd64/libkrb5support.so.0
libuutil.so.1 => /lib/64/libuutil.so.1
libm.so.2 => /lib/64/libm.so.2

U want compiled code? :-)

Speaking of which, I distinctly remember killall ignoring its
argument(s). It appears, that isn't the case anymore -- anyone
knows when that changed? Or was it some other Unix? Just curious.

Don't know this one never tried ...


--
Man is something that shall be overcome.
-- Friedrich Nietzsche
.

Relevant Pages

  • Re: Solaris 10 and KDE 3.5.10
    ... It is also only for Solaris 10. ... Your other option is to compile the ... BTW if you want to continue trying to build KDE3 then add this line to ... ~/.bashrc below the CFLAGS line: ...
    (comp.unix.solaris)
  • Re: Compiling sources for i386 or i586
    ... target machine returns i586, so I guess there is a need to compile GTM ... What is the proper way to do ...
    (comp.lang.mumps)
  • Re: more install problems
    ... > Realtek CardBus Ethernet Card Installation on Linux ... > in order to include proper .h file. ... it will be the first time I ever compile anything ... to benefit from it's declarations. ...
    (Debian-User)
  • Re: HOWTO: FreeTDS for Newbies (almost complete)
    ... it still wouldn't compile properly. ... cool -- PHP provides 3 ways to load extensions dynamically. ... So I tried changing the comma "," in $server to a colon ":". ... learning how to compile Apache with all the proper modules enabled ...
    (comp.lang.php)
  • Re: -Os breaks buildworld
    ... compile. ... Your CFLAGS line above shows -O2, yet your output below shows -Os, ... You should use CPUTYPE?= not CPUTYPE. ... from here *** Error code 1 ...
    (freebsd-stable)