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 this...)
Not sure if I do either. What do other (real) programs do?
I found a typo on the web page, and w
It's not theoretical. I invite you to install a cross-compiler and try it.
Sure. By theoretical I meant "because so few people cross-compile".
(And even fewer modify the sources. And even fewer than that care that
help2man might fail. I think we might be down to one person in the
world. :)
Btw, the "#ifdef __GLIBC__" in m4/fsusage.m4 looks wrong also for
the Hurd, because glibc/sysdeps/mach/hurd/statfs64.c does not
appear to access /proc.
/proc doesn't exist on GNU, never did.
Cheers.
Autoconf uses elisp-comp, which Automake supplies, so I installed this:
2006-08-24 Paul Eggert <[EMAIL PROTECTED]>
* MODULES.html.sh (Support for building libraries and executables):
Add elisp-comp.
* config/srclist.txt: Add elisp-comp.
* build-aux/elisp-comp: Ne
Hi,
I committed this change, to test non-default sourcebase and m4base.
Please let me know if it causes problems.
2006-08-24 Bruno Haible <[EMAIL PROTECTED]>
* gnulib-tool (func_create_testdir): Use non-default values of
sourcebase and m4base.
*** gnulib-20060823/gnulib-tool 2
Jim Meyering asks:
> I'm curious: what's your motivation for using it?
Portability testing. Through the BeOS porting, I found the following
problems not limited to BeOS:
- check-AUTHORS: applies to any platform that doesn't build all of the
programs.
- mbchar.h problem: applies to any plat
Ralf Wildenhues wrote:
> First, I think you wouldn't want `make' to keep trying to update
> hello.1
Well, if HELP2MAN is the command ':' that doesn't eat CPU time, it doesn't
matter.
> so a rule like
> if test '$(cross_compiling)' = yes
The value of $cross_compiling can also be 'maybe'. To be
Karl Berry wrote:
> I'm not sure it's best to add that additional level of
> infrastructure/indirection to Hello.
Yes, if it can be done through the one-liner by Ralf and my other
configure.ac patch today, that is simpler.
> Also, why not adding the help2man to build-aux?
>
> Sounds good to
Karl Berry wrote:
> I wonder whether any test is really necessary. As
> far as I know coreutils, texinfo, and other packages have used help2man
> for years, and I have never seen a bug report about the problem of
> help2man failing on cross compiles ...
The build failure is triggered if the user
Paul Eggert wrote:
> * MODULES.html.sh: Move 'assert' into the assert section.
> Move 'dummy' into the linking section.
> Remove ullong_max.
> Add section for compatibility checks for POSIX:2001 functions,
> and put d-ino, d-type, link-follow, rmdir-errno, unlink-busy,
Hi Bruno,
Thanks for all of your recent BeOS porting work.
We've received very few reports about BeOS problems, other than yours.
I'm curious: what's your motivation for using it?
Bruno Haible <[EMAIL PROTECTED]> wrote:
...
> After producing this patch, I noticed that the replacement 'statfs' tha
Ralf Wildenhues <[EMAIL PROTECTED]> writes:
> Hello Simon,
>
> * Simon Josefsson wrote on Thu, Aug 24, 2006 at 10:06:28AM CEST:
>>
>> Perhaps autoconf should de-couple "can i execute this binary" from
>> "cross-compilation". Autoconf could test if it is possible to run
>> programs by compiling a
Hello Simon,
* Simon Josefsson wrote on Thu, Aug 24, 2006 at 10:06:28AM CEST:
>
> Perhaps autoconf should de-couple "can i execute this binary" from
> "cross-compilation". Autoconf could test if it is possible to run
> programs by compiling a small program and run it, and see if the
> output is
Ralf Wildenhues <[EMAIL PROTECTED]> writes:
> would be suited a bit better. Second though, there are many
> "cross-compiling" situations where executing the program actually works,
> so the above is at least a wee bit suboptimal. (Think i486 -> i686, or
> Cygwin -> MinGW, or some simulator: on m
14 matches
Mail list logo
