This is the mail archive of the
mailing list for the newlib project.
Re: Problem with building PDFs
On 01/23/2013 02:04 PM, Freddie Chopin wrote:
W dniu 2013-01-23 20:35, Joel Sherrill pisze:
On 01/23/2013 01:20 PM, Freddie Chopin wrote:
But your message made me do a little "search" and indeed there are some
empty (0 bytes) files called stmp-def in many folders + some "normal"
file that are empty:
[freddie@arch newlib]$ find -size 0
So three .def files that are empty. Could that be the reason? These 3
names cannot be found in the log of "make pdf", so I guess not...
No. The *.def files that are empty are the problem. They are
not being generated properly.
But in case of these 3 files there's no documentation in the source .c
files, so I guess it's quite correct these are 0 bytes long. Or maybe
not "correct", but "expected"...
Those three are empty for me. But I ended up with libc.pdf
and libm.pdf. The build finished OK.
../newlib-cvs/src/newlib/configure >c.log 2>&1 && make info pdf >p.log
I guess the real reason is somewhere here:
I've got a failure for these 5 files:
Each failure is in exactly the same place:
Those files include references to "nodes" which are supposed
to be defined in the empty "*.def" files. So the linkage is broken
before some nodes are empty.
I'm confused... Do the 5 files above "link" any external .def files or
maybe the other way around?
The empty *.def files are triggering the failures. Why the build
is generating them empty is the question.
I can attach output of configure and make info pdf if that makes any
sense, but there's nothing especially wrong there other than what I've
Joel Sherrill, Ph.D. Director of Research& Development
joel.sherrill@OARcorp.com On-Line Applications Research
Ask me about RTEMS: a free RTOS Huntsville AL 35806
Support Available (256) 722-9985