[bug] Seaside not starting

Issue status update for
http://smalltalk.gnu.org/node/264
Post a follow up:
http://smalltalk.gnu.org/project/comments/add/264

 Project:      GNU Smalltalk
 Version:      <none>
 Component:    Seaside/Swazoo
 Category:     bug reports
 Priority:     normal
 Assigned to:  Unassigned
 Reported by:  Leonidas
 Updated by:   Leonidas
 Status:       active

Hi,

I tried running Seaside in GNU Smalltalk, like described here:

http://smalltalk.gnu.org/blog/bonzinip/seaside-development-gnu-smalltalk



I created the image and wanted to run it:

$ gst-remote -I seaside.im --server --start=Seaside
gst-remote server started.
gst/share/smalltalk/kernel/../scripts/Remote.st:275: Aborted
(ip 44)SocketAddress class>>#extractAddressesAfterLookup:
(ip 6)[] in SocketAddress class>>#allByName:
(ip 4) BlockClosure>>#ensure:
(ip 48)[] in SocketAddress class>>#allByName:
(ip 4)[] in SocketAddress class>>#at:cache:
(ip 10)Dictionary>>#at:ifAbsent:
(ip 18)SocketAddress class>>#at:cache:
(ip 24)SocketAddress class>>#allByName:
(ip 10)SocketAddress class>>#initLocalAddresses
(ip 10)IPAddress class(SocketAddress class)>>#anyLocalAddress
(ip 28)[] in UndefinedObject>>#executeStatements
(ip 10) BlockClosure>>#on:do:
(ip 14)UndefinedObject>>#executeStatements
(ip 0)
Aborted

Port 8080 should be free, I'm using only 80.




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

Issue status update for
http://smalltalk.gnu.org/project/issue/264
Post a follow up:
http://smalltalk.gnu.org/project/comments/add/264

 Project:      GNU Smalltalk
 Version:      <none>
 Component:    Seaside/Swazoo
 Category:     bug reports
 Priority:     normal
 Assigned to:  Unassigned
 Reported by:  Leonidas
 Updated by:   bonzinip
 Status:       active

I cannot reproduce it on Darwin, sorry.

What is your OS?




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

Issue status update for
http://smalltalk.gnu.org/project/issue/264
Post a follow up:
http://smalltalk.gnu.org/project/comments/add/264

 Project:      GNU Smalltalk
 Version:      <none>
 Component:    Seaside/Swazoo
 Category:     bug reports
 Priority:     normal
 Assigned to:  Unassigned
 Reported by:  Leonidas
 Updated by:   Leonidas
 Status:       active

Linux 2.6.18 amd64 (Debian Etch).




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

Issue status update for
http://smalltalk.gnu.org/project/issue/264
Post a follow up:
http://smalltalk.gnu.org/project/comments/add/264

 Project:      GNU Smalltalk
 Version:      <none>
 Component:    Seaside/Swazoo
 Category:     bug reports
 Priority:     normal
 Assigned to:  Unassigned
 Reported by:  Leonidas
 Updated by:   swoolerton
 Status:       active

I get exactly the same error. Centos Linux also on amd64.
Looks like it might be happening on Linux 64 bit systems. Can I help to
get this resolved.




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

Issue status update for
http://smalltalk.gnu.org/project/issue/264
Post a follow up:
http://smalltalk.gnu.org/project/comments/add/264

 Project:      GNU Smalltalk
 Version:      <none>
 Component:    Seaside/Swazoo
 Category:     bug reports
 Priority:     normal
 Assigned to:  Unassigned
 Reported by:  Leonidas
 Updated by:   joe
 Status:       active

Hello,

got the same problem, even on an amd64 System.

But you can workaround, (if you want to see seaside in action) with the
following:

If you created the seaside-image, start seaside with the following
commands through gst instead of gst-remote:


gst -I seaside.im


then in the gst-shell:


Seaside.SwazooSeaside startOn:8080
Processor activeProcess suspend


and than, point your Browser to http://localhost:8080/seaside

Regards,
Joachim.




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

I know, how to start seaside without gst-remote was already described
here in the list, but I want to point out, that the problem on amd64
Systems seems gst-remote and want to mention the possible workaround in
the problem-description.

Joachim.

Joachim Jaeckel schrieb:


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

Issue status update for
http://smalltalk.gnu.org/project/issue/264
Post a follow up:
http://smalltalk.gnu.org/project/comments/add/264

 Project:      GNU Smalltalk
 Version:      <none>
-Component:    Seaside/Swazoo
+Component:    VM
 Category:     bug reports
 Priority:     normal
 Assigned to:  Unassigned
 Reported by:  Leonidas
 Updated by:   bonzinip
 Status:       active

Adjusted component and title according to latest analysis on the mailing
list.




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

Issue status update for
http://smalltalk.gnu.org/project/issue/264
Post a follow up:
http://smalltalk.gnu.org/project/comments/add/264

 Project:      GNU Smalltalk
 Version:      <none>
 Component:    VM
 Category:     bug reports
 Priority:     normal
 Assigned to:  Unassigned
 Reported by:  Leonidas
 Updated by:   bonzinip
-Status:       active
+Status:       committed

should be fixed in latest git (8fec5) -- please verify!

I still have problems with

gst-remote --start Seaside
gst-remote --package Seaside-Development

But the basic working of gst-remote is okay.




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

Hi Paolo,

