Re: Building on linux

Hi Prunedtree,

What is the best way to keep up to date with your changes and changes
to mainline? Have your linux changes been merged with the main
repository? Is there any chance you can work on a branch so I can get
a sneak peak at your changes without having to wait for them to be
reviewed and merged to the mainline branch?

I presume I can tell gcc to make 32-bit object files and binaries (I
need to find out how to do that). But at least it seems I already have
a populated /usr/lib32 directory. What is needed until at least a
command line vm and image can be run? I presume the starting point is
getting all unit tests to succeed. (More reading on my part to find
out where and what the unit tests are). If one has a bunch of
strongtalk sources can one build an image using the vm, or is the
strongtalk parser written in strongtalk?

regards,

Richard.



On May 11, 2:56 am, prunedtree <[email protected]> wrote:
> On May 11, 8:34 am, Richard <[email protected]> wrote:
>
> > Hi,
>
> > I downloaded these sources and started trying to build them with
> > Eclipse CDT and GCC 4.1 on Debian-Etch- AMD64. There was no makefile
> > that I could find so I made one that includes all the directories and
> > all the sources and has directives you listed as well the defines from
> > the VisualC project files.
>
> That's right. Note that you can't get a running binary "as is" because
> there's nolinux-specific code yet.
>
> > So now g++ is complaining about:
>
> > dll.hpp:51          int tag() const { return maskBits(int(this),
> > Tag_Mask); }
>
> > g++ says this expression is lossing precision. I did a quick check,
> > sizeof(int)=4, but sizeof(void *)=8. How widespread do you think the
> > assumption in this code that pointers are 4 bytes is? Have I any hope
> > of making this 64-bit clean?
>
> None. Too much code is dependent on the ISA, like all the assembly
> code and the compiler.
> You should run in 32-bit mode on x86-64 cpus.
>
>
>
> > Something less important that I don't understand is what is going on
> > with the deps directory and the x.cpp.incl files? Is there some tool
> > which is automagically detecting which includes each cpp file needs?
>
> no, the tool uses a dependency database (look at includeDB &
> includeDB2)
>
> > There's a capitalization problem with eventlog.hpp (it is sometimes
> > listed as eventLog.hpp which is no good for unix systems).
>
> I think david changed things related to eventLog in r45, but my
> changes are based on r36.
> It looks like the correct capitalization is eventLog.
>
> cheers,
> prunedtree
>
>
>
> > regards,
>
> > Richard.


--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "Strongtalk-general" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [email protected]
For more options, visit this group at http://groups.google.com/group/strongtalk-general?hl=en
-~----------~----~----~----~------~----~------~--~---