Re: hello-2.1.91 build failure on MacOS X

2006-08-23 Thread Ralf Wildenhues
Hello Bruno, * Bruno Haible wrote on Wed, Aug 23, 2006 at 10:40:31PM CEST: > Ralf Wildenhues wrote: > > We could ask help2man to have it return a different exit > > status if it gets an exit status of 126 from the program, and have it > > return 63 then, which `missing' will interpret as version m

Re: hello-2.1.91 build failure on MacOS X

2006-08-23 Thread Ralf Wildenhues
Karl Berry writes: Next pretest coming soon ... With the program_name fix from Bruno, I get a distcheck pass on Cygwin. However, on MinGW all three tests fail because the program outputs CRLF line endings, while the test suite creates files with LF ending. (Not sure if you want to worry about

Re: coreutils-6.0 on BeOS (9)

2006-08-23 Thread Paul Eggert
Bruno Haible <[EMAIL PROTECTED]> writes: > The 'df' program needs a small adjustment so that the 'struct statvfs' of > BeOS can be used. And the 'stat' program needs porting too; here the > 'struct statvfs' cannot be used, because it does not have a f_type Thanks. While testing this on GNU/Linux

Re: hello-2.1.91 build failure on MacOS X

2006-08-23 Thread Karl Berry
Here's a fix suggestion, using the x-to-1 script that is in use in GNU gettext for 5 years. I'm not sure it's best to add that additional level of infrastructure/indirection to Hello. E.g., it seems unnecessary to have a skeleton when all that is being specified is the one-line descriptio

Re: hello-2.1.91 build failure on MacOS X

2006-08-23 Thread Karl Berry
Why would it be help2man's business to deal with cross-compiles? Agreed. IMO it is configure's business. What do you think about this patch? Seems ok to me, but I wonder whether any test is really necessary. As far as I know coreutils, texinfo, and other packages have used help2man for

Re: [bug-gnulib] gnulib changes to make it easier for coreutils to use gnulib-tool

2006-08-23 Thread Paul Eggert
"Mark D. Baushke" <[EMAIL PROTECTED]> writes: > I believe that the new openat module needs to depend on lchown. Yes, thanks for noting that. I installed your patch.

Re: [bug-gnulib] gnulib changes to make it easier for coreutils to use gnulib-tool

2006-08-23 Thread Mark D. Baushke
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi Paul, I believe that the new openat module needs to depend on lchown. I updated CVS and it didn't pull in the lchown module which lead to a build-break on BSDI BSD/OS. Index: modules/openat =

Re: hello-2.1.91 build failure on MacOS X

2006-08-23 Thread Bruno Haible
Ralf Wildenhues wrote: > We could ask help2man to have it return a different exit > status if it gets an exit status of 126 from the program, and have it > return 63 then, which `missing' will interpret as version mismatch. Uuhhh. I'm not sure you get a defined exit status when you try to execute

Re: hello-2.1.91 build failure on MacOS X

2006-08-23 Thread Ralf Wildenhues
* Bruno Haible wrote on Wed, Aug 23, 2006 at 08:00:57PM CEST: > Ralf Wildenhues wrote: > > This should only be an error if `missing' cannot guess the output file > > name. The fix is to use the flag -o or --output, to help `missing' to > > infer. > > And what about the cross-compiling case? 'help

Re: [bug-gnulib] Compilation failure of xvasprintf.c on FreeBSD 4.x

2006-08-23 Thread Martin Lambers
On Tue, 22. Aug 2006, 20:43:38 +, Roman Bogorodskiy wrote: > > > Roman Bogorodskiy reported that xvasprintf.c fails to compile on FreeBSD > > > 4.x, and that the patch below fixes that. He can give more details if > > > necessary. Apparently, FreeBSD does not have va_copy(). This should be > >

Re: fix gl_LOCK constraints

2006-08-23 Thread Paul Eggert
Bruno Haible <[EMAIL PROTECTED]> writes: > 2006-08-23 Bruno Haible <[EMAIL PROTECTED]> > > * m4/lock.m4 (gl_LOCK_EARLY): Renamed from gl_LOCK. Thanks for the heads-up. I installed the patch below to coreutils to accommodate this. This leads to one of the issues I had when converting core

coreutils-6.0 on BeOS (9)

2006-08-23 Thread Bruno Haible
The 'df' program needs a small adjustment so that the 'struct statvfs' of BeOS can be used. And the 'stat' program needs porting too; here the 'struct statvfs' cannot be used, because it does not have a f_type or f_fstypename or similar field. Btw, the "#ifdef __GLIBC__" in m4/fsusage.m4 looks wro

Re: hello-2.1.91 build failure on MacOS X

2006-08-23 Thread Bruno Haible
Ralf Wildenhues wrote: > This should only be an error if `missing' cannot guess the output file > name. The fix is to use the flag -o or --output, to help `missing' to > infer. And what about the cross-compiling case? 'help2man' bails out with an error if you have modified src/hello.c when cross-

Re: working with locally modified or augmented gnulib repositories

2006-08-23 Thread Simon Josefsson
Hi Bruno. I just tried this feature -- for doc/gendocs_template, which I modify to add links to GTK_DOC manuals -- and it seems to be working fine. Except that I have to specify --local-dir every time I use --import. Is this the intended behaviour? Maybe the --local-dir value could be cached, ju

lock module: change default settings for OSF/1

2006-08-23 Thread Bruno Haible
This turns off multithreading support for OSF/1 by default. Needed because the mere _linking_ with -lpthread causes programs using fork/exec to go into an endless SIGSEGV loop inside execvp(). 2006-08-18 Bruno Haible <[EMAIL PROTECTED]> * lock.m4 (gl_LOCK_BODY): Change the default value

fix gl_LOCK constraints

2006-08-23 Thread Bruno Haible
Hi, Up to now, gl_LOCK must be placed as the last element of gl_EARLY, and no other macros that modify LIBS or CPPFLAGS can be used after gl_LOCK. To resolve these weird constraints, I'm separating the "early" part of the macro (which can modify LIBS or CPPFLAGS) from the "normal" part (which test

Re: coreutils-6.0 on BeOS (6)

2006-08-23 Thread Simon Josefsson
Bruno Haible <[EMAIL PROTECTED]> writes: > The reason is that BeOS does not have PF_INET, only AF_INET, but usually they > have the same values. Also it doesn't have PF_UNSPEC. Does it AF_UNSPEC? Did you grep the entire /usr/include tree to find PF_INET or PF_UNSPEC? Maybe they are in some non-