did a fresh checkout (but with CVS, don't know, if that makes a
difference...) and gave the configure script a new prefix, to seperate
it from my running one.

The result:
gst-remote --daemon seems working. I see an entry of it in my
process-list, but every other attempt to connect with it like
'/opt/bin/gst-remote --eval '3 add: 5' is aborting with:

/opt/share/smalltalk/kernel/../scripts/Remote.st:276: Aborted
(ip 44)SocketAddress class>>#extractAddressesAfterLookup:
(ip 6)[] in SocketAddress class>>#allByName:
(ip 4)<unwind> BlockClosure>>#ensure:
(ip 48)[] in SocketAddress class>>#allByName:
(ip 4)[] in SocketAddress class>>#at:cache:
(ip 10)Dictionary>>#at:ifAbsent:
(ip 18)SocketAddress class>>#at:cache:
(ip 24)SocketAddress class>>#allByName:
(ip 10)SocketAddress class>>#initLocalAddresses
(ip 10)IPAddress class(SocketAddress class)>>#anyLocalAddress
(ip 28)[] in UndefinedObject>>#executeStatements
(ip 10)<unwind> BlockClosure>>#on:do:
(ip 14)UndefinedObject>>#executeStatements
(ip 0)<bottom>
Abgebrochen

(Seems to be the same error as before, isn't it?)
Maybe I did something wrong!

Regards,
Joachim.

Paolo Bonzini schrieb:


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

On Sat, 06 Jun 2009 18:39:46 +0200
Joachim Jaeckel <[hidden email]> wrote:

> Hi Paolo,
>
> did a fresh checkout (but with CVS, don't know, if that makes a
> difference...) and gave the configure script a new prefix, to
> seperate it from my running one.

I started with a fresh git clone and repeated the steps I put
down on the blog http://smalltalk.gnu.org/blog/swsch/gst-gentoo .
The most recent commit is 8fec5.

Then I repeated Joachim's steps

> gst-remote --daemon seems working. I see an entry of it in my
> process-list, but every other attempt to connect with it like
> '/opt/bin/gst-remote --eval '3 add: 5' is aborting with:
>
> /opt/share/smalltalk/kernel/../scripts/Remote.st:276: Aborted
> (ip 44)SocketAddress class>>#extractAddressesAfterLookup:

that's exactly what I'm seeing here

stefan@g128 smalltalk $ uname -a
Linux g128 2.6.27-gentoo-r7-0312 #2 SMP Thu Mar 12 08:55:33 CET 2009 x86_64 Intel(R) Core(TM)2 Duo CPU E8500 @ 3.16GHz GenuineIntel GNU/Linux

s.


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

Hmm, it's definitely fixed for me on FC10.  Can you send your
/opt/lib/smalltalk/libc.la file?

Also, can you try --server instead of --daemon (I doubt it makes a
difference, but that's what I was using here)?

Thanks,

Paolo


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

Hello Paolo,

here's my /opt/lib/smalltalk/libc.la:

# libc.la - a libtool library file
# libc.la.  Generated from libc.la.in by configure.
# Created for GNU Smalltalk's dynamic loading mechanism.

# The name that we can dlopen(3).
dlname='libc.so.6'

# Names of this library.
library_names='libc.so.6'

# Libraries that this one depends upon.
dependency_libs=''

# Is this an already installed library?
installed=yes

# Directory that this library needs to be installed in:
libdir='/lib'

Regards,
Joachim.


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

> # Directory that this library needs to be installed in:
> libdir='/lib'

Hmm, it should be /lib64 here after the patch.

Please send me the output of "gcc --print-multi-os-directory" and check
that you don't have a config.cache file lying around in the build directory.

Also check libc.la in the build directory to see if the installation was
done correctly.

Paolo


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

> Please send me the output of "gcc --print-multi-os-directory" and check
> that you don't have a config.cache file lying around in the build
> directory.

Output is: "../lib" and I've searched for a config.cache in the
smalltalk checkout directory and nothing was found.

> Also check libc.la in the build directory to see if the installation was
> done correctly.

Even in the libc.la in the smalltalk dir is the "libdir='/lib'" content.

Did today again a cvs checkout -d ... and an autoreconf -vi ./configure
make make install before I tried it and posted the message. Should I
modify the libc.la by hand to /lib64 before the make?

I don't know enough (nothing!) about the automake/autoconf etc. tools
for a build, but I know, that Debian (which is my system) uses an old
version of libtool (1.5.26) I know that ubuntu is using a much newer
version. But the newer versions have some incompatibilities...

Joachim.


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

Joachim Jaeckel wrote:
>> Please send me the output of "gcc --print-multi-os-directory" and
>> check that you don't have a config.cache file lying around in the
>> build directory.
>
> Output is: "../lib" and I've searched for a config.cache in the
> smalltalk checkout directory and nothing was found.

Ah, ok so you have /lib32 and /lib instead of /lib and /lib64 (Debian,
Ubuntu, etc.).  That should be okay then.

I'll try to reproduce it but it will take a few days.

Paolo


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

Issue status update for
http://smalltalk.gnu.org/project/issue/264
Post a follow up:
http://smalltalk.gnu.org/project/comments/add/264

 Project:      GNU Smalltalk
 Version:      <none>
 Component:    VM
 Category:     bug reports
 Priority:     normal
 Assigned to:  Unassigned
 Reported by:  Leonidas
 Updated by:   bonzinip
-Status:       committed
+Status:       fixed

reported to be fixed on the mailing list




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