| All Forums |
Register |
Login |
Search |
Subscriptions |
My Profile |
Inbox |
| Tool Warehouse |
FAQs |
Resources |
Help |
Member List |
Address Book |
Logout |
|
|
bash filename globbing take 2
|
Logged in as: Guest |
| Users viewing this topic: none |
|
Login  |
|
|
 bash filename globbing take 2 - Mar. 24, '06, 12:06:37 PM
|
|
|
woehlkmp
Posts: 102
Status: offline
|
I think I'm having a similar problem as < http://www.interopsystems.com/tools/tm.aspx?m=7808&mpage=1&key=bash%2cglobbingẀ >... Namely, I can't get 'ls *' (or any globbing, it looks like) to work on any local directory. For example, if I do 'echo *', I get '*'. The funny thing is that it works just fine on NFS-mounted drives.
I'm using a copy of bash 3.0 that I built from the sources from this website (because I wanted 64-bit) To get this to work I had to get a new config.guess and use 'CC=cc' (because gcc is 32-bit and breaks 'ar'), and then I had some problems with (u)intmax_t being multiply defined in snprint.c which I fixed by adding '#define _(U)INTMAX_T' to config.h.
The ksh that comes with SUA doesn't have this problem.
I'm guessing the problem is in bash's internal globbing code, somehow, but in case I'm merely doing something stupid, 'set -o' reports:
allexport off
braceexpand on
emacs on
errexit off
errtrace off
functrace off
hashall on
histexpand on
history on
ignoreeof off
interactive-comments on
keyword off
monitor on
noclobber off
noexec off
noglob off
nolog off
notify off
nounset off
onecmd off
physical off
pipefail off
posix off
privileged off
verbose off
vi off
xtrace off
|
|
|
|
|
RE: bash filename globbing take 2 - Mar. 24, '06, 12:27:15 PM
|
|
|
woehlkmp
Posts: 102
Status: offline
|
Ok, I got this "working" via the rather ugly hack of putting 'exec bash --init-file .bash_aliases' in my .bash_profile (.bash_aliases sets up the aliases that are otherwise nuked from exec'ing a non-login instance of the shell). The question is, does anyone know why this works?
I would prefer to fix this, as I am already going through two logins because I have to start bash via ksh's .profile (really bad things happen if I don't), and each one takes a second or two to execute.
|
|
|
|
|
RE: bash filename globbing take 2 - Mar. 24, '06, 12:29:10 PM
|
|
|
Rodney
Posts: 3728
Joined: Jul. 9, '02,
From: /Tools lab
Status: offline
|
Had you rerun configure?
|
|
|
|
|
RE: bash filename globbing take 2 - Mar. 24, '06, 3:33:55 PM
|
|
|
woehlkmp
Posts: 102
Status: offline
|
Rerun after doing what? I'm pretty sure (ok, not positive) that I re-ran it after setting CC, and configure itself bombs without the new config.guess. The other change was adding '#define _(U)INTMAX_T', which is in config.h and so has to be done after running configure. I'm pretty sure I did a 'make clean' in between, though.
Oddly enough it seems bash 3.1 doesn't have this problem, or maybe I did muck something up with 3.0 and don't remember what any more. Maybe it's something that's broken in the interix mods??
If anyone has any guesses what would make it work on NFS drives and break otherwise, I'm still curious, but for now I seem to have it working. Thanks anyway!
|
|
|
|
 New Messages |
 No New Messages |
 Hot Topic w/ New Messages |
 Hot Topic w/o New Messages |
|
 Locked w/ New Messages |
 Locked w/o New Messages |
|
 Post New Thread
Reply to Message
Post New Poll
Submit Vote
Delete My Own Post
Delete My Own Thread
Rate Posts |
|
|
|
Printable Version
