To comment on the following update, log in, then open the issue:
http://www.openoffice.org/issues/show_bug.cgi?id=62916


User vq changed the following:

                  What    |Old value                 |New value
================================================================================
                    Status|RESOLVED                  |REOPENED
--------------------------------------------------------------------------------
                Resolution|FIXED                     |
--------------------------------------------------------------------------------




------- Additional comments from [EMAIL PROTECTED] Tue Apr 25 14:37:29 -0700 
2006 -------
> Rene points out on IRC that configure.in as patched in tml01 now uses 
> oowintool
> before it has checked whether Perl is even available. So the Perl check 
> sections
> in configure.in should be moved before the first use of oowintool to get
> meaningful error reports, I guess.
Yes, please.

> I can't say if it's necessary to have the
> path to perl in oowintool expanded from @PERL@ or if hardcoding /usr/bin/perl 
> as
> now is OK. Perl on Cygwin is always /usr/bin/perl, but would oowintool be used
> also with 4NT or something else? Is Perl somewhere else then?
Yes, oowintool can be used with 4nt, but it would still be executed in a cygwin
bash and would require a cygwin perl.

If we get too many complains about a cygwin perl being installed in a
non-standard we can change that to @PERL@ later.

P.S.: A resync to m164 would be nice ;)

---------------------------------------------------------------------
Please do not reply to this automatically generated notification from
Issue Tracker. Please log onto the website and enter your comments.
http://qa.openoffice.org/issue_handling/project_issues.html#notification

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to