Messages in this thread | | | Date | Mon, 31 Mar 1997 09:27:20 -0500 (EST) | From | "Richard B. Johnson" <> | Subject | Re: ld.so 1.9.1 and glibc 2.0.1 |
| |
On 31 Mar 1997, Ulrich Drepper wrote:
> > I tried to send in a report using the "%*^#%^#(8~#" script provided, > > and it uses Emacs!! Emacs on this machine is broken and seg-faults. > > I had to modify the script to use vi. Then, after all that work, > > I never even got a reply. > > You certainly got a reply. But even if you would not have seen any, > what do you expect? I cannot sit 24 hours here and answer questions.
You went to all the bother to create a mail script to provide a standard method of reporting problems to minimize your workload. Normally, one would provide an "automated" reply (using vacation perhaps) so that a respondent knows that the message got through. This has been normal practice from gnu developers for many years. Cool down. I thank you for your reply.
> emacs you haven't told it otherwise. If you don't use Emacs, you > should always set the environment variable EDITOR to vi or whatever > you use. If you don't know about this variable better start learning > about setups of Unix environment. Many scripts and programs depend on > this variable.
This is my environment. There is an "EDITOR=" in there somewhere. These environment variables are set from /etc/profile, rather than individual profiles in user accounts. This keeps everything uniform.
BASH=/bin/bash BASH_VERSION=1.14.5(1) COLUMNS=80 DISPLAY=:0 EDITOR=/usr/bin/vim EUID=0 GNUHELP=/usr/local/lib/gnuplot/gnuplot.gih HISTFILE= HISTFILESIZE=0 HISTSIZE=500 HOME=/root HOSTTYPE=i386 IFS=
LANG=en_US.88591 LESS=-MM LIB=/usr/X11R6/lib:/usr/X11/lib LINES=25 LOGNAME=root MAIL=/var/spool/mail/root MAILCHECK=60 MANPATH=/usr/man:/usr/X11/man:/usr/openwin/man MINICOM=-c on NLSPATH=/usr/man:/usr/X11/man:/usr/openwin/man OPENWINHOME=/usr/openwin OPTERR=1 OPTIND=1 OSTYPE=Linux PATH=/sbin:/bin:/usr/sbin:/usr/bin:/usr/local/bin:/usr/X11R6/bin:/usr/bin/X11:/usr/TeX/bin:/usr/openwin/bin:/usr/games:.:/home/users/root/tools PPID=1 PRINTER=print PS1=# PS2=> PS4=+ PWD=/root SHELL=/bin/bash SHLVL=1 TERM=vt100-am TERMCAP=vt100|vt100-am|dec vt100 (w/advanced video):am:mi:ms:xn:xo:co#80:it#8:li#25:vt#3:@8=\EOM:DO=\E[%dB:K1=\EOq:K2=\EOr:K3=\EOs:K4=\EOp:K5=\EOn:LE=\E[%dD:RI=\E[%dC:UP=\E[%dA:ac=\140\140aaffggjjkkllmmnnooppqqrrssttuuvvwwxxyyzz{{||}}~~:ae=^O:as=^N:bl=^G: cb=\E[1K:cd=\E[J:ce=\E[K:cl=\E[H\E[J:cm=\E[%i%d;%dH:cr=^M:cs=\E[%i%d;%dr:ct=\E[3g:do=^J:eA=\E(B\E)0:ho=\E[H:k0=\EOy:k1=\EOP:k2=\EOQ:k3=\EOR:k4=\EOS:k5=\EOt:k6=\EOu:k7=\EOv:k8=\EOl:k9=\EOw:k;=\EOx:kb=^H:kd=\EOB:ke=\E[?1l\E>:kl=\EOD:kr=\EOC:ks=\E[?1h\E=:ku= \EOA:le=^H:mb=\E[5m:md=\E[1m:me=\E[m\017:mr=\E[7m:nd=\E[C:is=\E<\E)0:r2=\E>\E[?3l\E[?4l\E[?5l\E[?7h\E[?8h:rc=\E8:sc=\E7:se=\E[m:sf=^J:so=\E[1;7m:sr=\EM:st=\EH:ta=^I:ue=\E[m:up=\E[A:us=\E[4m: UID=0 _=set notify=1
> > Third, I look at your problem but I have no clue how this can ever be > possible. Nobody reported something similar and compiling glibc > several hundred of times myself never showed this as well. I guess > it's a broken installed gcc.
This is the output from:
# gcc --print-file-name include /usr/lib/gcc-lib/i586-unknown-linux/2.7.2/include
# gcc --print-file-name lib lib
The 'C' compiler works, and was installed about 6 months ago by typing 'make install' after a sucessful complile. There is nothing strange about this system, no custom things whatsoever.
There __are__ some custom tools in my path.
The names are: Echo MAIL chkm com discard from monitor mymail noguest nolog pattern recv rootlog unix2world world2unix
These should not conflict with anything used to compile or link. There may be a symlink in /usr/lib, /usr/local/lib, /lib....etc that is confusing your build. If so, it is something that a standard installation of 'something' installed, that could cause problems in the future for others. I will check into this and I will report what I find. It was early in the morning, i.e., 2:00 AM when I looked at your script to send mail. I think that there is a variable missing somewhere which prevented bash from executing the script properly.
It doesn't know what "VISUAL" is. This is not in my environment, and does not appear to have been set in the script. Although I am relatively new at Unix (only 15 of the 20 years it's been around) and I'm learning new things you are "supposed" to do practically every day, what is the "VISUAL" environment to which your script refers?
# If they don't have a preferred editor set, then use if [ -z "$VISUAL" ]; then if [ -z "$EDITOR" ]; then EDIT=vi else EDIT="$EDITOR" fi else EDIT="$VISUAL" fi
Cheers, Dick Johnson -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Richard B. Johnson Project Engineer Analogic Corporation Voice : (508) 977-3000 ext. 3754 Fax : (508) 532-6097 Modem : (508) 977-6870 Ftp : ftp@boneserver.analogic.com Email : rjohnson@analogic.com, johnson@analogic.com Penguin : Linux version 2.1.30 on an i586 machine (66.15 BogoMips). Warning : I read unsolicited mail for $350.00 per hour. Supply billing address. -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
| |