Thread View: gnu.bash.bug
2 messages
2 total messages
Started by Mitch Wright
Sat, 29 Aug 1992 23:09
BASH Under Solaris 2.0 ???
Author: Mitch Wright
Date: Sat, 29 Aug 1992 23:09
Date: Sat, 29 Aug 1992 23:09
10 lines
772 bytes
772 bytes
This isn't really a bug, but I didn't see a discussion group... Anyone have bash version 1.12 running under Solaris 2.x? Just letting the make figure things out makes it want to build it as if it were running unders SunOS4. Obviously that fails miserably. Anyway, before I put much effort into this I'd like to know if anyone has already made the effort. ~mitch mitch@cirrus.com
Re: BASH Under Solaris 2.0 ???
Author: Dave Brennan
Date: Sat, 05 Sep 1992 10:00
Date: Sat, 05 Sep 1992 10:00
46 lines
2277 bytes
2277 bytes
I just took a quick pass at building 1.12 under SunOS 5.0 (ie: USG V.4). Since I don't have a lot of time to mess with this I operated in quick port/hack mode. Because I'm not sure what cc or cpp defines I replaced the old sparc definitions in machines.h with: # define M_OS USG # define SunOS4_SYSDEP_CFLAGS -DUSGr4 # define HAVE_SYS_SIGLIST # define HAVE_VFPRINTF # define VOID_SIGHANDLER # define HAVE_ALLOCA # define HAVE_STRERROR # define HAVE_GETGROUPS Here's the problems I encountered: * For some reason the PPROPMT and SPROMPT macros defined on the "cc" line got substituted without the closing quote. For now I just hacked up the "cc -E" output so that it would compile. I don't know why, but somewhere the quote was getting eaten. I'd like to know why, but don't have time to chase it down. * All instances of the "ar" command in the library Makefiles use the depreciated 'l' flag which isn't supported anymore. * readline.c didn't compile at first because /usr/include/sys/reg.h defines "PC" as "(1)" and PC is used as a variable. I just threw #ifdef PC / #undef PC in readline.c to fix it. * Trying to link -Bstatic caused cc to look for libaio.a, which was missing. Removing -Bstatic fixed this. * globbing is messed up and always seems to chop the first 2 characters off file names. Unfortunately this makes bash highly unusable. If anyone else has had any luck or has time to track this last problem down you'd be doing everyone a favor. Please send me mail or post if you need or have more info. -- Dave Brennan HaL Computer Systems brennan@hal.com (512) 794-2855 Visit the Emacs Lisp Archive: archive.cis.ohio-state.edu:pub/gnu/emacs
Thread Navigation
This is a paginated view of messages in the thread with full content displayed inline.
Messages are displayed in chronological order, with the original post highlighted in green.
Use pagination controls to navigate through all messages in large threads.
Back to All Threads