BTW I also tried to install emacs v 18.x using the source code from the FSF GNU website hoping that it's age and the fact that it was probably contemporary to the VAX as a new machine and probably older than GCC 2.9.5 but that compilation also failed.
On Feb 11, 2013, at 4:42 AM, Stuart Henderson <[email protected]> wrote: > [ Note: reply-to is set to ports@ ] > > On 2013/02/10 20:37, Hany Aziz wrote: >> I have attempted to install from ports multiple programs both small and >> large >> (Emacs 21, Emacs 23, Zile, Git, Gtypist and others) they invariably fail >> during the compilation stage. > > One failure of the emacs ports is due to a compiler option being > used which isn't supported on GCC 2.95 (-fno-pie), this is no longer > used in the port in -current so stands a better chance of building, > there is definitely a problem with the X flavours though so you'll > probably need to use FLAVOR=no_x11. > >> install of xemacs-sumo (NOT MULE) failed though it does appear to have >> installed the package's man and info pages. > > The description in COMMENT is not entirely clear but this looks a > bunch of .el files and some supporting files. It does not include > binaries which are in the package which would be produced by > ports/editors/xemacs if it built. There are two versions of xemacs available for installation. One includes MULE (MULti-lingual Enhancement to GNU Emacs) and one does not. I have tried to install the one without the MULE features since English is the only language I use. > >> [demime 1.01d removed an attachment of type application/octet-stream which >> had a name of vim_2.log] >> [demime 1.01d removed an attachment of type application/octet-stream which >> had a name of emacs21.error.log] >> [demime 1.01d removed an attachment of type application/octet-stream which >> had a name of emacs23_make.log] > (etc) > > Most of the mailing lists do not permit attachments. (also separating > out stderr from stdout is just going to make it hard to match up errors > with normal output..) > > For some things in ports, there will just be small fixes needed to > for vax (one of the most common problems is mixed code and declarations, > sometimes it's absolutely rife in the code but other times it just needs > a few lines reordering).. but for many things, between the low memory, > no shared libraries and gcc 2.95, it will be a major challenge. > > That said fixing a few common ports will get a lot more building.. e.g. > > gettext: > > cc -DHAVE_CONFIG_H -I. -I.. -I.. -I../gnulib-lib -I../gnulib-lib -I../intl > -DIN_GETTEXT_TOOLS_LIBGREP=1 -I/usr/local/include -O2 -pipe -c regex.c > In file included from regex.c:66: > regex_internal.h:40: warning: `__libc_lock_define' redefined > ../config.h:2592: warning: this is the location of the previous definition >
