* Daniel Richard G. wrote on Sat, Dec 13, 2008 at 10:37:30PM CET:
> Here is the real problem---not gawk(1), but indeed tr(1):
>
> % ( echo foo ; echo bar ) | tr '\015\012' ' '
> foo
> bar
> % ( echo foo ; echo bar ) | tr '\015\012' ' ' < note the two-space
> string
> foo bar %
>
> The expe
[ adding bug-gnulib, removing bug-autoconf ]
* Daniel Richard G. wrote on Sat, Dec 13, 2008 at 11:16:28PM CET:
> However, I'm running into a more tricky issue during the build...
>
> source='sig2str.c' object='sig2str.o' libtool=no DEPDIR=.deps depmode=tru64
> /bin/ksh ../build-aux/depcomp cc
On (info "(coreutils)stty invocation")
say what you mean by Input Settings and Output Settings.
I.e., what you type into the terminal and then goes into... what is
sent from the computer to your terminal...??
After
`iuclc'
Translate uppercase characters to lowercase. Non-POSIX. May be
---
ChangeLog|6 ++
lib/getopt.c | 25 +
2 files changed, 23 insertions(+), 8 deletions(-)
diff --git a/ChangeLog b/ChangeLog
index 7faac2b..b593588 100644
--- a/ChangeLog
+++ b/ChangeLog
@@ -1,3 +1,9 @@
+2008-12-14 James Youngman
+
+ getopt: Indicat
James Youngman wrote:
> +2008-12-14 James Youngman
> +
> + getopt: Indicate the problem with ambiguous options clearly.
> + * lib/getopt.c (_getopt_internal_r): Print the first and second
> + possibility when there is an ambiguous match.
The patch looks good. But the master sources
On Sun, Dec 14, 2008 at 7:05 PM, Bruno Haible wrote:
> James Youngman wrote:
>> +2008-12-14 James Youngman
>> +
>> + getopt: Indicate the problem with ambiguous options clearly.
>> + * lib/getopt.c (_getopt_internal_r): Print the first and second
>> + possibility when there is an am
Ralf Wildenhues cited Daniel Richard G. and wrote:
> > However, I'm running into a more tricky issue during the build...
> >
> > source='sig2str.c' object='sig2str.o' libtool=no DEPDIR=.deps
> > depmode=tru64
> > /bin/ksh ../build-aux/depcomp cc -std -std -I.-ieee -g -c -o
> > sig2str.
jida...@jidanni.org wrote:
> On (info "(coreutils)stty invocation")
> say what you mean by Input Settings and Output Settings.
> I.e., what you type into the terminal and then goes into... what is
> sent from the computer to your terminal...??
>
> After
> `iuclc'
> Translate uppercase ch
> -Original Message-
> From: bug-coreutils-bounces+oss=teragram@gnu.org
> [mailto:bug-coreutils-
> bounces+oss=teragram@gnu.org] On Behalf Of Bruno
> Haible
>
> The usual way to debug this kind of things is
> 1) to look at the preprocessor output. Here:
> $ cc -std -std -I.
Daniel Richard G. wrote:
> -std puts the compiler into relaxed-ANSI mode, instead of the default, which
> is K&R. This flag was actually added by autoconf itself---the build failure I
> quoted was obtained with all *FLAGS variables unset.
>
> (The only other options here are -std1 [strict ANSI],
> -Original Message-
> From: Bruno Haible [mailto:br...@clisp.org]
> >
> > From "egrep '^#|timespec' i" ...
> >
> > # 582 "/usr/include/sys/types.h"
> > # 35 "/usr/include/sys/sysmisc.h"
> > typedef struct timespec {
> > } timespec_t;
> > # 35 "/usr/include/sys/siginfo.h"
>
> So? What is yo
11 matches
Mail list logo
