[M3devel] Auto-discard notification

[Olaf Wagner]

You need to subscribe to the list to be able to post to it.

However, I can quickly answer some of your questions:

  o You need to use the script upgrade.sh or upgrade.py to perform a
    full core system upgrade from source. This bootstraps the compiler
    and runtime libraries using an existing compiler and installs
    everything it has built. "install-cm3-compiler.sh upgrade" will just
    install a compiler from your workspace.

  o Failures in the packages odbc, postgres95, and db are most likely
    due to missing libraries on your system. Just install the needed
    third party packages for this software with the appropriate tools
    for your system (e.g. pkg_add, apt-get, ...) and adapt the
    library paths in the cm3 config files if they still aren't found.
    Have a look at /usr/local/cm3/bin/cm3.cfg and its includes.

  o If the packages are missing, that should not be a problem, too,
    as long as you don't need their functionality.

Hope this helps,

Olaf

Quoting m3devel-bounces at elegosoft.com:

> The attached message has been automatically discarded.

My CM3 build was getting pretty old, so I decided to re-install
from scratch, and came across a number of problems whose solution
wasn't obvious.  Could someone please confirm that I got the
answers right?  (This was on a current x86 Linux box.)

I installed from the cm3-bin-core tarfile, which gave me a basic
m3 compiler and linker.

I then tried installing from the cm3-src-all tarfile, with the
command:
   install-cm3-compiler.sh upgrade
since I wanted to force a compiler upgrade for various reasons.

Should I have used do-cm3-core.sh buildship as well?  Could I
have used do-cm3-core.sh instead, if I didn't want to rebuild
the compiler?

I then tried:
   do-cm3-std.sh buildship
which failed on the packages odbc, postgres95, and db (smalldb
built correctly).  This is where I ran into real problems, since
I couldn't find any documentation on the packages to be built,
or a way of restarting a failed build.  I finally decided that
pkginfo.txt was the one, and edited it. Re-running do-cm3-std
then got me a working system.

Was this the right approach, and does the pkginfo.txt format
allow for commenting out lines (I just deleted the successful
packages), and if so what is the comment symbol (; ? # ?).

Is there an easier way to restart a failed build?

Is any of this documented anywhere?

-- 
Olaf Wagner -- elego Software Solutions GmbH
                Gustav-Meyer-Allee 25 / Gebäude 12, 13355 Berlin, Germany
phone: +49 30 23 45 86 96  mobile: +49 177 2345 869  fax: +49 30 23 45 86 95
    http://www.elegosoft.com | Geschäftsführer: Olaf Wagner | Sitz: Berlin
Handelregister: Amtsgericht Charlottenburg HRB 77719 | USt-IdNr: DE163214194