Re: bash 3.1 on Solaris 9

2006-07-18 Thread Bob Proulx
Chris,

Please keep replies to the mailing list so that others may participate
and the answers will be available for those who search the archives
later.  Also I am actually traveling right now and so I will be really
slow responding for a while.

Cheltenham, Christopher J wrote:
> Well I tried to compile it myself but I kept getting errors with gcc.
> Something about it cannot create executables.

Ouch.  That message is being produced from one of the early autoconf
tests.  You would need to debug why your compiler installation is not
working first because obviously a working C compiler is required.

> The third part is Sun Freeware which I always thought was you guys
> anyway but apparently not.

I am not familiar with Sun Freeware.  Others on the mailing list might
be however.  This is the bash mailing list at gnu.org.  It is
concerned with the development of the bash shell.

  http://www.gnu.org/software/bash/

Bash is one of the components of the GNU operating system.

  http://www.gnu.org/

Ports of software from the GNU Project are often made to other
platforms.  But usually not distributed as binaries from gnu.org.  I
will infer, perhaps incorrectly, that Sun Freeware is one of those
folks porting software to Sun.  If so then you would probably have
better luck contacting them directly with your problem.

Bob


Cheltenham, Christopher J wrote:
> Well I tried to compile it myself but I kept getting errors with gcc.
> Something about it cannot create executables. The third part is Sun
> Freeware which I always thought was you guys anyway but apparently not.
> 
> 
> Thanks
> =
> Chris Cheltenham  
> Computer Specialist
> Campbell Library @ Rowan University  
> Glassboro, NJ 
> 856-256-4979   
> =
> 
> -Original Message-
> From: Bob Proulx [mailto:[EMAIL PROTECTED] 
> Sent: Friday, July 14, 2006 1:32 AM
> To: Cheltenham, Christopher J
> Cc: bug-bash@gnu.org
> Subject: Re: bash 3.1 on Solaris 9
> 
> Cheltenham, Christopher J wrote:
> > What can I do for this error?
> > 
> > ld.so.1: bash: fatal: libiconv.so.2: open failed: No such file or
> > directory
> > Killed
> 
> You apparently got a precompiled binary from some third party.  That
> binary is using a shared library that it did not include.  Probably at
> the same place that you got the bash binary you would also find the
> libiconv shared library.  Install it too.  Repeat as needed.
> 
> Or you could pull the source code to bash and compile it yourself
> which would build it without that dependency.  The GNU project
> generally distributes source code.  A whole infrastructure of third
> parties have developed around compiling the source code and
> distributing it.  But really anyone can compile the code and this is
> encouraged.
> 
> Bob
> 


___
Bug-bash mailing list
Bug-bash@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-bash


Re: bash 3.1 on Solaris 9

2006-07-18 Thread Hugh Sasse
On Tue, 18 Jul 2006, Bob Proulx wrote:

> Chris,
[...]
> > The third part is Sun Freeware which I always thought was you guys
> > anyway but apparently not.
> 
> I am not familiar with Sun Freeware.  Others on the mailing list might

http://sunfreeware.com/

> I will infer, perhaps incorrectly, that Sun Freeware is one of those
> folks porting software to Sun.  If so then you would probably have

Yes.
> 
> Cheltenham, Christopher J wrote:
> > Well I tried to compile it myself but I kept getting errors with gcc.
[...]
> > -Original Message-
> > From: Bob Proulx [mailto:[EMAIL PROTECTED] 
> > Sent: Friday, July 14, 2006 1:32 AM
[...]
> > Cheltenham, Christopher J wrote:
> > > What can I do for this error?
> > > 
> > > ld.so.1: bash: fatal: libiconv.so.2: open failed: No such file or
> > > directory

So you want to look at:

http://sunfreeware.com/programlistsparc9.html#libiconv

specifically, I think.  IIRC you are on sparc not x86.

HTH
Hugh


___
Bug-bash mailing list
Bug-bash@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-bash


message: ^Z: nothing to suspend

2006-07-18 Thread Dan Jacobson
Maybe bash should print a message when one hits ^Z but there is
nothing to suspend:

$ bla&
^Z
bash: useless hit of ^Z
or
bash: ^Z: nothing to suspend


___
Bug-bash mailing list
Bug-bash@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-bash


mention kill 0

2006-07-18 Thread Dan Jacobson
The kill(1) man page doesn't mention "kill 0".
/bin/kill 0 #scripts proceed no further
The bash man page mentions kill 0, but not in its main kill paragraph.
The bash man page doesn't mention kill -1.
The bash "help kill" bulrb doesn't mention kill 0 or -1.
The kill(1) man page, as of
procps:
  Installed: 1:3.2.6-2.2
still looks a mess:
   Name Num   ActionDescription
   ()   
   ()#very long wrapped line

   0  0   n/a   exit code indicates if a signal may be sent


___
Bug-bash mailing list
Bug-bash@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-bash