Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.os.linux.misc > #35755
| From | Eli the Bearded <*@eli.users.panix.com> |
|---|---|
| Newsgroups | comp.os.linux.misc |
| Subject | Re: The difference between /bin/test and /bin/[ |
| Date | 2022-10-21 04:41 +0000 |
| Organization | Some absurd concept |
| Message-ID | <eli$2210210026@qaz.wtf> (permalink) |
| References | <tije9a$19dt$1@gioia.aioe.org> <ygaedv58ewi.fsf@akutech.de> <timcia$3o485$1@dont-email.me> <timeu8$3o485$2@dont-email.me> |
In comp.os.linux.misc, Lew Pitcher <lew.pitcher@digitalfreehold.ca> wrote: > The question intrigued me, so I checked the source for the /bin/test > on my Slackware installation. It appears that, for the GNU CoreUtils > version of test, GNU took "the long way around" in it's error reporting. > > Specifically, the source includes conditional compilation logic to > report name of the binary based on a value passed in at compilation time. Time was when many non-Linux systems used to have Gnu utilities installed with different filenames, typically adding a 'g' to the front. On this NetBSD box I'm using, for example: $ ls --version ls: unknown option -- - usage: ls [-1AaBbCcdFfghikLlMmnOoPpqRrSsTtuWwXx] [file ...] $ gls --version 2>&1 ls (GNU coreutils) 9.0 Copyright (C) 2021 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later <https://gnu.org/licenses/gpl.html>. This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. Written by Richard M. Stallman and David MacKenzie. I expect the compiled in name is relevant to that. Not sure how test uses it though. $ cp $(which gtest) /tmp/gnutest $ /tmp/gnutest x = gnutest: missing argument after '=' Elijah ------ gcc is called that because the vendor cc was likely different
Back to comp.os.linux.misc | Previous | Next — Previous in thread | Next in thread | Find similar
correct quoting for variables in bash scripts? Barry Stir <scooter@mealteam6.mil> - 2022-10-17 19:28 +0800
Re: correct quoting for variables in bash scripts? Aragorn <telcontar@duck.com> - 2022-10-17 14:10 +0200
Re: correct quoting for variables in bash scripts? Ralf Fassel <ralfixx@gmx.de> - 2022-10-17 14:15 +0200
Re: correct quoting for variables in bash scripts? Jerry Peters <jerry@example.invalid> - 2022-11-01 20:27 +0000
Re: correct quoting for variables in bash scripts? "Carlos E. R." <robin_listas@es.invalid> - 2022-10-17 14:39 +0200
Re: correct quoting for variables in bash scripts? Rich <rich@example.invalid> - 2022-10-17 14:02 +0000
Re: correct quoting for variables in bash scripts? Henning Hucke <h_hucke+spam.news@newsmail.aeon.icebear.org> - 2022-10-17 13:54 +0000
Re: correct quoting for variables in bash scripts? Eli the Bearded <*@eli.users.panix.com> - 2022-10-17 23:35 +0000
Re: correct quoting for variables in bash scripts? Ralf Fassel <ralfixx@gmx.de> - 2022-10-18 11:31 +0200
Re: correct quoting for variables in bash scripts? Rich <rich@example.invalid> - 2022-10-18 12:02 +0000
Re: correct quoting for variables in bash scripts? Ralf Fassel <ralfixx@gmx.de> - 2022-10-18 15:01 +0200
Re: correct quoting for variables in bash scripts? Lew Pitcher <lew.pitcher@digitalfreehold.ca> - 2022-10-18 14:17 +0000
The difference between /bin/test and /bin/[ Lew Pitcher <lew.pitcher@digitalfreehold.ca> - 2022-10-18 14:58 +0000
Re: The difference between /bin/test and /bin/[ Eli the Bearded <*@eli.users.panix.com> - 2022-10-21 04:41 +0000
Re: correct quoting for variables in bash scripts? Ralf Fassel <ralfixx@gmx.de> - 2022-10-19 12:04 +0200
csiph-web