Trouble to compile a CVS version on mac.

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
5 messages Options
Reply | Threaded
Open this post in threaded view
|

Trouble to compile a CVS version on mac.

Mathieu Suen-2
Hi All,

I am having some trouble to compile the source from cvs on Mac

Here the output:

smalltalk $  autoconf -fvi
autoconf: invalid option -fvi
Try `autoconf --help' for more information.
smalltalk $  autoconf
configure.ac:1: error: possibly undefined macro: dnl
       If this token and others are legitimate, please use  
m4_pattern_allow.
       See the Autoconf documentation.
configure.ac:21: error: possibly undefined macro: AM_CONFIG_HEADER
configure.ac:22: error: possibly undefined macro: AM_INIT_AUTOMAKE
configure.ac:60: error: possibly undefined macro: AM_PATH_LISPDIR
configure.ac:63: error: possibly undefined macro: AM_CONDITIONAL
configure.ac:67: error: possibly undefined macro: AM_MISSING_PROG
configure.ac:81: error: possibly undefined macro:  
AC_SNPRINTFV_CONVENIENCE
configure.ac:84: error: possibly undefined macro: AC_ARG_ENABLE
configure.ac:154: error: possibly undefined macro: AC_LIBTOOL_TAGS
configure.ac:155: error: possibly undefined macro: AC_LIBTOOL_DLOPEN
configure.ac:156: error: possibly undefined macro: AC_LIBTOOL_WIN32_DLL
configure.ac:157: error: possibly undefined macro: AC_PROG_LIBTOOL
configure.ac:182: error: possibly undefined macro: _LT_AC_TAGVAR
configure.ac:243: error: possibly undefined macro: AC_CHECK_FUNCS_ONCE
configure.ac:254: error: possibly undefined macro: AC_LIB_LTDL
configure.ac:289: error: possibly undefined macro: AC_CHECK_HEADER
configure.ac:309: error: possibly undefined macro: AM_PATH_GLIB_2_0
configure.ac:310: error: possibly undefined macro: AM_PATH_GTK_2_0
configure.ac:330: error: possibly undefined macro: AM_LANGINFO_CODESET
configure.ac:331: error: possibly undefined macro: AM_ICONV
smalltalk $  ./configure
./configure: line 1787: syntax error near unexpected token `7:0:0'
./configure: line 1787: `GST_REVISION(7:0:0)'

Thanks


        Mth




       

       
               
___________________________________________________________________________
Yahoo! Mail réinvente le mail ! Découvrez le nouveau Yahoo! Mail et son interface révolutionnaire.
http://fr.mail.yahoo.com



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

Re: Trouble to compile a CVS version on mac.

Paolo Bonzini-2
Mathieu Suen wrote:
> Hi All,
>
> I am having some trouble to compile the source from cvs on Mac
>
> Here the output:
>
> smalltalk $  autoconf -fvi

That should have been "autoreconf -fvi".  If you still have problems,
just download 3.0.

Paolo


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

Re: Trouble to compile a CVS version on mac.

Damien Pollet
On 30/01/2008, Paolo Bonzini <[hidden email]> wrote:
> > I am having some trouble to compile the source from cvs on Mac
> >
> > Here the output:
> >
> > smalltalk $  autoconf -fvi
>
> That should have been "autoreconf -fvi".  If you still have problems,
> just download 3.0.

it's in macports now,
      sudo port install gst
should work

--
Damien Pollet
type less, do more [ | ] http://typo.cdlm.fasmz.org


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

Re: Trouble to compile a CVS version on mac.

Mathieu Suen-2

Now it work.
I was looking for how do you booostrap the system.
Do you have some doc, paper on it?

Thanks

On Jan 30, 2008, at 5:04 PM, Damien Pollet wrote:

> On 30/01/2008, Paolo Bonzini <[hidden email]> wrote:
>>> I am having some trouble to compile the source from cvs on Mac
>>>
>>> Here the output:
>>>
>>> smalltalk $  autoconf -fvi
>>
>> That should have been "autoreconf -fvi".  If you still have problems,
>> just download 3.0.
>
> it's in macports now,
>      sudo port install gst
> should work
>
> --
> Damien Pollet
> type less, do more [ | ] http://typo.cdlm.fasmz.org

        Mth




       

       
               
___________________________________________________________________________
Yahoo! Mail réinvente le mail ! Découvrez le nouveau Yahoo! Mail et son interface révolutionnaire.
http://fr.mail.yahoo.com



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

Bootstrapping a Smalltalk image

Paolo Bonzini-2
Mathieu Suen wrote:
>
> Now it work.
> I was looking for how do you booostrap the system.
> Do you have some doc, paper on it?

The source code is dict.c and files.c.  Here is a short LaTeX document
that describes it (you can of course read it from here).

Paolo




\documentclass{article}
\usepackage{hyperref}
\begin{document}

\newcommand{\code}[1]{%
   \texorpdfstring{%
      {\texttt{\hyphenchar\font=`-%
        \begingroup\protect\frenchspacing#1\endgroup}}}{%
      #1}}

Unlike most other image-based Smalltalk systems, GNU Smalltalk is
able to create an image from scratch, only starting from the
definitions of the base classes and the source code to them (that is,
the definitions are not expressed as Smalltalk source code, but
separately).  Other systems, instead, always create an image from a
pre-existing one, possibly stripping out unneeded components.

The bootstrapping process is complex due to the necessity of
recreating the parallel hierarchy of classes and metaclasses, and then
merging them together.

First of all, the system creates the builtin objects (nil, true, false
and the 256 instances of \code{Character}).  The pointer to their
class is not known yet, but the system can store pointers to them even
if they are still in an embryonal state: it is easier to plug the 259
pointers to the classes \code{UndefinedObject}, \code{True},
\code{False} and \code{Character}, than to put back all the pointers
to \code{nil} where they are needed.

As mentioned, the virtual machine code contains the description on the
core classes\footnote{It would be possible to load them from an
   external source, with a parser for a subset of Smalltalk or from an
   XML description.}.  The hierarchy tree is visited breadth-first,
creating classes and metaclasses along the way.  A few fields are
initialized in class objects: the superclass field, the pointer to the
metaclass, and the \code{instanceSpec}. This is enough for the system to
create their instances.

Now, builtin objects are given a class and other objects can be
created: these include namespaces, and some \code{VariableBinding}
objects through which the virtual machine can pass some information
about the system to the Smalltalk code\footnote{Such as the underlying
operating system, or \code{sizeof(void *)}.}.  C code manipulates
namespaces and fills them with \code{VariableBinding} objects for the
classes.

The remaining fields of class and metaclass objects are filled in,
including linking metaclasses back to their sole instance, making
Metaclass the class of metaclasses and making Class the superclass of
`Object class'.

In order to compile the source code for the core classes, GNU
Smalltalk includes a compiler written in C.  This compiler is invoked
once manually to compile the \code{methodsFor:} primitive, and then to
file in the sources for the kernel. As more and more classes are loaded,
the system takes shape: later on, it will be complete enough to be able
to create new classes, and possibly to run another compiler which is
written in Smalltalk.  At this point, the system has bootstrapped.

\end{document}


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