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. :)
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
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
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
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
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
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
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
* 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
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-
* Bruno Haible wrote on Tue, Aug 22, 2006 at 02:15:36PM CEST:
> Making all in man
> /bin/sh /Users/bruno/data/work/hello-2.1.91/build-aux/missing --run help2man
> --name="Friendly Greeting Program" ../src/hello >hello.1
> /Users/bruno/data/work/hello-2.1.91/build-aux/missing: line 46: help2man:
Later on in the MacOS X build:
Making all in doc
make[2]: Nothing to be done for `all'.
Making all in man
/bin/sh /Users/bruno/data/work/hello-2.1.91/build-aux/missing --run help2man
--name="Friendly Greeting Program" ../src/hello >hello.1
/Users/bruno/data/work/hello-2.1.91/build-aux/missing: li
17 matches
Mail list logo
