Smalltalk › Gnu

What might cause "No runnable processAbort trap"?

‹ Previous Topic Next Topic ›
 
classic Classic list List threaded Threaded
♦
♦
 26 messages Options
12
dukester
Reply | Threaded
Open this post in threaded view
♦
♦
|

Re: What might cause "No runnable processAbort trap"?

dukester
On Thu, 7 Jan 2010, Paolo Bonzini wrote:

> On 01/07/2010 02:16 PM, Duke Normandin wrote:
> > So libtools is living in/opt/blah. You want them in the /usr/  tree? I
> > wonder how many files we're talking about here? I could symlink them
> > to /opt/whatever, but what a&^%$@# PITA! Can't we do something in the
> > "configure" script or the "Makefile", line "ifdef $OSTYPE or
> > something, then look at /usr then /opt?
>
> No no, just do the other try...
>
> Paolo
>

I did a:

autoreconf -fvi
./configure

then

dnormandin@ ~/smalltalk
06:43 am >> make
make  all-recursive
Making all in lib-src
/bin/sh ../libtool --tag=CC   --mode=compile gcc -DHAVE_CONFIG_H
-I. -I..     -g -O2 -Wall -Wno-strict-aliasing -Wno-switch -fno-gcse
-fstrict-aliasing -Wdeclaration-after-statement -Wno-format
-Wno-long-double -Wpointer-arith -Wno-pointer-sign -Wwrite-strings
-MT qsort.lo -MD -MP -MF .deps/qsort.Tpo -c -o qsort.lo qsort.c
../libtool: line 796: X--tag=CC: command not found
../libtool: line 829: libtool: ignoring unknown tag : command not found
../libtool: line 796: X--mode=compile: command not found
../libtool: line 962: *** Warning: inferring the mode of operation is deprecated.: command not found
../libtool: line 963: *** Future versions of Libtool will require --mode=MODE be specified.: command not found
../libtool: line 1106: Xgcc: command not found
../libtool: line 1106: X-DHAVE_CONFIG_H: command not found
../libtool: line 1106: X-I.: command not found
../libtool: line 1106: X-I..: command not found
../libtool: line 1106: X-g: command not found
../libtool: line 1106: X-O2: command not found
../libtool: line 1106: X-Wall: command not found
../libtool: line 1106: X-Wno-strict-aliasing: command not found
../libtool: line 1106: X-Wno-switch: command not found
../libtool: line 1106: X-fno-gcse: command not found
../libtool: line 1106: X-fstrict-aliasing: command not found
../libtool: line 1106: X-Wdeclaration-after-statement: command not found
../libtool: line 1106: X-Wno-format: command not found
../libtool: line 1106: X-Wno-long-double: command not found
../libtool: line 1106: X-Wpointer-arith: command not found
../libtool: line 1106: X-Wno-pointer-sign: command not found
../libtool: line 1106: X-Wwrite-strings: command not found
../libtool: line 1106: X-MT: command not found
../libtool: line 1106: Xqsort.lo: command not found
../libtool: line 1106: X-MD: command not found
../libtool: line 1106: X-MP: command not found
../libtool: line 1106: X-MF: command not found
../libtool: line 1106: X.deps/qsort.Tpo: No such file or directory
../libtool: line 1106: X-c: command not found
../libtool: line 1157: Xqsort.lo: command not found
../libtool: line 1162: libtool: compile: cannot determine name of library object from `': command not found
make[2]: *** [qsort.lo] Error 1
make[1]: *** [all-recursive] Error 1
make: *** [all] Error 2
--
Duke


_______________________________________________
help-smalltalk mailing list
[hidden email]
http://lists.gnu.org/mailman/listinfo/help-smalltalk
Paolo Bonzini-2
Reply | Threaded
Open this post in threaded view
♦
♦
|

Re: What might cause "No runnable processAbort trap"?

Paolo Bonzini-2
On 01/07/2010 02:50 PM, Duke Normandin wrote:

> On Thu, 7 Jan 2010, Paolo Bonzini wrote:
>
>> On 01/07/2010 02:16 PM, Duke Normandin wrote:
>>> So libtools is living in/opt/blah. You want them in the /usr/  tree? I
>>> wonder how many files we're talking about here? I could symlink them
>>> to /opt/whatever, but what a&^%$@# PITA! Can't we do something in the
>>> "configure" script or the "Makefile", line "ifdef $OSTYPE or
>>> something, then look at /usr then /opt?
>>
>> No no, just do the other try...
>>
>> Paolo
>>
>
> I did a:
>
> autoreconf -fvi
> ./configure

Did you look for ltmain.sh files and remove them?

Paolo


_______________________________________________
help-smalltalk mailing list
[hidden email]
http://lists.gnu.org/mailman/listinfo/help-smalltalk
dukester
Reply | Threaded
Open this post in threaded view
♦
♦
|

Re: What might cause "No runnable processAbort trap"?

dukester
On Thu, 7 Jan 2010, Paolo Bonzini wrote:

> On 01/07/2010 02:50 PM, Duke Normandin wrote:
> > On Thu, 7 Jan 2010, Paolo Bonzini wrote:
> >
> > > On 01/07/2010 02:16 PM, Duke Normandin wrote:
> > > > So libtools is living in/opt/blah. You want them in the /usr/  tree? I
> > > > wonder how many files we're talking about here? I could symlink them
> > > > to /opt/whatever, but what a&^%$@# PITA! Can't we do something in the
> > > > "configure" script or the "Makefile", line "ifdef $OSTYPE or
> > > > something, then look at /usr then /opt?
> > >
> > > No no, just do the other try...
> > >
> > > Paolo
> > >
> >
> > I did a:
> >
> > autoreconf -fvi
> > ./configure
>
> Did you look for ltmain.sh files and remove them?
>
> Paolo
>

Actually, I simply did a:

dnormandin@ ~/smalltalk
06:56 am >> find . -name "ltmain.sh"

Two of them showed up - one each in build-aux/ and snprintfv/

I mv(ed) them to ltmain.shx. However, I see that for some reason
build-aux still has a copy of ltmain.sh in it, even after the "mv". So
I nuked it and I'll try again.
--
Duke


_______________________________________________
help-smalltalk mailing list
[hidden email]
http://lists.gnu.org/mailman/listinfo/help-smalltalk
dukester
Reply | Threaded
Open this post in threaded view
♦
♦
|

Re: What might cause "No runnable processAbort trap"?

dukester
In reply to this post by Paolo Bonzini-2
On Thu, 7 Jan 2010, Paolo Bonzini wrote:

> On 01/07/2010 02:50 PM, Duke Normandin wrote:
> > On Thu, 7 Jan 2010, Paolo Bonzini wrote:
> >
> > > On 01/07/2010 02:16 PM, Duke Normandin wrote:
> > > > So libtools is living in/opt/blah. You want them in the /usr/  tree? I
> > > > wonder how many files we're talking about here? I could symlink them
> > > > to /opt/whatever, but what a&^%$@# PITA! Can't we do something in the
> > > > "configure" script or the "Makefile", line "ifdef $OSTYPE or
> > > > something, then look at /usr then /opt?
> > >
> > > No no, just do the other try...
> > >
> > > Paolo
> > >
> >
> > I did a:
> >
> > autoreconf -fvi
> > ./configure
>
> Did you look for ltmain.sh files and remove them?
>
> Paolo
>

 OK... I jumped through the hoops once again. Attached is my
 autoreconf.log file. How can I get rid of the:

"You should update your `aclocal.m4' by running aclocal"

