Distributing Aldor

[Pippijn van Steenhoven]

Bill,

On Thu, Sep 11, 2008 at 09:44:49PM -0400, Bill Page wrote:

> Pippijn
>
> I just downloaded the msi file again 12 Sept, 2:00 Z (although the link from
>
> http://xinutec.org/~pippijn/en/projects_aldor_install.xhtml
>
> was missing). I tried the install again on another machine running
> Windows XP/SP3. This time the user interface was noticably different.
> The end result was a Aldor/Aldor REPL link in start/All Programs that
> runs "C:\Program Files\Aldor\aldor-loop.bat". But when I click this
> link a command windows flashes open and immediately closes.

The link was missing with a reason. I should have deleted the msi, as
well, to be explicit.

> I cannot seem to reproduce even getting -gloop to work on this system
> with this most recent version.

Try the very most recent version, which is now available for download.
Note that this does not yet modify the PATH variable. I will add that to
the next package.

> But then I re-considered the issue. What Windows user is likely to
> install Aldor (a compiler) if they have not previously installed some
> C compiler?

Maybe not currently, but in the future, when more people try Aldor, there
may be many that simply download my installer, install it and play around
with it. I have had several people playing around with it when fixing the
library issue, which was the reason for the breakage of the previous
packages.

> > but if I ever wanted to use the mingw crosscompiler (I have
> > already successfully built aldor with that and ran it on wine for
> > testing),
>
> I have not had particularly reliable results testing with wine. I
> would recommend running actual Windows in a VM.

I did test it with a VM, as well.

> > then they need to install the mingw native compiler.
>
> Except for licensing issues, it would be possible to include mingw in
> the windows installer for Aldor and thereby make only a single
> installation necessary. This is what we did in some versions in the
> Windows installer for the some versions of Axiom.

Yes, that is impossible with the current licence conditions.

> > Should I change these semantics and allow the user to define the
> > compiler being used?
>
> If it is possible to define the compiler at run time or even at
> installation time I think that would be great. Also provide a link to
> where users can download Visual Studio or mingw.

I will look into it. I could write some code for the installer that
searches for an existing compiler.

> Native windows in preferrable but for compatibility with some versions
> of Axiom, you might also want to consider a build of Aldor for cygwin.

I tried to set up a cross compilation environment for cygwin, but failed.
I will try again, later.

Regards,

Pippijn


_______________________________________________
Aldor-l mailing list
Aldor-l@...
http://aldor.org/mailman/listinfo/aldor-l_aldor.org

[Bill Page-7]

2008/9/12  Pippijn wrote:
>
> Try the very most recent version, which is now available for download.
> Note that this does not yet modify the PATH variable. I will add that to
> the next package.
>

Ok. Just downloaded and tried it. Aldor REPL works fine. Thanks!

> ...
> I tried to set up a cross compilation environment for cygwin, but failed.
> I will try again, later.
>

Why cross-compile?

Regards,
Bill Page.

_______________________________________________
Aldor-l mailing list
Aldor-l@...
http://aldor.org/mailman/listinfo/aldor-l_aldor.org

[Pippijn van Steenhoven]

On Fri, Sep 12, 2008 at 09:36:34AM -0400, Bill Page wrote:
> > I tried to set up a cross compilation environment for cygwin, but failed.
> > I will try again, later.
>
> Why cross-compile?

Because the disk space on my windows VM is very limited.

Pippijn


_______________________________________________
Aldor-l mailing list
Aldor-l@...
http://aldor.org/mailman/listinfo/aldor-l_aldor.org

[Bill Page-7]

Pippijn,

I still have not had any success building your version of Aldor from
source on any of my systems. :-(  My most recent attempt was on a
Debian 5.0 (Lenny, beta 2) x86 system. First I tried your debian
package but that failed with a message about 'libssp0' which doesn't
seem to be available in Lenny:

debian:/home/wspage# apt-get install aldor
Reading package lists... Done
Building dependency tree
Reading state information... Done
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.

Since you only requested a single operation it is extremely likely that
the package is simply not installable and a bug report against
that package should be filed.
The following information may help to resolve the situation:

The following packages have unmet dependencies:
  aldor: Depends: libfoam-aldor (= 1.1.0-1) but it is not going to be installed
         Depends: libssp0 (>= 4.1.1-12) but it is not installable
E: Broken packages

debian:/home/wspage# apt-cache search libssp
gcc-4.1 - The GNU C compiler

----

Maybe it is associated with a previous version of the gcc? It looks
like it is only found in etch:

http://packages.debian.org/search?suite=default§ion=all&arch=any&searchon=names&keywords=libssp0

----

Then I tried building from source. But I get an error while it tries
to build the rona library. Here is the tail end of the build log:

...

Linking as C++
        LD     /home/wspage/aldor-1.1.0-1/obj/lib/librona.so
10:21:15   >> building os
       CXX     /home/wspage/aldor-1.1.0-1/extra/rona/rona/os/environ.s
        AS     /home/wspage/aldor-1.1.0-1/extra/rona/rona/os/environ.o
       CXX     /home/wspage/aldor-1.1.0-1/extra/rona/rona/os/path.s
/home/wspage/aldor-1.1.0-1/extra/rona/rona/os/path.cc: In function
âstd::__debug::vector<std::basic_string<char, std::char_traits<char>,
std::allocator<char> >, std::allocator<std::basic_string<char,
std::char_traits<char>, std::allocator<char> > > >
rona::os::path::listdir(const std::string&)â:
/home/wspage/aldor-1.1.0-1/extra/rona/rona/os/path.cc:56: error:
âstrerrorâ was not declared in this scope
Error executing command: g++ -c $CXXFLAGS path.cc -o path.s
CXXFLAGS = -g -O2 -O0 -g3 -ggdb3 -fstack-protector-all
-Wno-write-strings  -fPIC -DPIC -D_GLIBCXX_DEBUG
-D_GLIBCXX_DEBUG_PEDANTIC -D_GLIBCXX_CONCEPT_CHECKS
-I/home/wspage/aldor-1.1.0-1/extra/rona/include  -Iinclude
-I/home/wspage/aldor-1.1.0-1/include  -DIN_RONA_OS
make[6]: *** [/home/wspage/aldor-1.1.0-1/extra/rona/rona/os/path.s] Error 1
make[5]: *** [os.build.tag] Error 1
make[4]: *** [build] Error 1
make[3]: *** [rona.build.tag] Error 1
make[2]: *** [build] Error 1
make[1]: *** [src.build.tag] Error 1
make: *** [build] Error 1
wspage@debian:~/aldor-1.1.0-1$

-----

Any ideas?

Regards,
Bill Page.

_______________________________________________
Aldor-l mailing list
Aldor-l@...
http://aldor.org/mailman/listinfo/aldor-l_aldor.org