Here's the patch to fix this:
Thanks, installed.
From: Andreas Schwab sch...@linux-m68k.org
Cc: e...@gnu.org, bug-texinfo@gnu.org
Date: Sun, 23 Dec 2012 00:09:30 +0100
k...@freefriends.org (Karl Berry) writes:
Did I use an incorrect variable?
I don't know. Sorry. I trust someone else can help.
$target has no use in
Eli Zaretskii e...@gnu.org writes:
For my education: isn't $host the machine on which the package is
compiled,
No, that's $build, obviously.
Andreas.
--
Andreas Schwab, sch...@linux-m68k.org
GPG Key fingerprint = 58CA 54C7 6D53 942B 1756 01D3 44D5 214B 8276 4ED5
And now for something
Date: Sat, 15 Dec 2012 10:06:57 +0200
From: Eli Zaretskii e...@gnu.org
CC: bug-texinfo@gnu.org
Date: Fri, 14 Dec 2012 22:35:23 GMT
From: k...@freefriends.org (Karl Berry)
I attach below a patch to install Windows batch files
I installed it.
If you could send me the
Did I use an incorrect variable?
I don't know. Sorry. I trust someone else can help.
. If I use --target=, the test works, but make install fails
because the *.bat files were not included in the tarball.
Sorry about that. I fixed it for next time.
Best,
Karl
k...@freefriends.org (Karl Berry) writes:
Did I use an incorrect variable?
I don't know. Sorry. I trust someone else can help.
$target has no use in anything but a compiler. Everyone else should
look at $host only.
Andreas.
--
Andreas Schwab, sch...@linux-m68k.org
GPG Key
From: Andreas Schwab sch...@linux-m68k.org
Cc: e...@gnu.org, bug-texinfo@gnu.org
Date: Sun, 23 Dec 2012 00:09:30 +0100
$target has no use in anything but a compiler. Everyone else should
look at $host only.
Thanks. For my education: isn't $host the machine on which the
package is
Date: Mon, 10 Dec 2012 22:06:18 GMT
From: k...@freefriends.org (Karl Berry)
Cc: bug-texinfo@gnu.org
How about looking at the target produced by configure? The relevant
ones are *-pc-mingw32 and *-pc-msdosdjgpp. Would that work?
Maybe. I don't know. I need you, or someone, to
On Tue, Dec 11, 2012 at 12:06:49PM +0200, Eli Zaretskii wrote:
Failing that, I will need some help here. I know enough Autoconf to
add the necessary magic to configure.ac that will replace some
@VOODOO@ with the list of files to install on Windows and leave it
empty on Posix platforms. But
On Tue, Dec 11, 2012 at 12:06:49PM +0200, Eli Zaretskii wrote:
Failing that, I will need some help here. I know enough Autoconf to
add the necessary magic to configure.ac that will replace some
@VOODOO@ with the list of files to install on Windows and leave it
empty on Posix platforms. But
Date: Tue, 11 Dec 2012 12:24:50 +0100
From: Patrice Dumas pertu...@free.fr
On Tue, Dec 11, 2012 at 12:06:49PM +0200, Eli Zaretskii wrote:
Failing that, I will need some help here. I know enough Autoconf to
add the necessary magic to configure.ac that will replace some
@VOODOO@ with
How about looking at the target produced by configure? The relevant
ones are *-pc-mingw32 and *-pc-msdosdjgpp. Would that work?
Maybe. I don't know. I need you, or someone, to make the actual patch
and try it. I have zero interest in ever touching Windows myself.
Best,
k
Date: Sat, 1 Dec 2012 23:41:38 GMT
From: k...@freefriends.org (Karl Berry)
Cc: bug-texinfo@gnu.org
Would it be OK for me to submit 3 short Windows batch files, to be
installed in the $prefix/bin directory when make install is run on
MS-Windows
Sure, if you can tell me what
() k...@freefriends.org (Karl Berry)
() Tue, 27 Nov 2012 01:13:31 GMT
ftp://alpha.gnu.org/gnu/texinfo/texinfo-4.13.91.tar.xz
http://alpha.gnu.org/gnu/texinfo/texinfo-4.13.91.tar.xz
I generated XML (in doc/ after make all check = OK) w/ GNUmakefile:
include Makefile
xml:
Date: Tue, 27 Nov 2012 01:13:31 GMT
From: k...@freefriends.org (Karl Berry)
I've put up the next pretest:
ftp://alpha.gnu.org/gnu/texinfo/texinfo-4.13.91.tar.xz
http://alpha.gnu.org/gnu/texinfo/texinfo-4.13.91.tar.xz
Same deal as before, please send any feedback here, to
Would it be OK for me to submit 3 short Windows batch files, to be
installed in the $prefix/bin directory when make install is run on
MS-Windows
Sure, if you can tell me what to do in the Makefile.am so they get
installed only on Windows.
k
build texinfo without ever running the perl programs being built.
It could be done, but I still don't see any overwhelming reason to worry
about it. Sorry. Other people contributed a way to do cross compiling
many years ago (build the programs natively and then use them to build
the cross
On Mi, 28 Nov 2012, Norbert Preining wrote:
On Mi, 28 Nov 2012, Norbert Preining wrote:
I guess I will activate that by default and let us see how the build
daemons crumble ... at least we get some reports what needs to be fixed ;-)
Done that now, new version -2 which runs all checks
On 11/27/2012 02:13 AM, Karl Berry wrote:
I've put up the next pretest:
ftp://alpha.gnu.org/gnu/texinfo/texinfo-4.13.91.tar.xz
http://alpha.gnu.org/gnu/texinfo/texinfo-4.13.91.tar.xz
Same deal as before, please send any feedback here, to bug-texinfo.
I'm seeing this error trying to
Is there interest to bomb you with bugs in the info viewer? (that
are still present, like some misplaced cursors, or remaining
droppings - incomplete redraws, ...)
I use info all the time! Actually, it's my preferred `browser' for
reading info documents. So yes, I'm interested in getting
On Tue, Nov 27, 2012 at 08:57:43PM +0900, Norbert Preining wrote:
Hi Karl, hi all,
On Di, 27 Nov 2012, Karl Berry wrote:
http://alpha.gnu.org/gnu/texinfo/texinfo-4.13.91.tar.xz
Short sucess story: I have uploaded 4.13.91 (debian release -1) to
Debian/experimental, and it has been
On Di, 27 Nov 2012, Patrice Dumas wrote:
Did you run the tests as part of the build?
No. Here on my computer I run it maually, though, and get all PASS
or SKIP (a few tests are skipped).
My feeling (but not tried) is that in the minimal environment of
Debian build-daemons there will be quite
Karl, what would you prefer?
I'm not sure I fully understand the choices.
I intentionally made the Texinfo build create the info files for the
Texinfo manuals, because if the newly-built Texinfo can't even manage to
do that, what good is it? Pregenerating the info files would just paper
On Wed, Nov 28, 2012 at 07:55:12AM +0900, Norbert Preining wrote:
On Di, 27 Nov 2012, Patrice Dumas wrote:
Did you run the tests as part of the build?
No. Here on my computer I run it maually, though, and get all PASS
or SKIP (a few tests are skipped).
My feeling (but not tried) is that
On Wed, Nov 28, 2012 at 12:02:44AM +, Karl Berry wrote:
Karl, what would you prefer?
I'm not sure I fully understand the choices.
In fact, what I have in mind (but it may make no sense) was to allow to
build texinfo without ever running the perl programs being built. One
could even
Hi Patrice,
thanks for your email!
On Mi, 28 Nov 2012, Patrice Dumas wrote:
all the dependencies. Actually it looks like Unicode::EastAsianWidth
is not packaged in debian, I guess the internal copy is used. The
Yes, I call --with-system-... only for the other two, this one is
not in
On Mi, 28 Nov 2012, Norbert Preining wrote:
I guess I will activate that by default and let us see how the build
daemons crumble ... at least we get some reports what needs to be fixed ;-)
Done that now, new version -2 which runs all checks during build
uploaded to Debian/experimental, will
I've put up the next pretest:
ftp://alpha.gnu.org/gnu/texinfo/texinfo-4.13.91.tar.xz
http://alpha.gnu.org/gnu/texinfo/texinfo-4.13.91.tar.xz
Same deal as before, please send any feedback here, to bug-texinfo.
Thanks,
Karl
28 matches
Mail list logo
