Am Montag, 18. Dezember 2006 04:50 schrieb chromatic via RT:
> On Mon May 09 07:36:14 2005, leo wrote:
> > If you are embedding or extending Parrot and linked against libparrot
> > you now have to additionally link with one of:
> >
> >src/null_config.o
> >src/parrot_config.o # prefix :
Leopold Toetsch (via RT) wrote:
If you are embedding or extending Parrot and linked against libparrot
you now have to additionally link with one of:
src/null_config.o
src/parrot_config.o # prefix := build-dir
src/install_config.o # prefix := --prefix dir
leo
Leopold Toetsch (via RT) wrote:
3) "make install" creates src/parrot_config_install.c and links that
into parrot_install$EXE, which during installation becomes
.../bin/parrot$EXE. With this step we get rid of the problem with
runtime vs build directory library usage.
Done (rev 8028), with slight
Leopold Toetsch (via RT) wrote:
1) We have F, which is a frozen
image of the config hash generated by F. Creating the
frozen image needs already parrot (a possibly already existing parrot or
miniparrot in the long run). But locating this file needs the library or
include path, with resides in t
On 15 Apr, Leopold Toetsch wrote:
: That stuff is all in Perl code under the config dir, e.g:
:
: $ find config -type f | xargs grep -w intsize
This clarifies some of my unapproved assumptions, although src has
some files containing these keywords too.
: I think we should have:
:
:INTVAL_t
Steven Philip Schubiger wrote:
[ cc'ed list, so that folks know about takers ]
On 15 Apr, Leopold Toetsch wrote:
: 5) along with bringing the config online, some cleanup and renaming
: wouldn't harm e.g. "iv" vs "opcode_t", "intvalsize" vs "intsize" vs
: "opcode_t_size" ...
This part seems appea
# New Ticket Created by Leopold Toetsch
# Please include the string: [perl #34994]
# in the subject line of all future correspondence about this issue.
# https://rt.perl.org/rt3/Ticket/Display.html?id=34994 >
A Python example first:
$ python
>>> import sys
>>> print sys.maxint
2147483647
