Bruno Haible wrote:
Hello Sylvain,
The build is based on a slightly modified gcc
cross-compiler for mipsel, and a minimal libc on top off of newlib
(ftp://sources.redhat.com/pub/newlib/) - check 'psptoolchain' and
'pspsdk' at
http://svn.ps2dev.org/listing.php?repname=psppath=%2Ftrunk%2F .
Hi,
- Including system's strings.h while it isn't available:
gnulib/doc/posix-headers/strings.texi tells you that all platforms have this
header file.
And I see that MinGW's just include 'string.h'. Good enough :)
- missing libc functions:
- fchdir.c references 'dup' and 'dup2'
Sylvain Beucler wrote:
...
- getcwd references 'rewinddir' which isn't present
Likewise, all platforms have opendir and rewinddir.
Thanks.
I was not sure whether that was common or not in an embedded system.
What bothers me though is that the functions aren't used (since the
program
Sylvain Beucler wrote:
What bothers me though is that the functions aren't used (since the
program runs without) yet are still required at compile time
Regarding dup and dup2 this is normal: fchdir.c overrides them without calling
rpl_dup and rpl_dup2 itself. This code assumes that dup and dup2
On Sun, Mar 22, 2009 at 10:48:51PM +0100, Jim Meyering wrote:
Stefan Bienert wrote:
I need a fallback implementation of srand48 and drand48 for my GPL project
to compile with mingw32 for a certain operating system.
Is there a chance that this can be put into a near-by-future revision of
Richard W.M. Jones wrote:
On Sun, Mar 22, 2009 at 10:48:51PM +0100, Jim Meyering wrote:
Stefan Bienert wrote:
I need a fallback implementation of srand48 and drand48 for my GPL project
to compile with mingw32 for a certain operating system.
Is there a chance that this can be put into a
Bruno Haible br...@clisp.org writes:
Some ideas:
1) Should the sockets.m4 module unconditionally add LIBSOCKET to LDADD?
2) Should the gnulib-tool generated Makefile.am add LIBSOCKET to LDADD?
No, LDADD has an effect on all executables. I don't want to link all my
programs against
On Saturday 21 March 2009 00:03:30 Kamil Dudka wrote:
On Friday 20 of March 2009 22:25:30 Bob Proulx wrote:
The '~' is often used in package version numbers. It sorts before the
version without it. For example the rule[1] for generating a stable
backport from the latest unstable version
s/runs/runs -- as far as you've seen --/ ?
At least in the save-cwd module (used e.g., via openat), getcwd
is not used in the common case, but under unusual circumstances,
fall-back code does use it.
I'd say runs - Bruno explained that 'dup' and 'dup2' are used in
auxiliary replacements
Kamil Dudka wrote:
Kamil Dudka wrote:
I'll look at it deeper next week and check if the new regex works in all
cases.
The Debian's backport suffix ~bpo${debian_release}+${build_int} seems to
be safe in the context of this patch. Thanks to the '+' it can be never
matched as a file
Hello Bruno,
* Bruno Haible wrote on Mon, Mar 23, 2009 at 12:28:51AM CET:
http://lists.gnu.org/archive/html/bug-gnulib/2005-02/msg0.html
Without consensus on the question whether interoperability is desirable,
it is moot to discuss the format. As I read the archives, at some point
My project is GPL. Is it really legally OK to copy LGPL code verbatim
into my project?
Yes, because the LGPL has a specific provision allowing upgrading to the
GPL.
With latest gnulib on HP-UX 10.20:
$ ./gnulib-tool --create-testdir --dir=t strtoull
$ cd t
$ ./configure
...
$ gmake
...
source='dummy.c' object='dummy.o' libtool=no \
DEPDIR=.deps depmode=hp /bin/sh ../build-aux/depcomp \
cc -Ae -DHAVE_CONFIG_H -I. -I.. -g -c dummy.c
13 matches
Mail list logo
