[Aldor-l] Distributing Aldor

[pip88nl at gmail.com]

On Wed, Sep 10, 2008 at 12:10:08PM -0400, Bill Page wrote:
> /export/home0/wspage/aldor-1.1.0-1/src/compiler/port/opsys.c:350:
> error: 'FDIRSEP' undeclared (first use in this function)

These are not good. It looks like the aldor portability layer did not
recognise your system as anything at all. Neither UNIX, OS/2, MSDOS,
Win32, CMS, VMS nor Macintosh System 7. Can you issue the following
command:

  echo | gcc - -E -dD | grep '#define'

It shows all preprocessor symbols defined by the compiler. I might need
more information on your system later, so I can build or correct the
portability layer. What system is it? Are you working on the Solaris
system right now?

> /export/home0/wspage/aldor-1.1.0-1/src/compiler/port/opsys.c: At top level:
> /export/home0/wspage/aldor-1.1.0-1/src/compiler/port/opsys.c:1005:
> error: conflicting types for 'osMemMap'
> /export/home0/wspage/aldor-1.1.0-1/include/opsys.h:360: error:
> previous declaration of 'osMemMap' was here

This was actually a bug in Aldor itself. I fixed it with the latest
tarball.

> Error executing command: gcc -c $CFLAGS opsys.c -o opsys.s
> CFLAGS   = -g -O2 -O0 -g3 -ggdb3   -fPIC -DPIC -shared
> -D_GLIBCXX_DEBUG -D_GLIBCXX_DEBUG_PEDANTIC -D_GLIBCXX_CONCEPT_CHECKS
> -I/export/home0/wspage/aldor-1.1.0-1/extra/rona/include  -Iinclude
> -I/export/home0/wspage/aldor-1.1.0-1/include  -DIN_PORT -DIN_GENERAL
> -DIN_STRUCT -DIN_PHASES -DIN_TOPLEVEL

This looks good, just the way I want it.

> g++ -g -O2 -O0 -g3 -ggdb3 -Wno-write-strings  -fPIC -DPIC -shared -D_GLIBCXX_DEB
> UG -D_GLIBCXX_DEBUG_PEDANTIC -D_GLIBCXX_CONCEPT_CHECKS  -I/export/home0/wspage/a
> ldor-1.1.0-1/extra/rona/include  -Iinclude -I/export/home0/wspage/aldor-1.1.0-1/
> include  -DIN_RONA  -c -o /export/home0/wspage/aldor-1.1.0-1/extra/rona/rona/sca
> lar.o /export/home0/wspage/aldor-1.1.0-1/extra/rona/rona/scalar.cc
> /export/home0/wspage/aldor-1.1.0-1/extra/rona/include/rona/strings/scalar.h:711:
>  error: 'template<class T> typename rona::meta::type_if<void, rona::adt::scalar:
> :known_type<T>::value>::type rona::adt::scalar::assign(const T&)' cannot be over
> loaded
> /export/home0/wspage/aldor-1.1.0-1/extra/rona/include/rona/strings/scalar.h:704:
>  error: with 'template<class T> typename rona::meta::type_if<void, (! rona::adt:
> :scalar::known_type<T>::value)>::type rona::adt::scalar::assign(const T&)'
> /export/home0/wspage/aldor-1.1.0-1/extra/rona/include/rona/strings/scalar.h: In
> instantiation of 'rona::adt::visitor::binary_visitor_c<bool, const long int&, ro
> na::adt::visitor::addeq_predicate>':

Yeah.

> I don't really understand the make scripts yet, but maybe this shows
> an uncaught error in the compilation of the RONA library?

No, it's an error with your compiler. The Rona library contains highly
complex pieces of C++ code. I (ab)use the C++ feature "SFINAE" which Gaby
explained at the workshop in a standard compliant, but maybe not in a GCC
4.0.2 compliant way. You can safely remove scalar.cc from
extra/rona/rona/Makefile, as it is not required by Aldor.

Pippijn
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 189 bytes
Desc: Digital signature
URL: <http://mail.aldor.org/pipermail/aldor-l_aldor.org/attachments/20080910/4e4523eb/attachment-0002.bin>