Are you referring to the precompiled binaries or to the ports that will compile and is there another version of OpenBSD that will allow more packages to install or compile on the Vax? In other words can I install another version of openbsd and have less issues? All I really want is gcc, gdb, emacs and preferably git. Give me those and I am happy.
Thanks. Sincerely, Hany. On Feb 15, 2013, at 11:24 AM, Stuart Henderson <[email protected]> wrote: > On 2013/02/15 15:38, Jérémie Courrèges-Anglas wrote: >> >> Thanks for your report, however I find this rather weird... >> Excerpt from emacs23_make.log: > > gperf built ok on vax in the last -current package snapshot. > > emacs21,no_x11 fails reliably during link: > > cc -nostartfiles -L/usr/local/lib -o temacs pre-crt0.o > /usr/lib/crt0.o dispnew.o frame.o scroll.o xdisp.o xmenu.o window.o > charset.o coding.o category.o ccl.o cm.o term.o xfaces.o emacs.o > keyboard.o macros.o keymap.o sysdep.o buffer.o filelock.o insdel.o marker.o > minibuf.o fileio.o dired.o filemode.o cmds.o casetab.o casefiddle.o > indent.o search.o regex.o undo.o alloc.o data.o doc.o editfns.o callint.o > eval.o floatfns.o fns.o print.o lread.o abbrev.o syntax.o > unexsunos4.o mocklisp.o bytecode.o process.o callproc.o region-cache.o > sound.o atimer.o doprnt.o strftime.o intervals.o textprop.o > composite.o md5.o terminfo.o lastfile.o gmalloc.o ralloc.o vm-limit.o > -lossaudio -lncurses `cc -print-libgcc-file-name` -lm > -lc `cc -print-libgcc-file-name` > <<snip 32 lines of 'XX is often misused'>> > /tmp//ccXwptf3.o: Definition of symbol `___CTOR_LIST__' (multiply defined) > /tmp//ccXwptf3.o: Definition of symbol `___DTOR_LIST__' (multiply defined) > <<snip another 6 lines>> > emacs.o: Definition of symbol `___CTOR_LIST__' (multiply defined) > emacs.o: Definition of symbol `___DTOR_LIST__' (multiply defined) > <<snip another 26 lines>> > collect2: ld returned 1 exit status > > > > it's pretty sad that only ~320 packages built (and several of these > are just "recompress a bunch of files for things which aren't useful on > vax anyway"). weird too though, there are various things which should > have worked which didn't get built (e.g. math/moo). or even attempted, > from the looks of the dpb logs..? > > for the broken ports, actually fixing things on vax is so time consuming > that the only way it's going to happen is if somebody who really wants > it does the work. running the builds, working out which failures are > even worth looking at, fixing, sending out diffs, etc. and a lot of > the people who can do that work are already quite busy enough... > >
