Poky Project Discussions
 help / color / mirror / Atom feed
From: Mark Hatle <mark.hatle@windriver.com>
To: Wolfgang Denk <wd@denx.de>
Cc: poky@yoctoproject.org
Subject: Re: Build of prelink_git.bb fails
Date: Thu, 03 Feb 2011 08:22:40 -0600	[thread overview]
Message-ID: <4D4ABA30.4020505@windriver.com> (raw)
In-Reply-To: <20110203141543.0C504D81AE2@gemini.denx.de>

Something is wrong with your host system.  Nothing has changed with the prelink
integration since late December.

The failure seems to indicate a broken latex, tetex and/or tex2pdf installation.

--Mark

On 2/3/11 8:15 AM, Wolfgang Denk wrote:
> Hello,
> 
> when building poky-image-sato-sdk in recent versions the build fails
> with:
> 
> ERROR: 'virtual:native:/opt/poky/git/poky/work/meta/recipes-devtools/prelink/prelink_git.bb' failed
> ERROR: Function 'do_compile' failed (see /opt/poky/build/mainline-test/tmp/work/x86_64-linux/prelink-native-1.0+git1+909470ee441237563d6236c505cb2d02ddc48704-r0/temp/log.do_compile.10035 for further information)
> 
> 
> It appears that's because some "fancyheadings.sty" cannot be found:
> 
> from log.do_compile.10035:
> 
> ...
> (/usr/share/texmf/tex/latex/pdftex-def/pdftex.def))
> (/usr/share/texmf/tex/latex/type1cm/type1cm.sty)
> (/usr/share/texmf/tex/generic/thumbpdf/thumbpdf.sty
> 
> Package thumbpdf Warning: Thumbnail data file `prelink.tpt' not found.
> 
> ) (/usr/share/texmf/tex/plain/misc/pdfcolor.tex)
> (/usr/share/texmf/tex/latex/eso-pic/eso-pic.sty
> (/usr/share/texmf/tex/latex/everyshi/everyshi.sty)
> (/usr/share/texmf/tex/latex/graphics/keyval.sty))
> (/usr/share/texmf/tex/latex/graphics/color.sty
> (/usr/share/texmf/tex/latex/config/color.cfg))
> 
> ! LaTeX Error: File `fancyheadings.sty' not found.
> 
> Type X to quit or <RETURN> to proceed,
> or enter new name. (Default extension: sty)
> 
> Enter file name:
> ! Emergency stop.
> <read *>
> 
> l.116 \pagestyle
>                 {fancy}^^M
> !  ==> Fatal error occurred, no output PDF file produced!
> Transcript written on prelink.log.
> make[2]: *** [prelink.pdf] Error 1
> make[2]: Leaving directory `/opt/poky/build/mainline-test/tmp/work/x86_64-linux/prelink-native-1.0+git1+909470ee441237563d6236c505cb2d02ddc48704-r0/git/trunk/doc'
> make[1]: *** [all-recursive] Error 1
> make[1]: Leaving directory `/opt/poky/build/mainline-test/tmp/work/x86_64-linux/prelink-native-1.0+git1+909470ee441237563d6236c505cb2d02ddc48704-r0/git/trunk'
> make: *** [all] Error 2
> FATAL: oe_runmFunction 'do_compile' failed (see /opt/poky/build/mainline-test/tmp/work/x86_64-linux/prelink-native-1.0+git1+909470ee441237563d6236c505cb2d02ddc48704-r0/temp/log.do_compile.10035 for further information)
> 
> 
> This must be because one of the recently added changes (within the
> last 48 hors or so).
> 
> Best regards,
> 
> Wolfgang Denk
> 



  reply	other threads:[~2011-02-03 14:22 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-02-03 14:15 Build of prelink_git.bb fails Wolfgang Denk
2011-02-03 14:22 ` Mark Hatle [this message]
2011-02-03 14:43   ` Richard Purdie
2011-02-03 14:47     ` Wolfgang Denk
2011-02-03 14:45   ` Wolfgang Denk
2011-02-03 16:15     ` Mark Hatle

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4D4ABA30.4020505@windriver.com \
    --to=mark.hatle@windriver.com \
    --cc=poky@yoctoproject.org \
    --cc=wd@denx.de \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox