64 bit machines
BigJohnT wrote:
I asked someone in the know and
changelog on master is the result of merges and is not carefully maintained. there have not been any merges into master since 2.5.1 was tagged. we will never make a release off master so this is not usually a problem
John
Where would someone in the know 'pull' from?
Thx
_jC
.
Not being "in the know" about what your looking for I have no idea.
He was just explaining that if you pull from master the changelog is not maintained. Which branch you use depends on what you want. If you clone master but want 2.5.1 then you need to checkout the 2.5 branch.
John
Please Log in or Create an account to join the conversation.
Ideally I'd like to know how to grab the current stable release sources, and the development release patchset against them.
Thanks
_jC
.
I'm not sure what you mean by "and the development release patchset against them", never heard that term used for Linuxcnc... If you use the Git repository to get the source what ever branch you clone will be the most current for that branch. Complete instructions for obtaining the source is on the Wiki.
John
Please Log in or Create an account to join the conversation.
_jC wrote:
Ideally I'd like to know how to grab the current stable release sources, and the development release patchset against them.
Thanks
_jC
.
I'm not sure what you mean by "and the development release patchset against them", never heard that term used for Linuxcnc... If you use the Git repository to get the source what ever branch you clone will be the most current for that branch. Complete instructions for obtaining the source is on the Wiki.
John
Yeah, I see that now. I'm really just getting up to speed on the repositories.
So is it correct to assume that the Stable 2.5.1 release is the v2.5.1 tag of v2.5_branch? I see that the current pulls are the rolling patchsets past that point.
---
Don't know if I should start a new thread on my building problems, or indeed if this is the correct forum catagory for them.
But with the latest pull from v2.5_branch I am still having problems with bad asciidoc text breaking my build. Here is the latest build-crash:
...
xsltproc -o Master_Getting_Started_es.rtex --xinclude --xincludestyle --param current.dir '/home/sixis/Downloads/linuxCNC/builds/v2.5_branch/docs/src' --param listings.xml '/tmp/tmpQdxsuL/listings.xml' /tmp/tmpQdxsuL/custom.xsl /home/sixis/Downloads/linuxCNC/builds/v2.5_branch/docs/src/Master_Getting_Started_es.xml
XSLT stylesheets DocBook - LaTeX 2e (0.3.4-1)
===================================================
Error: no ID for constraint linkend: sub:Finding-Maximum-Velocity.
XRef to nonexistent id: sub:Finding-Maximum-Velocity
Error: no ID for constraint linkend: sub:Finding-Maximum-Acceleration.
XRef to nonexistent id: sub:Finding-Maximum-Acceleration
Error: no ID for constraint linkend: cap:EMC2-seleccion-de-configuracion.
XRef to nonexistent id: cap:EMC2-seleccion-de-configuracion
Build Master_Getting_Started_es.pdf
built-in module pdftex registered
no support found for ifthen
no support found for ifxetex
no support found for fontspec
no support found for xltxtra
no support found for fontenc
no support found for ucs
no support found for inputenc
no support found for fancybox
built-in module makeidx registered
no support found for emc2
building additional files...
checking if compiling is necessary...
the output file doesn't exist
pdflatex -interaction=batchmode Master_Getting_Started_es.tex
pdflatex failed
Master_Getting_Started_es.tex:1369: Package utf8x Error: MalformedUTF-8sequence.
Master_Getting_Started_es.tex:1369: leading text: ... = 200 Pasos por revolución
Master_Getting_Started_es.tex:1369: Package ucs Error: Unknown Unicode character 65533 = U+FFFD,
Master_Getting_Started_es.tex:1369: leading text: ... = 200 Pasos por revolución
Master_Getting_Started_es.tex:1369: Package utf8x Error: Character179appearedalone.
Master_Getting_Started_es.tex:1369: leading text: ... = 200 Pasos por revolución
Master_Getting_Started_es.tex:1372: Package utf8x Error: MalformedUTF-8sequence.
Master_Getting_Started_es.tex:1372: leading text: Dientes del tornillo guía
Master_Getting_Started_es.tex:1372: Package utf8x Error: Character173appearedalone.
Master_Getting_Started_es.tex:1372: leading text: Dientes del tornillo guía
Master_Getting_Started_es.tex:1373: Package utf8x Error: MalformedUTF-8sequence.
Master_Getting_Started_es.tex:1373: leading text: Paso del tornillo guía
Master_Getting_Started_es.tex:1373: Package utf8x Error: Character173appearedalone.
Master_Getting_Started_es.tex:1373: leading text: Paso del tornillo guía
Master_Getting_Started_es.tex:1373: Package utf8x Error: MalformedUTF-8sequence.
Master_Getting_Started_es.tex:1373: leading text: ...a = 0.2000 pulgadas por revolución
Master_Getting_Started_es.tex:1373: Package utf8x Error: Character179appearedalone.
Master_Getting_Started_es.tex:1373: leading text: ...a = 0.2000 pulgadas por revolución
Master_Getting_Started_es.tex:1398: Package utf8x Error: MalformedUTF-8sequence.
Master_Getting_Started_es.tex:1398: leading text: ... = 200 Pasos por revolución
Master_Getting_Started_es.tex:1398: Package utf8x Error: Character179appearedalone.
Master_Getting_Started_es.tex:1398: leading text: ... = 200 Pasos por revolución
Master_Getting_Started_es.tex:1401: Package utf8x Error: MalformedUTF-8sequence.
Master_Getting_Started_es.tex:1401: leading text: Dientes del tornillo guía
Master_Getting_Started_es.tex:1401: Package utf8x Error: Character173appearedalone.
Master_Getting_Started_es.tex:1401: leading text: Dientes del tornillo guía
Master_Getting_Started_es.tex:1402: Package utf8x Error: MalformedUTF-8sequence.
Master_Getting_Started_es.tex:1402: leading text: Paso del tornillo guía
Master_Getting_Started_es.tex:1402: Package utf8x Error: Character173appearedalone.
Master_Getting_Started_es.tex:1402: leading text: Paso del tornillo guía
Master_Getting_Started_es.tex:1402: Package utf8x Error: MalformedUTF-8sequence.
Master_Getting_Started_es.tex:1402: leading text: ...llo guía = 5.00 mm por revolución
Master_Getting_Started_es.tex:1402: Package utf8x Error: Character179appearedalone.
Master_Getting_Started_es.tex:1402: leading text: ...llo guía = 5.00 mm por revolución
Master_Getting_Started_es.tex:3794: Package utf8x Error: MalformedUTF-8sequence.
Master_Getting_Started_es.tex:3794: leading text: .Arrastré
Master_Getting_Started_es.tex:3794: Package utf8x Error: Character169appearedalone.
Master_Getting_Started_es.tex:3794: leading text: .Arrastré
A possible reason for transformation failure is invalid DocBook
(as reported by xmllint)
Error: pdflatex compilation failed
a2x: ERROR: "dblatex" -t pdf -p "/etc/asciidoc/dblatex/asciidoc-dblatex.xsl" -s "/etc/asciidoc/dblatex/asciidoc-dblatex.sty" -P doc.publisher.show=0 -P latex.output.revhistory=0 -s ../docs/src/emc2.sty -P latex.hyperparam=colorlinks,linkcolor=blue,filecolor=blue,urlcolor=blue,citecolor=blue -P latex.encoding=utf8 -V "/home/sixis/Downloads/linuxCNC/builds/v2.5_branch/docs/src/Master_Getting_Started_es.xml" returned non-zero exit status 1
rm: cannot remove `../docs/src/Master_Getting_Started_es.pdf': No such file or directory
make[1]: *** [../docs/src/Master_Getting_Started_es.pdf] Error 1
make[1]: Leaving directory `/home/sixis/Downloads/linuxCNC/builds/v2.5_branch/src'
make: *** [build-stamp] Error 2
sixis@sixis:~/Downloads/linuxCNC/builds/v2.5_branch$
sixis@sixis:~/Downloads/linuxCNC/builds/v2.5_branch$ locale
LANG=en_US.UTF-8
LANGUAGE=en_US:en
LC_CTYPE="en_US.UTF-8"
LC_NUMERIC="en_US.UTF-8"
LC_TIME="en_US.UTF-8"
LC_COLLATE=C
LC_MONETARY="en_US.UTF-8"
LC_MESSAGES="en_US.UTF-8"
LC_PAPER="en_US.UTF-8"
LC_NAME="en_US.UTF-8"
LC_ADDRESS="en_US.UTF-8"
LC_TELEPHONE="en_US.UTF-8"
LC_MEASUREMENT="en_US.UTF-8"
LC_IDENTIFICATION="en_US.UTF-8"
LC_ALL=
sixis@sixis:~/Downloads/linuxCNC/builds/v2.5_branch$
Package: asciidoc
Version: 8.6.7-1
Versions of packages asciidoc depends on:
ii python 2.7.3-2
Versions of packages asciidoc recommends:
ii dblatex 0.3.4-1
ii docbook-utils 0.6.14-2
ii libxml2-utils 2.8.0+dfsg1-5
ii xmlto 0.0.25-2
Versions of packages asciidoc suggests:
ii source-highlight 3.1.6-1+b1
pn vim-addon-manager <none>
-- System Information:
Debian Release: wheezy/sid
APT prefers testing-proposed-updates
APT policy: (500, 'testing-proposed-updates'), (500, 'stable-updates'), (500, 'unstable'), (500, 'testing'), (500, 'stable')
Architecture: amd64 (x86_64)
Kernel: Linux 2.6.38.8-120804.a-multitouch-rtai (SMP w/2 CPU cores; PREEMPT)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Is there some missing dependancy or missconfiguation that is breaking the pdflatex step of the document build? The German document that preceeds the Spanish docu processes fine???
Thanks
_jC
.
Please Log in or Create an account to join the conversation.
Please Log in or Create an account to join the conversation.
It might be expedient to not build the docs?
Yes, but curiously non-trivial. As I posted above in #22854 linuxcnc.org/index.php/english/component...mit=6&start=12#22854
====
make: *** [build-stamp] Error 2
I found the easiest solution was just to throw the offending input files overboard.
sixis@sixis:~/linuxcnc-v2.5.1$ cat docs/src/empty-doc
empty doc
sixis@sixis:~/linuxcnc-v2.5.1$ find docs -name *_??.txt -exec cp docs/src/empty-doc '{}' ';'
After that everything builds
====
The bigger issue is the 'scary delta' between my build and the build-bot's.
I mean, if my build configuation can't build the docs cleanly, what else does it silently goof?
I will investigate further after my day job.
Thanks and regards
_jC
.
Please Log in or Create an account to join the conversation.
So is it correct to assume that the Stable 2.5.1 release is the v2.5.1 tag of v2.5_branch? I see that the current pulls are the rolling patchsets past that point.
Yes the v2.5.1 is the latest release for 2.5. Generally it is assumed that you are safe in getting the v2.5_branch as no new features will be added once a branch is released and only bug fixes or document changes are pushed to the branch so you would want them too. Another problem if you use v2.5.1 is you will be left behind when v2.5.2 is released...
A git patch is something a non-developer uses to send to a developer for consideration.
Typically you clone master then checkout the branch you desire or you could just clone the branch.
John
Please Log in or Create an account to join the conversation.
The bigger issue is the 'scary delta' between my build and the build-bot's.
I've looked at this several times now, and narrowed the issue to the difference between the 'texlive' packages of Debian and Ubuntu, without finally finding a solution for discrepancy.
Rather unfortunate, but tossing the offending files overboard, and installing the buildbots documentation packages is a sufficient and timesaving workaround.
I'll just have to wait until the documentation developers are faced with this same problem on the next Ubuntu TeX upgrade cycle.
Cheers
_jC
.
Please Log in or Create an account to join the conversation.
Up until now I have not been able to build the documentation packages within the 'v2.5_branch' git pull.
I have found that the problem is caused by invisible utf8 character in the v2.5_branch/docs/src/gcode/gcode.txt file.
And ... voilà!
dh_builddeb
dpkg-deb: building package `linuxcnc-dev' in `../linuxcnc-dev_2.5.2_amd64.deb'.
dpkg-deb: building package `linuxcnc' in `../linuxcnc_2.5.2_amd64.deb'.
dpkg-deb: building package `linuxcnc-doc-en' in `../linuxcnc-doc-en_2.5.2_all.deb'.
dpkg-deb: building package `linuxcnc-doc-fr' in `../linuxcnc-doc-fr_2.5.2_all.deb'.
dpkg-deb: building package `linuxcnc-doc-de' in `../linuxcnc-doc-de_2.5.2_all.deb'.
dpkg-deb: building package `linuxcnc-doc-es' in `../linuxcnc-doc-es_2.5.2_all.deb'.
dpkg-deb: building package `linuxcnc-doc-pl' in `../linuxcnc-doc-pl_2.5.2_all.deb'.
sixis@sixis:~/Downloads/linuxCNC/builds/v2.5_branch$ cd ../..
sixis@sixis:~/Downloads/linuxCNC$ diff git/v2.5_branch/docs/src/gcode/gcode.txt builds/v2.5_branch/docs/src/gcode/gcode.txt
647c647
< G10 L2 P1 X3.5 Y17.2
---
> G10 L2 P1 X3.5 Y17.2
658c658
< G10 L2 P1 X0 Y0 Z0 (clear offsets for X,Y & Z axes in coordinate system 1)
---
> G10 L2 P1 X0 Y0 Z0 (clear offsets for X,Y & Z axes in coordinate system 1)
1384c1384
< * 'Drive Line' - A line through the initial X position parallel to the Z.
---
> * 'Drive Line' - A line through the initial X position parallel to the Z.
sixis@sixis:~/Downloads/linuxCNC$
sixis@sixis:~/Downloads/linuxCNC$ diff git/v2.5_branch/docs/src/gcode/gcode.txt builds/v2.5_branch/docs/src/gcode/gcode.txt | grep ">" | head -1| od -tx1 -c
0000000 3e 20 47 31 30 20 4c 32 20 50 31 20 58 33 2e 35
> G 1 0 L 2 P 1 X 3 . 5
0000020 20 59 31 37 2e 32 0a
Y 1 7 . 2 \n
0000027
sixis@sixis:~/Downloads/linuxCNC$ diff git/v2.5_branch/docs/src/gcode/gcode.txt builds/v2.5_branch/docs/src/gcode/gcode.txt | grep "<" | head -1| od -tx1 -c
0000000 3c 20 47 31 30 c2 a0 4c 32 c2 a0 50 31 c2 a0 58
< G 1 0 302 240 L 2 302 240 P 1 302 240 X
0000020 33 2e 35 c2 a0 59 31 37 2e 32 0a
3 . 5 302 240 Y 1 7 . 2 \n
0000033
sixis@sixis:~/Downloads/linuxCNC$
I don't know why this has been working on Ubuntu, but with the above fix I can build the English docs on Debian. Finally.
I'm still "empty string" padding the source texts for the internationalized docs, as they too are full of utf8 goofyness.
Debian's dblatex is more strict about these unexpected character sequences. I wish someone could say how to make it relax.
Cheers
jCandlish
.
Please Log in or Create an account to join the conversation.
John
Please Log in or Create an account to join the conversation.
What was the offending character? Can you give me a line number of a file that contains it?
John
The offending character is the HEX pair 'c2 a0' masquerading as an ASCII space, or HEX '20'
An unicode non-breaking white-space character.
According to the 'diff', it occurs on lines 647, 658 and 1384 of the file v2.5_branch/docs/src/gcode/gcode.txt
And probably elsewheres. I've only checked the English documentation.
That character breaks Debian's asciitext implementation.
Please Log in or Create an account to join the conversation.