| Summary: | xpdf: can't get expected result | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [Build System, Metadata & Runtime] OE-Core | Reporter: | Xiaofeng Yan <Xiaofeng.yan> | ||||
| Component: | core | Assignee: | Xiaofeng Yan <Xiaofeng.yan> | ||||
| Status: | RESOLVED FIXED | QA Contact: | |||||
| Severity: | normal | ||||||
| Priority: | Medium | CC: | meta.mr.watcher, meta.watcher, richard.purdie | ||||
| Version: | 1.0 | ||||||
| Target Milestone: | 1.1 | ||||||
| Hardware: | mpc8315e-rdb | ||||||
| OS: | ppc | ||||||
| Whiteboard: | |||||||
| OS type for building Yocto: | --- | Type of Regression: | --- | ||||
| Verified: | Documentation change: | --- | |||||
| Attachments: |
|
||||||
|
Description
Xiaofeng Yan
2011-03-17 18:48:46 UTC
Can you please attach a copy of /opt/lsb/appbat/bin/pdftotext, I would like to see the commands it is really using. Currently the meta data does not contain any recipes for xpdf, so I would like to see what command it's using. Created attachment 131 [details]
test case for pdftotext
The following steps is about how to reproduce the error for command "pdftotext test1.pdf" Step1: Download binary pdftotext PC# wget http://ftp.linux-foundation.org/pub/lsb/app-battery/released-4.1.0/ppc32/lsb-xpdf-1.01-10.lsb4.ppc.rpm Step2: Set rpm environment for ppc root@qemuppc#echo "ppc-suse-linux-gnu" >> /etc/rpm/platform Step3: Prepare stuff root@qemuppc:/# ls lsb-xpdf-1.01-10.lsb4.ppc.rpm test1.pdf Step4: Install xpdf tools root@qemuppc:/# rpm -ivh lsb-xpdf-1.01-10.lsb4.ppc.rpm --nodeps warning: lsb-xpdf-1.01-10.lsb4.ppc.rpm: Header V4 DSA signature: NOKEY, key ID bdc76b46 Preparing... ########################################### [100%] 1:lsb-xpdf ########################################### [100%] Step5: Run command "pdftotext test1.pdf" root@qemuppc:/# /opt/lsb/appbat/bin/pdftotext test1.pdf Illegal instruction The normal result for "pdftotext test1.pdf" should generate a file "test1.txt" but error "Illegal instruction" arise now. this error is only exist in ppc, x86 and x86-64 don't have this bugs now. It is compilation tool problem by verification because the compilation tool from test suite compiled by LSB official is different from compilation tool from mpc8315e. So some instructions from compilation tool for LSB official have no existence in compilation tool from mpc8315e. |