#2224 [Rev. 46094] Build process breaks while parsing the documentation.

[Frederic bezies]

When the build process is working on the documentation, I got dozens and dozens of:

.awk: cmd. line:1: error: ? * + or {interval} not preceded by valid subpattern: /*\//

This break the pdf bulding.

And the last lines before build is stopped are:

/usr/sbin/texi2dvi: pdfetex exited with bad status, quitting.
/usr/sbin/texi2dvi: Removing vice.t2d

texinfo version: 7.3
awk version: 5.4.0

I have to use --disable-pdf-docs to have a working build process.

My distribution is Archlinux. I don't know where this part of the build process stopped working.

[gpz]

has to be r46089

really strange that this wouldnt work, my version of awk is even older:

$ awk --version
GNU Awk 5.3.2

and it works just fine this way.

to verify its really this, you could

cd vice/docs
./snapshots-extract.sh

[Roberto Muscedere]

Don't know if this helps, but in order for me to get the PDFs to generate, I needed the following Debian/Ubuntu packages:
texinfo
texlive
texlive-plain-generic
It might be better to generate the PDF than avoiding generating the PDF for now.

[gpz]

I doubt tex stuff is the problem here :)

[gpz]

This is the awk line, btw. If someone can tell what/how to fix, go ahead :)

TAB=`echo "$FULL" | awk '/*\// {exit} {print}'`

(It should return everyting from the input until the first occurance of */, ie closing comment)

[gpz]

please try if replacing the line by the following fixes it for you:

TAB=$(echo "$FULL" | awk '/\*\/ /{exit} {print}')

[Frederic bezies]

I will try this asap. I'm not in front of my computer right now. Sorry!

Edit: doesn't change anything. Same output errors and pdf is not created. Ouch!

[gpz]

i have comitted the change, please try :)

[Frederic bezies]

Which commit? The last I see is for residfp, not for the documentation.

[gpz]

ooops. now its there (r46098)

[Frederic bezies]

Still broken with the awk errors by dozens. Maybe something else will work?

[gpz]

I have no idea.

BUT did you verify it is actually that script? (run directly from the docs dir)

[Frederic bezies]

I do run it from the docs directory and got the same spamming error. Annoying.

[Frederic bezies]

Using my favorite AI, I got a working awk line:

TAB=$(printf "%s\n" "$FULL" | awk '/\*\// {exit} {print}')

Let's hope it won't break on distribution other than Archlinux.

Works with both zsh and bash. Hope it helps!

[gpz]

odd! is that just an extra space? please try

TAB=$(echo "$FULL" | awk '/\*\// {exit} {print}')

[Frederic bezies]

Launching the script with this version of TAB is working. So, we have a working fix?

[gpz]

looks like it, comitted in r46105 - please test

[Frederic bezies]

Will test and report. Well, I noticed when I grab the revision 46105, I still have the old awk line, not the fixed one. Weird.

I grabbed the code, could it be with makepkg (it grabbed the last revision) or using svn checkout https://svn.code.sf.net/p/vice-emu/code/trunk vice-emu-code I got the old awk line.

What's going on?

[gpz]

The only way i can see this happening is when you changed the file locally, then did something like "svn up" - which would merge your changes with whats in the repo shrug

[Frederic bezies]

Well, I removed all the source code before trying. So any modification made is gone. The screenshot was made using a new full source download. Weird :(

I did not use svn up, so my modification wasn't stored.

I removed the vice-emu-code repository and grabbed fresh new code. Still the old line. Very weird :(

When I type cat ./snapshots-extract.sh| grep TAB= on a fresh new source code, I got this output:

~~~
TAB=echo "$FULL" | awk '/*\// {exit} {print}'
TAB=$(echo "$FULL" | awk '/*\// {exit} {print}')
~~~

What's going on?

[gpz]

lol, well. the trick is to replace BOTH occurances of this line/expression :)

try r46106 :)

[Frederic bezies]

LOL, indeed. This time it worked. Let's close this annoying bug.

[gpz]

good, closing then :)