BASH BASH BASH BASH BASH BASH BASH BASH BASH BASH

BASH BASH BASH BASH BASH BASH BASH BASH BASH BASH

Post by Neil J. McRa » Mon, 06 Jun 1994 20:18:40



Is there a proper fixed bash on any of the FTP sites out there?

I know there bash is on the usual sites but I don't know if they are
bugged or not :(

Regards,

Neil.

--


------------------------------------| Edinburgh, EH14 2DE, United Kingdom
**Domino: There`s nothing you can do when you`re the next in line: Domino**

 
 
 

BASH BASH BASH BASH BASH BASH BASH BASH BASH BASH

Post by n.. » Sat, 11 Jun 1994 00:57:57


: Ce brave Neil J. McRae ecrit:
:
:
:
[deleted...]
:
: Get the GNU source bash-1.14.tar.gz  (just released a few days ago).
:
: Type "make".
: You have a working bash.
:
: (Remove the -g option in the CFLAGS or you will get a big binary...)
:
: About bugs, better read gnu.bash.bugs; I have been running it for 2 days
: and no problem on my news shell scripts at least.

I grabbed bash-1.14 source from "prep.ai.mit.edu" and built it
on a box running Linux 1.0.4 (MCC 1.0+).  The resulting binaries
are HUGE, see (below); captured output of "ldd", "ls -l",
and "file":

statically linked
-rwx--x--x   2 root     root      1514205 Jun  8 09:18 bash
bash:   Linux/i386 OMAGIC demand paged executable not stripped

I found no '-g' switch (debug) in the 'Makefile'.

What did I do wrong?

BTW: I couldn't even find "CFLAGS", or "LDFLAGS" :-(.

Thanks.


 
 
 

BASH BASH BASH BASH BASH BASH BASH BASH BASH BASH

Post by the MOST SIGNIFICANT b » Sat, 11 Jun 1994 01:59:47



>I grabbed bash-1.14 source from "prep.ai.mit.edu" and built it
>on a box running Linux 1.0.4 (MCC 1.0+).  The resulting binaries
>are HUGE, see (below); captured output of "ldd", "ls -l",
>and "file":

        [...]

Quote:>I found no '-g' switch (debug) in the 'Makefile'.

        Look in the file cpp-Makefile, and search for -g
--
Maurice S. Barnum               ==    I speak for me, not my employer.



 
 
 

BASH BASH BASH BASH BASH BASH BASH BASH BASH BASH

Post by Ron Watki » Sat, 11 Jun 1994 02:57:13


You can also 'strip' the resulting executable to shrink it down. It's just
as effective as removeing the -g switch as the -g switch just puts info for
the debugging trace in the executable and strip will remove that. So you
can leave the -g in the cpp-Makefile and just strip it after it's built. You
will get a substantially reduced file size.

                        Ron W.
--

931 Gould-Simpson                            /            /____/     /
University of Arizona                       /            /          /
Tucson AZ. 85721 -- (602) 621-8606         (____ unar & / lanetary (____ ab.

 
 
 

BASH BASH BASH BASH BASH BASH BASH BASH BASH BASH

Post by Jeremy Bett » Sat, 11 Jun 1994 06:51:35



>You can also 'strip' the resulting executable to shrink it down. It's just
>as effective as removeing the -g switch as the -g switch just puts info for
>the debugging trace in the executable and strip will remove that. So you
>can leave the -g in the cpp-Makefile and just strip it after it's built. You
>will get a substantially reduced file size.

This is not quite true.  It will still be statically linked, because -g
implies -static.  If you want the smallest code, compile without -g and then
strip it afterwards. (or compile with the -s option.)

The -N option will make the program even smaller, but not demand-loaded, so
it is a bad idea for bash. For things like fsck, or loadkeys it is useful.
--
Jeremy Bettis   -*-   Jerbo Jehoshaphat   -*-   University of Nebraska


Running Linux -- The Free Unix for i386/i486/Pentium machines. Ask me how.

 
 
 

1. Bashing bash (Was Re: bash or user error with set -e and subshells)

Hi there,

This thread was initially about whether it is a bug or a feature, that
bash pedanticly sticks to the POSIX-sufficient requirement that 'set -e'
exit only after getting a nonzero status from a "simple command", while
the original Bourne makes a very useful generalization to "any child"
(including subshells).

I'm still interested in the answer: could some kind person please
address this issue specifically, without digressing to the (otherwise
exciting) millions of ways of avoiding a subshell, or good/bad reasons
to use 'set -e' ?...

What's the rationale after all ? The generalization is trivial to
implement, while the bash behavior has already consumed many
person-months in debugging (as witnessed by groups.google.com) !

Please...

TIA,

-Alex

2. Build problem in 2.5.61/sparc

3. Bash calls TCL, TCL calls Bash, 2nd Bash never reads input

4. VPN and isakmp Config error ver2.8

5. Bash/CGI - - HTML call to Bash script

6. help debugging

7. difference in behaviour of bash-2.0 from bash-1.14.7

8. Terminal input?

9. (patch for Bash) Bash with embedded Python

10. co-processes and bash (ksh does it, can bash?)

11. Stupid BASH BASH EXPORT PS1 and path to X Question

12. changing bash to "bash -noprofile"

13. Bash: How to invoke executable for bash with bashrc env setup?