David N. Williams schrieb:
> Krishna Myneni wrote:
> > Guido Draheim wrote:
> >
> >> ... I have applied those patches as well as others that were sent to
> >> me in the
> >> last year. A new release 33.65 has been uploaded to the Sourceforge
> file
> >> section and a Freshmeat announcement was sent. ...
> >
> >
> > I tried building release 0.33.66 on an x86_64 Ubuntu 7.10 system, but
> > "make" failed as shown below. Any insight?
> >
> > Krishna
> >
> > --
> >
> > make[2]: Entering directory
> >
>
`/home/krishna/apps/pfe/pfe-0.33.66/Linux_2.6.22-14-generic_x86_64.d/bin'
> > /bin/bash ./libtool --tag=CC --mode=link gcc -g -O2 -o pfe-exec
> > pfe-exec.o ../pfe/libpfe.la
> > gcc -g -O2 -o .libs/pfe-exec pfe-exec.o ../pfe/.libs/libpfe.so
> > -lncurses -ldl
> > pfe-exec.o: In function `main':
> >
>
/home/krishna/apps/pfe/pfe-0.33.66/Linux_2.6.22-14-generic_x86_64.d/bin/../../bin/pfe-exec.c:25:
>
> > undefined reference to `p4_strlen'
> > collect2: ld returned 1 exit status
> > make[2]: *** [pfe-exec] Error 1
> > make[2]: Leaving directory
> >
>
`/home/krishna/apps/pfe/pfe-0.33.66/Linux_2.6.22-14-generic_x86_64.d/bin'
> > make[1]: *** [all-recursive] Error 1
> > make[1]: Leaving directory
> > `/home/krishna/apps/pfe/pfe-0.33.66/Linux_2.6.22-14-generic_x86_64.d'
> > make: *** [all] Error 2
> > krishna@[EMAIL PROTECTED]
>
> The pfe-0.33.66 build works fine for me with
> Linux_2.6.21.3_i686.d and gcc 3.4.5, both with the default
> ./configure, and with --with-sbr-threading --with-regs=2.
>
> On the other hand, my build attempt with Leopard ppc fails
> (with both gcc 4.0.1 and 3.3) on debug-ext.c, which I think is
> much before the above. It works fine with 0.33.65. The
> ChangeLog does show significant changes between the two versions
> in debug-ext. My temporary solution is to go with 0.33.65 plus
> the simple bug fix at the top of the 0.33.66 ChangeLog.
>
> Don't know if that would work with your system...
>
> -- David
(a)
The pfe-exec.c error is probably due to some cleanup that has removed
the implicit #include <pfe/os-string.h> - it does not hurt however to
just add it on default. So be it, committed to CVS.
(b)
Yes, debug-ext.c has been given some extensions to make it work in
non-ITC modes as well. In current CVS it does a pretty good job to
decompile sbr-threaded words - even if it is userr native code that
was compiled via CODE - END-CODE. If debug-ext fails on Leopard then
please send a logfile so that I can have check - good debugging support
is an important feature of a good Forth system.
Thanks in advance, cheers, Guido
|
