Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

individual lab building is broken #264

Open
tleb opened this issue Jan 16, 2025 · 0 comments
Open

individual lab building is broken #264

tleb opened this issue Jan 16, 2025 · 0 comments

Comments

@tleb
Copy link
Member

tleb commented Jan 16, 2025

common/labs-header.tex contains much more content than common/single-lab-header.tex. That implies that building labs using features from labs-header.tex does not work. Example:

⟩ make kernel-i2c-describing-hardware-labs.pdf
...
/usr/bin/texfot: invoking: xelatex kernel-i2c-describing-hardware-labs.tex
This is XeTeX, Version 3.141592653-2.6-0.999996 (TeX Live 2024/Arch Linux) (preloaded format=xelatex)
LaTeX Warning: Unused global option(s):
Package hyperref Warning: Rerun to get /PageLabels entry.
Package fancyhdr Warning: \headheight is too small (15.0pt):
Underfull \vbox (badness 10000) has occurred while \output is active
Package fancyhdr Warning: \headheight is too small (15.0pt):
! LaTeX Error: Environment bashinput undefined.

l.132 \begin{bashinput}
! Emergency stop.
 ...
l.132 \begin{bashinput}
Output written on kernel-i2c-describing-hardware-labs.pdf (2 pages).
make[1]: *** [Makefile:200: kernel-i2c-describing-hardware-labs.pdf] Error 1
...
make: *** [Makefile:219: kernel-i2c-describing-hardware-labs.pdf] Error 2

Solutions?

  • Copy interesting content from labs-header.tex to single-lab-header.tex.
  • Make a all-labs-header.tex that gets used for both.
  • Remove the infrastructure to build individual labs.

Commit introducing bashinput & co is dc88032:

commit dc88032a70bd3b989455a9ddf4f8e80c01bd4f98
Author: Manuel Reis <[email protected]>
Date:   Sat Apr 10 10:59:31 2021 +0100

    add formatting to bash/uboot commands
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant