software request on solaris-x86: libgc and emacs

[cjpinon_solaris-x86]

Hi,

i. Insofar as libgc is available for solaris-x86, would it be possible to install it? (See http://www.hboehm.info/gc/ )

ii. It would be great to get emacs as well.

Thanks,
C.

[zoli]

Hi,

i. Insofar as libgc is available for solaris-x86, would it be possible to install it?

gc does not build on this host... but you are welcome to fix the port - or myabe it is enough just ot use a different compliler.
This far I have come:

Code: Select all

root@solaris-x86:~/gc/bdwgc#
root@solaris-x86:~/gc/bdwgc# autoreconf -vif
autoreconf: Entering directory `.'
autoreconf: configure.ac: not using Gettext
autoreconf: running: /opt/csw/bin/aclocal --force -I m4
autoreconf: configure.ac: tracing
autoreconf: configure.ac: adding subdirectory libatomic_ops to autoreconf
autoreconf: Entering directory `libatomic_ops'
autoreconf: running: /opt/csw/bin/libtoolize --copy --force
libtoolize: putting auxiliary files in `.'.
libtoolize: copying file `./ltmain.sh'
libtoolize: putting macros in AC_CONFIG_MACRO_DIR, `m4'.
libtoolize: copying file `m4/libtool.m4'
libtoolize: copying file `m4/ltoptions.m4'
libtoolize: copying file `m4/ltsugar.m4'
libtoolize: copying file `m4/ltversion.m4'
libtoolize: copying file `m4/lt~obsolete.m4'
autoreconf: running: /opt/csw/bin/autoconf --force
autoreconf: running: /opt/csw/bin/autoheader --force
autoreconf: running: /opt/csw/bin/automake --add-missing --copy --force-missing
configure.ac:14: installing './compile'
configure.ac:5: installing './config.guess'
configure.ac:5: installing './config.sub'
configure.ac:8: installing './install-sh'
configure.ac:8: installing './missing'
src/Makefile.am: installing './depcomp'
parallel-tests: installing './test-driver'
autoreconf: Leaving directory `libatomic_ops'
libtoolize: putting auxiliary files in `.'.
libtoolize: copying file `./ltmain.sh'
libtoolize: putting macros in AC_CONFIG_MACRO_DIR, `m4'.
libtoolize: copying file `m4/libtool.m4'
libtoolize: copying file `m4/ltoptions.m4'
libtoolize: copying file `m4/ltsugar.m4'
libtoolize: copying file `m4/ltversion.m4'
libtoolize: copying file `m4/lt~obsolete.m4'
autoreconf: Leaving directory `.'
root@solaris-x86:~/gc/bdwgc# automake --add-missing
root@solaris-x86:~/gc/bdwgc# ./configure
checking build system type... i386-pc-solaris2.11
checking host system type... i386-pc-solaris2.11
checking target system type... i386-pc-solaris2.11
checking GC version numbers... major=7 minor=5                 micro=0
checking for a BSD-compatible install... /usr/bin/ginstall -c
checking whether build environment is sane... yes
checking for a thread-safe mkdir -p... /usr/bin/gmkdir -p
checking for gawk... gawk
checking whether make sets $(MAKE)... yes
checking whether make supports nested variables... yes
checking whether to enable maintainer-specific portions of Makefiles... no
checking for style of include used by make... GNU
checking for gcc... no
checking for cc... cc
checking whether the C compiler works... yes
checking for C compiler default output file name... a.out
checking for suffix of executables...
checking whether we are cross compiling... no
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 whether cc understands -c and -o together... yes
checking dependency style of cc... none
checking for g++... no
checking for c++... no
checking for gpp... no
checking for aCC... no
checking for CC... CC
checking whether we are using the GNU C++ compiler... no
checking whether CC accepts -g... yes
checking dependency style of CC... none
checking dependency style of cc... none
checking how to print strings... print -r
checking for a sed that does not truncate output... /usr/bin/gsed
checking for grep that handles long lines and -e... /usr/bin/ggrep
checking for egrep... /usr/bin/ggrep -E
checking for fgrep... /usr/bin/ggrep -F
checking for non-GNU ld... /usr/bin/ld
checking if the linker (/usr/bin/ld) is GNU ld... no
checking for BSD- or MS-compatible name lister (nm)... /usr/bin/nm -p
checking the name lister (/usr/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 "+="... yes
checking how to convert i386-pc-solaris2.11 file names to i386-pc-solaris2.11 format... func_convert_file_noop
checking how to convert i386-pc-solaris2.11 file names to toolchain format... func_convert_file_noop
checking for /usr/bin/ld option to reload object files... -r
checking for objdump... no
checking how to recognize dependent libraries... pass_all
checking for dlltool... no
checking how to associate runtime and link libraries... print -r --
checking for ar... ar
checking for archiver @FILE support... no
checking for strip... strip
checking for ranlib... ranlib
checking command to parse /usr/bin/nm -p output from cc object... ok
checking for sysroot... no
checking for mt... mt
checking if mt is a manifest tool... no
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... yes
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/bin/ld) supports shared libraries... yes
checking dynamic linker characteristics... solaris2.11 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 how to run the C++ preprocessor... CC -E
checking whether the CC linker (/usr/bin/ld) supports shared libraries... yes
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... yes
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/bin/ld) supports shared libraries... yes
checking dynamic linker characteristics... solaris2.11 ld.so
checking how to hardcode library paths into programs... immediate
checking for thread model used by GCC... no
checking for inline... inline
checking for xlc... no
checking for dlopen in -ldl... yes
checking whether to build shared libraries... yes
checking which machine-dependent code should be used...
checking whether Solaris gcc optimization fix is necessary... no
checking for dladdr... yes
checking sys/dg_sys_info.h usability... no
checking sys/dg_sys_info.h presence... no
checking for sys/dg_sys_info.h... no
./configure: line 16875: syntax error at line 16877: `(' unexpected

ii. It would be great to get emacs as well.

Done.

[cjpinon_solaris-x86]

Hi again,

gc does not build on this host... but you are welcome to fix the port - or myabe it is enough just ot use a different compliler.

Again, thanks for trying.

Done.

Unfortunately, there seems to be a linking problem (is libXaw installed?):

Code: Select all

$ emacs
ld.so.1: emacs-24.3-athena: fatal: libXaw.so.5: open failed: No such file or directory
ld.so.1: emacs-24.3-athena: fatal: relocation error: file /opt/csw/bin/emacs-24.3-athena: symbol scrollbarWidgetClass: referenced symbol not found
Killed


Thanks,
C.

[zoli]

I am sorry,
you are right... I just installed and never tried to start emacs - hahaha I am vi guy, it normally never happes to me to need to start emacs - but I did it for you, and indeed the libXaw.so.5 library was missing. After installing that library, your emacs works as it should.

Enjoy.

[cjpinon_solaris-x86]

you are right... I just installed and never tried to start emacs - hahaha I am vi guy, it normally never happes to me to need to start emacs - but I did it for you, and indeed the libXaw.so.5 library was missing. After installing that library, your emacs works as it should.

Hi,

Thanks, yes, emacs works now, but I'm afraid that I have a further problem: X forwarding doesn't seem to work. My guess is that no X server is installed -- is this the case? For example, xterm isn't found:

Code: Select all

$ type xterm
-bash: type: xterm : non trouvé


Would you have an idea about this?

Thanks,
C.

[zoli]

xterm is not part of the X server... and indeed it was not installed (I did it now)

X11 forwarding is enabled in the sshd server.
Please, try to start your ssh session with enabled X11 forwarding (-X in the command line) or a special option in putty for example.

[cjpinon_solaris-x86]

xterm is not part of the X server... and indeed it was not installed (I did it now)

X11 forwarding is enabled in the sshd server.
Please, try to start your ssh session with enabled X11 forwarding (-X in the command line) or a special option in putty for example.

Hi, yes, all of this is clear to me, but what I don't understand is why X11 forwarding works for me on polarhome's solaris machine but not on solaris-x86. I get this message when I log on to solaris-x86:

Code: Select all

X11 forwarding request failed on channel 0

Does X11 forwarding work for you (as an ordinary user) on solaris-x86? Or for any other solaris-x86 user that reads this?

(Just a thought: after turning on X11 forwarding, did you restart sshd?)

C.

[zoli]

Right... the X11 forwarding did not work... and it took me few hours before I realized what is the problem and fixed.
On Solaris 11- the X needs to run in order to be able to export the session - therefore I was forced to install the solaris-desktop. Let the server start into the GUI and just then the sshd was satisfied with the local X security.

You are welcome.
It works now - at least for me
PS: use -Y instead of -X option in order to supress the "Warning: untrusted X11 forwarding setup failed: xauth key data not generated" warning.

[cjpinon_solaris-x86]

Right... the X11 forwarding did not work... and it took me few hours before I realized what is the problem and fixed.
On Solaris 11- the X needs to run in order to be able to export the session - therefore I was forced to install the solaris-desktop. Let the server start into the GUI and just then the sshd was satisfied with the local X security.

You are welcome.
It works now - at least for me
PS: use -Y instead of -X option in order to supress the "Warning: untrusted X11 forwarding setup failed: xauth key data not generated" warning.

Thanks, yes, it seems to work now for me as well. And suddenly the version of emacs is newer than the version that you installed several days ago.

By the way, I don't get a warning with the -X option (of course, -Y works as well).

C.

[zoli]

I am glad we sort out this issue.
It took me a while, but Solaris 11 is so very much different than anything else, that it was my pleasure to work with it. It is a real perl with its pkg and ZFS tools.

[cjpinon_solaris-x86]

It took me a while, but Solaris 11 is so very much different than anything else, that it was my pleasure to work with it. It is a real perl with its pkg and ZFS tools.

I hardly know Solaris 11, but when I used earlier versions of Solaris in the past, I always liked them.

It's sad that Sun no longer exists; it's also sad that Oracle killed OpenSolaris.

C.

[zoli]

Hi,

It's sad that Sun no longer exists; it's also sad that Oracle killed OpenSolaris.

Yes, such company purchases always reshape the World around us. Remember when Compaq bought Digital? This is the same, just sightly better, because Oracle knows a lot about software development. Java, Solaris, MySQL are still alive and have a product strategy (that we might not agree - but exist).

[cjpinon_solaris-x86]

Yes, such company purchases always reshape the World around us. Remember when Compaq bought Digital? This is the same, just sightly better, because Oracle knows a lot about software development. Java, Solaris, MySQL are still alive and have a product strategy (that we might not agree - but exist).

True, Solaris seems to be in a better situation at the moment than (say) OpenVMS, yet it doesn't seem to be a priority of Oracle to "push" Solaris (in contrast to Oracle Linux), but maybe I'm mistaken about this.

As for OpenVMS, I'm impressed that polarhome has it running on three machines. But I imagine that the days are now numbered for the hardware Alpha and VAX. It'll become increasingly difficult to repair/replace Alpha or VAX, won't it?

OpenVMS may have a future, but we'll see ( http://www.osnews.com/comments/27871 ).

C.

[zoli]

Hi,

As for OpenVMS, I'm impressed that polarhome has it running on three machines. But I imagine that the days are now numbered for the hardware Alpha and VAX. It'll become increasingly difficult to repair/replace Alpha or VAX, won't it?

Yes, you are right. The Alpha and VAX hardware is very hard to find, they are expencive and the performance is low compared with the modern hardware. polarhome still owns few of those old beasts, but the online available servers are running on simulators to cut the electricity costs. VAX on SIMH and alpha on alphavm-free both on a Linux host.

OpenVMS may have a future, but we'll see ( http://www.osnews.com/comments/27871 ).

Hmmm http://vmssoftware.com/ is, indeed some kind of future for OpenVMS - but what really is needed a radically new product management strategy. It is not enough to satisfy the old ethusiasts and customers. OpenVMS needs to fight its own marketshare with the current server competition - and for that this old team has failed already - several times earlier too.

What is needed:
- improved GNV
- make it easier to port to VMS
- improve the java, perl, bash development environmnets
- make VMS more unix like (for beginners)
- skip licences - make it free and available
- lock the new generation

... I am aware that all this will make VMS less VMS like, but the OS underneath will be the same providing performance and stability - and just the shell around needs to be familiar for the rest of the World.

[cjpinon_solaris-x86]

Yes, you are right. The Alpha and VAX hardware is very hard to find, they are expencive and the performance is low compared with the modern hardware. polarhome still owns few of those old beasts, but the online available servers are running on simulators to cut the electricity costs. VAX on SIMH and alpha on alphavm-free both on a Linux host.

I see. Yes, this makes sense; in this way, you don't have to worry about replacing Alpha or VAX hardware if something fails.

Hmmm http://vmssoftware.com/ is, indeed some kind of future for OpenVMS - but what really is needed a radically new product management strategy. It is not enough to satisfy the old ethusiasts and customers. OpenVMS needs to fight its own marketshare with the current server competition - and for that this old team has failed already - several times earlier too.

What is needed:
- improved GNV
- make it easier to port to VMS
- improve the java, perl, bash development environmnets
- make VMS more unix like (for beginners)
- skip licences - make it free and available
- lock the new generation

... I am aware that all this will make VMS less VMS like, but the OS underneath will be the same providing performance and stability - and just the shell around needs to be familiar for the rest of the World.

I agree with you completely, but I'm also doubtful that most of this will happen in practice. There are many who say that OpenVMS is effectively dead already, and that no one in their right mind would choose OpenVMS for a new site/installation. It's really the old sites/installations that depend on OpenVMS that keep it alive, but then just barely -- it's more a question of support contracts than innovation. And, as far as I can tell, HP has lost interest in OpenVMS.

When I start thinking more about the comparison between Solaris and OpenVMS, Solaris is in great shape by comparison, despite any doubts about the future of Solaris.

C.

[zoli]

When I start thinking more about the comparison between Solaris and OpenVMS, Solaris is in great shape by comparison, despite any doubts about the future of Solaris.

hahaha you see?
...so do not complain

[cjpinon_solaris-x86]

hahaha you see?
...so do not complain

No more complaints from me provided that polarhome officially advocates the use of Viper mode on Emacs instead of that other editor!

(http://www.gnu.org/software/emacs/manua ... viper.html )

I think that I'll go hide now.