messages. I have run "aclocal --force" with NO joy!

dnormandin@ ~
07:06 am >> ls -AFl /usr/bin/aclocal
lrwxr-xr-x  1 root  wheel  22  6 Jan 20:10 /usr/bin/aclocal@ -> /opt/local/bin/aclocal

dnormandin@ ~
07:20 am >> aclocal --version
aclocal (GNU automake) 1.11
Copyright (C) 2009 Free Software Foundation, Inc.
License GPLv2+: GNU GPL version 2 or later
<http://gnu.org/licenses/gpl-2.0.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.

Written by Tom Tromey <[hidden email]>
       and Alexandre Duret-Lutz <[hidden email]>.

Is there anything else in the autoreconf.log file that concerns you?
--
duke


_______________________________________________
help-smalltalk mailing list
[hidden email]
http://lists.gnu.org/mailman/listinfo/help-smalltalk
dukester
Reply | Threaded
Open this post in threaded view
♦
♦
|

Re: What might cause "No runnable processAbort trap"?

dukester
In reply to this post by Paolo Bonzini-2
On Thu, 7 Jan 2010, Paolo Bonzini wrote:

> On 01/07/2010 02:50 PM, Duke Normandin wrote:
> > On Thu, 7 Jan 2010, Paolo Bonzini wrote:
> >
> > > On 01/07/2010 02:16 PM, Duke Normandin wrote:
> > > > So libtools is living in/opt/blah. You want them in the /usr/  tree? I
> > > > wonder how many files we're talking about here? I could symlink them
> > > > to /opt/whatever, but what a&^%$@# PITA! Can't we do something in the
> > > > "configure" script or the "Makefile", line "ifdef $OSTYPE or
> > > > something, then look at /usr then /opt?
> > >
> > > No no, just do the other try...
> > >
> > > Paolo
> > >
> >
> > I did a:
> >
> > autoreconf -fvi
> > ./configure
>
> Did you look for ltmain.sh files and remove them?
>
> Paolo
>
Sorry... forgot to attach the bloody file...

More coffeeeeeee!!
--
duke
_______________________________________________
help-smalltalk mailing list
[hidden email]
http://lists.gnu.org/mailman/listinfo/help-smalltalk

autoreconf.log (3K) Download Attachment
Paolo Bonzini-2
Reply | Threaded
Open this post in threaded view
♦
♦
|

Re: What might cause "No runnable processAbort trap"?

Paolo Bonzini-2
In reply to this post by dukester

>   OK... I jumped through the hoops once again. Attached is my
>   autoreconf.log file. How can I get rid of the:
>
> "You should update your `aclocal.m4' by running aclocal"

Why worry since it's succeeding after all? :-)  It is taking care of it
for you since you gave --force to autoreconf.

Paolo


_______________________________________________
help-smalltalk mailing list
[hidden email]
http://lists.gnu.org/mailman/listinfo/help-smalltalk
12
Free forum by Nabble Edit this page