ust
> before including gnulib/stdint.h.
I agree that having gnulib pull in wchar.h is very unfortunate. The
gnulib folks, CC'd, are very responsive - maybe someone on bug-gnulib
has an idea on how to fix this?
--
Daniel Jacobowitz
CodeSourcery
d specify the oldest version to be
supported separately.
Mike, I thought the *at wrappers fell back to emulation if the
syscalls were missing. Is that impossible for utimensat?
--
Daniel Jacobowitz
CodeSourcery
try ((int * (*) ()) __errno_location) (). The default return
type for non-debugging functions is int rather than long still.
--
Daniel Jacobowitz
CodeSourcery
ice for
a different system? Seems like a stretch to me. If I wanted to use a
Windows version of gettext, I'd either use Windows paths or arrange
for a shell which converted.
--
Daniel Jacobowitz
CodeSourcery
back to it.
I do want to fix the GDB bug that got me started on this, but there
may be another way now.
--
Daniel Jacobowitz
CodeSourcery
isunderstood you. When is it O(N*2) - only with high
precision?
--
Daniel Jacobowitz
CodeSourcery
his in GDB with user
input if it might take all year; that's hardly more useful.
--
Daniel Jacobowitz
CodeSourcery
%I64d instead of %lld
> for printing 64-bit integers. Needed for mingw.
vasnprintf.c, you mean?
--
Daniel Jacobowitz
CodeSourcery
e that if no one else does sooner, I'll be back to it.
--
Daniel Jacobowitz
CodeSourcery
d of $HOME. If $HOME
is behind an NFS automounter, and your program searches for anything
in its $prefix, then this can slow things to a crawl.
--
Daniel Jacobowitz
CodeSourcery
ile on snprintfv, so don't expect too
much unless someone else wants to pick up the project of making GDB
happier - which I'd be glad to assist with as time permits :-)
--
Daniel Jacobowitz
CodeSourcery
>
> FCN seems more meaningful.
Bruce agrees, I agree... let's do that. I've checked this in. I also
had to revert one of the line wrapping changes - the doc generation
script relies on having argument descriptions all on one line, or the
formatting of the manual gets messed up.
pository, it's named SNV_ASSERT_FMT - just grep for it.
Which one should it be? Can't have half and half.
--
Daniel Jacobowitz
CodeSourcery
weekend working on merging? I'm worried that gnulib is developing too
many different ways to do almost the same thing, all slightly
different.
--
Daniel Jacobowitz
CodeSourcery
On Mon, Feb 26, 2007 at 04:58:49AM +0100, Ralf Wildenhues wrote:
> * Daniel Jacobowitz wrote on Mon, Feb 26, 2007 at 01:29:53AM CET:
> >
> > That's from standalone libsnprintfv DLL support, which we're
> > obsoleting as we fold it into gnulib. It doesn't wor
__, __LINE__, SNV_ASSERT_FMT, str);
+printf_error(pi, __FILE__, __LINE__, SNV_ASSERT_FCN, str);
That's not defined anywhere.
../../libsnprintfv/snprintfv/printf.c: In function
'parse_printf_format':
../../libsnprintfv/snprintfv/printf.c:386: error: 'SNV_ASSERT_FCN'
undeclared (first use in this function)
--
Daniel Jacobowitz
CodeSourcery
On Sun, Feb 25, 2007 at 03:56:46PM +0100, Bruno Haible wrote:
> Daniel Jacobowitz wrote:
> > Paolo's updates added a check for runetype.h
> > in order to make Mac OS/X's work properly. Perhaps gnulib's
> > substitute wchar.h ought to handle that?
>
&
check went away - current autoconf's inline check also
checks for working static inline.
I did notice one thing: Paolo's updates added a check for runetype.h
in order to make Mac OS/X's work properly. Perhaps gnulib's
substitute wchar.h ought to handle that?
--
Daniel Jacob
clear macro that determines this. __VFP_FP__ is
a subset of the times that normal IEEE layout is used.
--
Daniel Jacobowitz
CodeSourcery
On Fri, Feb 23, 2007 at 11:42:31PM -0500, Daniel Jacobowitz wrote:
> I checked in the attached to libsnprintfv.
By the way, the only warning in the mingw32 build:
../../libsnprintfv/snprintfv/printf.c: In function `stream_vprintf':
../../libsnprintfv/snprintfv/printf.c:850: warning: `sn
antage of
those shiny new modules for some of it, and I'm tentatively planning
to remove various portability widgets that the rest of gnulib just
relies on now. Plus everything simplifies when we no longer need to
make it installable.
--
Daniel Jacobowitz
CodeSourcery
2007-02-23 Daniel
On Fri, Feb 23, 2007 at 07:46:27AM -0500, Daniel Jacobowitz wrote:
> How should I initially configure this? It has a couple of support
> files already (compile, ltmain.sh) but not in the build-aux directory
> where it wants to find them, and not all of the necessary files
> e.g
where it wants to find them, and not all of the necessary files
e.g. config.sub.
If the right answer is just "use --add-missing", then should we delete
the existing copy of libtool.m4 / ltmain.sh?
--
Daniel Jacobowitz
CodeSourcery
already a printf parser in gnulib, and it looks as if it
was at some point related to snprintfv's. Unification will
interesting.
I will work on gnulib-izing snprintfv first. Are there any particular
platforms you would recommend compiling for? Otherwise I'll default
to Linux and mingw32.
--
Daniel Jacobowitz
CodeSourcery
ly on gnulib infrastructure (e.g. for
portability issues that libsnprintfv currently solves on its own).
--
Daniel Jacobowitz
CodeSourcery
om (it's already FSF
assigned, right?). Want to give me a pointer, or would you rather do
it yourself?
--
Daniel Jacobowitz
CodeSourcery
autoconf and automake. Do you have time to work on that
> with me?
Is that really necessary? I know that GCC manages something similar
that doesn't require any makefile adjustment - at most some defines
added to config.h.
--
Daniel Jacobowitz
CodeSourcery
there's only lukewarm interest, I may do
something specific to hex float. We already have routines to
decompose FP numbers.
--
Daniel Jacobowitz
CodeSourcery
nt on the list, please ask the Steering Committee.
This is a textbook example of what they're for.
--
Daniel Jacobowitz
CodeSourcery
z \"\$\$MOSTLYCLEANDIRS\" || \\"
> ! echo " for dir in \$\$MOSTLYCLEANDIRS; do \\"
> ! echo "if test -d \$\$dir; then \\"
> ! echo " echo \"rmdir \$\$dir\"; rmdir \$\$dir; \\"
> ! echo "
On Wed, Oct 18, 2006 at 04:10:46PM -0400, Daniel Jacobowitz wrote:
> I'm now worrying that I misunderstood how the gnulib vasnprintf works,
> though. This may be less useful than I thought, since it uses both the
> result of arg parsing and the format string :-(
Never mind, this bi
To be honest, I don't particularly care about this today. GDB support
for wide strings is miniscule and no one is improving it. However,
if I were to support it, I would try to emulate the target machine's
behavior on the host through some other mechanism.
--
Daniel Jacobowitz
CodeSourcery
On Wed, Oct 18, 2006 at 06:08:22PM +0200, Bruno Haible wrote:
> Daniel Jacobowitz wrote:
> > For GDB, we're looking at fixing our printf built in command once and
> > for all. What we really need to do that is two separate interfaces
> > that can talk to each other
rintf, but without printf_fetchargs.
Could I persuade you to split the existing vasnprintf along these
lines, so that we can use it? I can submit a patch myself if necessary
to shuffle all the code around, but I don't have a gnulib assignment;
not sure whether that would be considered trivial.
> - it would be impossible to restore the initial working
> directory, once it's been changed -- thereafter, no reference
> to a `.'-relative name can be resolved.
You're talking about exec. If you're going to use
35 matches
Mail list logo
