John Summerfield wrote:
> 
> Michael Tokarev:
[]
> > I guess that some program used to "build help tree" (whatever it is)
> > doesn't installed at my machine, but what program it is??  Tried to
> > look to sources, where that help tree should be built, but without
> > any luck -- it's a big tcl script, and it includes tons of other
> > scripts, but where it fails, I don't know.  Using something like
> > strace isn't very appropriate -- it will be really HUGE trace file.
> > Maybe someone knows what is missing at my machine for this (and
> > yes, missing from BuildPreReq section of tcltk.spec)?
[]

> Possibly there's a missing program.
This is exactly what I thought.

> Probably there's a message you missed.
No, no other error messages around, just this one I quoted.

> Certainly a program that's supposed to be reading "file8" is not listening any more.
This was exactly my thoghts also... :)

> Try again, and pipe everything into a file:
> rpm ... >build.log 2>&1

And this is exactly what I did several times with several tcltk versions/releases... 
:))
(actually: rpm --rebuild tcltk.src.rpm &>tcltk.log &).

> and read the end of the log looking for what went wrong. If you can't find anything,
> run it this way:
> strace -f -F -o rpm.trace rpm ... >build.log 2>&1
> 
> The file, rpm.trace, will be enormous, but it will have the answer about what went
> wrong.
And the fact that strace output will be HUGE (I mentioned this in my message) caused
me to try to ask here first...

> Read the man page for strace for some refinements.
Ok, by incident, Wietse Venema gives me the answer:
  Try:
    % strace -eopen postconf mynetworks
  and see what file changes.
This gives me an idea to use "-e" strace's option.  For my case, this probably should 
be
"-eexec", isn't it?  File will be huge anyway, but much smaller.  Ok, let's try to do
so...:)

Anyway, thank for trying to be helpful.

Regards,
 Michael.



_______________________________________________
Redhat-devel-list mailing list
[EMAIL PROTECTED]
https://listman.redhat.com/mailman/listinfo/redhat-devel-list

Reply via email to