Thanks for your comments.  I will send a maximally simple broken
example to the people who responded.  Here's the description:

Inside the archives are two short lyx files and associated latex & PDF output.
(1) PDF_to_include is a short file that I created for the purpose of
the test.  I try to include it into the otherfile with the command
\includepdf

(2) File_that_includes_other_file shows the symptoms:
(a) if I load the lyx fil into lyx, and use "View" or "Export" via
pdflatex, I can't get a PDF out of it.
(b) if I export the Latex, it produces the tex file in the archive
(c) if I do pdflatex from the command line or from Texshop, I can
easily produce the PDF you have here --- the PDF I would expect.

I have noticed a new thing: if I comment out the ERT \includepdf
statement, (but still keep pdfpages in the preamble), everything works
as expected.

(Bennett Helm wrote)
> The similar setup for me works just fine, without any problems. Are
> you sure nothing has changed in the meantime? -- You haven't changed
> the file at all? You haven't updated latex?

Sorry, yes, I have updated latex.  I am using the most recent (of a
few days ago) version from fink unstable.  I didn't suspect latex,
because everything works fine from the command line and texshop....
but I guess I should, because it's the only thing that has changed.

pdflatex --version tells me:
pdfeTeX 3.141592-1.21a-2.2

fink describe tetex tells me:
tetex-3.0-1

(Geoff Lloyd wrote)
> Otherwise you could run Lyx via a terminal windows and see what
> errors/comments it lists when you do the compile in PDFlatex.

Errmmm... I could, but I'll have to hunt around for some info on how
to do that.  I'll get back.

Thanks.  D


--

==================================
David J Philp
Postdoctoral Fellow
National Centre for Epidemiology and Population Health
Building 62, cnr Mills Rd & Eggleston Rd
The Australian National University
Canberra ACT 0200 Australia

T: +61 2 6125 8260
F: +61 2 6125 0740
M: 0423 535 397
W: http://nceph.anu.edu.au/

CRICOS Provider #00120C

Reply via email to