[MonetDB-users] Cannot compile MonetDB_4-24
Thanks for your help, however I still cannot compile.
Actually, I just need to work with most current versions of Pathfinder, and maybe try some other branches of that one as well, until I find out where the fixes end up, and which one works for me. Unortunately I was unable to find a detailed description of which branches of what modules are required to build which other branches of whatever modules I need anyway.
If someone would be so kind as to show me how I can achieve this without touching CVS, I would be deeply grateful.
Until then, I'll try to follow the CVS trail.
On 17 July 2008, Stefan Manegold wrote with possible deletions:
In case you prefer to use the CVS sources, and you do not require the latest cutting-edge (potentially instable) development version we recommend to checkout the latest Stable branches. I ust realize that the respective branch tags are not (yet?) listed on the MonetDB web site, hence I'll share them here:
buildtools: MonetDB_1-24 MonetDB: MonetDB_1-24 clients: Clients_1-24 MonetDB4: MonetDB_4-24 MonetDB5: MonetDB_5-6 pathfinder: XQuery_0-24 sql: SQL_2-24 geom: Geom_0-4
Thank you for this information, but compilation fails for MonetDB4 on the 'make' command with the following error message:
/home/sk/opt/MonetDB/include/MonetDB/gdk/gdk_system.h:117: error: expected ‘)’ before ‘*’ token
A detailed description of what I did is in the attached 'report' file, which actually is a bash script. The resulting logfile [1] from
report 2>&1 | tee logfile
is available for download.
Kind regards Stefan
____________________ [1] logfile, link valid for one week, 409565 Bytes https://depot.uni-konstanz.de/get/72fwr6
Stefan,
On Fri, Jul 18, 2008 at 02:35:01PM +0200, Stefan Klinger wrote:
Thanks for your help, however I still cannot compile.
Actually, I just need to work with most current versions of Pathfinder,
The most current *released*/*stable* version or the most current *development* version?
and maybe try some other branches of that one as well, until I find out
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ There are no "other branches" of the most current version of Pathfinder, other than the latest release/stable branch and the development trunk.
where the fixes end up, and which one works for me. Unortunately I was
fixes end up where they belong: fixes that (also) apply to the latest released version go to the latest stable branch (first and are then automatically propagated to the development trunk), fixes tha apply to the development trunk (only) go there (only).
unable to find a detailed description of which branches of what modules are required to build which other branches of whatever modules I need anyway.
For the latest release, I gave you the detailed list (see below). For the development trunk, at least the latest stable release of each required module is required. In fact, due to ongoing development, the latest development versions of required modules might be required. This is the case for the lastest development version of pathfinder right now. The requirements/depencies are maintained in and checked by our configure scripts. The detailed description of "whatever modules" you "need anyway" is to be found on the MonetDB web site at http://monetdb.cwi.nl/Download/Packages/ and/or http://monetdb.cwi.nl/projects/monetdb//MonetDB/Documentation/Experts.html and/or http://monetdb.cwi.nl/projects/monetdb//MonetDB/Documentation/Linux-Installa...
If someone would be so kind as to show me how I can achieve this without touching CVS, I would be deeply grateful.
As far as I know, the monetdb-install.sh script only allows to choose between either all (desired/required) packages from the latest stable release or all from the current development trunk.
Until then, I'll try to follow the CVS trail.
Fine with me.
On 17 July 2008, Stefan Manegold wrote with possible deletions:
In case you prefer to use the CVS sources, and you do not require the latest cutting-edge (potentially instable) development version we recommend to checkout the latest Stable branches. I ust realize that the respective branch tags are not (yet?) listed on the MonetDB web site, hence I'll share them here:
buildtools: MonetDB_1-24 MonetDB: MonetDB_1-24 clients: Clients_1-24 MonetDB4: MonetDB_4-24 MonetDB5: MonetDB_5-6 pathfinder: XQuery_0-24 sql: SQL_2-24 geom: Geom_0-4
Thank you for this information, but compilation fails for MonetDB4 on the 'make' command with the following error message:
/home/sk/opt/MonetDB/include/MonetDB/gdk/gdk_system.h:117: error: expected ‘)’ before ‘*’ token
Would mind sharing with us, on which platform (HW, OS, version) you try to compile MonetDB, and which tools (incl. version numbers) you are using: autoconf automake libtool lex/flex yacc/bison compiler ?
Would you mind sharing with us, what line, say, 110 - 123 of your /home/sk/opt/MonetDB/include/MonetDB/gdk/gdk_system.h look like?
Stefan
A detailed description of what I did is in the attached 'report' file, which actually is a bash script. The resulting logfile [1] from
report 2>&1 | tee logfile
is available for download.
Kind regards Stefan
[1] logfile, link valid for one week, 409565 Bytes https://depot.uni-konstanz.de/get/72fwr6
-- Stefan Klinger o/klettern // bis zum send plaintext only - max size 32kB - no spam \ Abfallen http://stefan-klinger.de
#!/bin/bash
# I've been running this script in a new empty directory, using the command # report 2>&1 | tee logfile
function err { xmessage ERROR & exit 1; } function succ { xmessage SUCCESS "$@" & }
prefix="${HOME}/opt/MonetDB" export MAKEOPTS='-j2' echo "PATH is ${PATH}";
rm -rf "${prefix}"
echo '#################### build tools' cvs -d:pserver:anonymous@monetdb.cvs.sourceforge.net:/cvsroot/monetdb checkout -r MonetDB_1-24 buildtools ||err test -d buildtools ||err pushd buildtools ./bootstrap ||err ./configure --prefix="${prefix}" ||err make ||err make install ||err popd succ build tools
echo '#################### MonetDB' cvs -d:pserver:anonymous@monetdb.cvs.sourceforge.net:/cvsroot/monetdb checkout -r MonetDB_1-24 MonetDB ||err test -d MonetDB ||err pushd MonetDB export PYTHONPATH="${prefix}/$(python -c 'import distutils.sysconfig; print distutils.sysconfig.get_python_lib(0,0,"")')" ||err ./bootstrap ||err mkdir build && cd build ||err ../configure --prefix="${prefix}" ||err make ||err make install ||err popd succ MonetDB
echo '#################### clients' cvs -d:pserver:anonymous@monetdb.cvs.sourceforge.net:/cvsroot/monetdb checkout -r Clients_1-24 clients ||err test -d clients ||err pushd clients ./bootstrap ||err ./configure --prefix="${prefix}" ||err make ||err make install ||err popd succ clients
echo '#################### MonetDB4' cvs -d:pserver:anonymous@monetdb.cvs.sourceforge.net:/cvsroot/monetdb checkout -r MonetDB_4-24 MonetDB4 ||err test -d MonetDB4 ||err pushd MonetDB4 ./bootstrap ||err ./configure --prefix="${prefix}" ||err make ||err make install ||err popd succ MonetDB4
# echo '#################### pathfinder' #cvs -d:pserver:anonymous@monetdb.cvs.sourceforge.net:/cvsroot/monetdb checkout -r XQuery_0-24 pathfinder #pushd pathfinder #./configure --prefix="${HOME}/opt/MonetDB"
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/ _______________________________________________ MonetDB-users mailing list MonetDB-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/monetdb-users
On Fri, Jul 18, 2008 at 03:40:09PM +0200, Stefan Manegold wrote:
A detailed description of what I did is in the attached 'report' file, which actually is a bash script. The resulting logfile [1] from
report 2>&1 | tee logfile
ps: Is there any particular reason why you use a separate build dir only for MonetDB, but call configure in the top-level source dir for all other packages? To keep the source tree clean, we always reccomend to use a separate build dir in all cases.
is available for download.
Kind regards Stefan
On 18 July 2008, Stefan Manegold wrote with possible deletions:
ps: Is there any particular reason why you use a separate build dir only for MonetDB, but call configure in the top-level source dir for all other packages? To keep the source tree clean, we always reccomend to use a separate build dir in all cases.
No, not really. But the MonetDB package was the only one where I stumbled over an according hint. Generally I tar-bzip2 directories checked out, and in case something fails with the build, I remove the (polluted) dir and unpack the original. Besides, I think 'configure' in a seperate directory is a bit unusual, and I did not want to break things.
Kind regards, Stefan
On Fri, Jul 18, 2008 at 03:40:09PM +0200, Stefan Manegold wrote: [...]
If someone would be so kind as to show me how I can achieve this without touching CVS, I would be deeply grateful.
As far as I know, the monetdb-install.sh script only allows to choose between either all (desired/required) packages from the latest stable release or all from the current development trunk.
see `monetdb-install.sh --help` for details.
Stefan
On 18 July 2008, Stefan Manegold wrote with possible deletions:
see `monetdb-install.sh --help` for details.
To be honest, this just added to my confusion: There are nightly checkouts, tarballs, branches and a trunk, stable/current/development, and even tags...
I can download tarballs, checkout via CVS, or use the install-script.
This makes three methods to retrieve the sources, and a lot of sources to choose from. I simply lost orientation when choosing the right combination for me.
But don't take this personally, I know that you provide each of these methods for a good reason, and that you actually do a good job.
Kind regards, Stefan
On 21-07-2008 12:20:56 +0200, Stefan Klinger wrote:
On 18 July 2008, Stefan Manegold wrote with possible deletions:
see `monetdb-install.sh --help` for details.
To be honest, this just added to my confusion: There are nightly checkouts, tarballs, branches and a trunk, stable/current/development, and even tags...
I can download tarballs, checkout via CVS, or use the install-script.
This makes three methods to retrieve the sources, and a lot of sources to choose from. I simply lost orientation when choosing the right combination for me.
Let me try to help you understand our maze.
quote: --nightly=target download and install a nightly snapshot of the stable or current branch, target must be 'stable' or 'current' --cvs checkout a CVS snapshot of the current branch
Now, first thing, the monetdb-install.sh script is a little helper, it does nothing more than executing some commands to help you get the complex process of getting a useful MonetDB instance running. The script itself is not a "distribution" at all, it is only a mere meta-file. Second, that you get confused in the jungle of branches, tags, releases, snapshots and more of that is quite understandable. However that seems to be the faith of MonetDB. Hence, the monetdb-install.sh script tries to help you again here.
Referring to the quote now, there are two options that in total select 3 out of the maze of branches, etc. To make it easier, in fact, MonetDB knows (short version) only two "branches", a "current" and a "stable" branch. Of course these branches remain in CVS, where our development is tracked. The --cvs option to monetdb-install.sh simply selects the "current" branch (you cannot choose), and makes a CVS checkout for that. With that option you get really up-to-date sources, but that comes at the price of needing more tools to build, which may be missing on your system. Exactly for that reason we do some preparatory steps on the CVS sources every night, removing most of the build tool requirements. We call those "prepared" sources "nightly snapshots". That is where the --nightly option comes in. If you don't require bleeding edge up-to-date sources, you best take a nightly snapshot. The only thing here, is that you have to choose: do you want the "current" or "stable" branch? Roughly, the "stable" branch means the latest release + bugfixes that we applied. The "current" branch contains new features and ground-breaking improvements. If you're looking for a solid and stable playground, you best take the "stable" branch (--nightly=stable). If you are adventurous, and require new features, you best take the "current" branch. Note that when using --cvs you implicitly belong to this brave adventurous group of people ;)
I hope this clears up the confusion a bit.
Thank you Stefan!
I'll answer all your questions below. The information about which trunks exist really helps, since I don't have an overview, and I'm also not an experienced CVS user.
On 18 July 2008, Stefan Manegold wrote with possible deletions:
The most current *released*/*stable* version or the most current *development* version?
Jan fixed a bug in Pathfinder for me, and I need to test it. He said that fix went to the stable branch, so I think I have to use that one. However, I'd like to be preared in case I need to use the development branch.
Would mind sharing with us, on which platform (HW, OS, version) you try to compile MonetDB, and which tools (incl. version numbers) you are using:
Hardware: Two Intel Core2 Duo CPUs at 2.00GHz (/proc/cpuinfo), total memory is 2068152kB (/proc/meminfo).
OS: Debian GNU/Linux lenny/sid, latest upgrade was Jul 20 2008 12:22:11 +0200. The kernel is Linux 2.6.25-2-686 (uname -a)
tools: Some of the tools are hidden behind symlinks. If so, I listed them in the usual '->' notation.
autoconf --version
autoconf (GNU Autoconf) 2.61
/usr/bin/automake -> /etc/alternatives/automake /etc/alternatives/automake -> /usr/bin/automake-1.10
automake --version
automake (GNU automake) 1.10.1
libtool --version
ltmain.sh (GNU libtool) 1.5.26 Debian 1.5.26-4 (1.1220.2.493 2008/02/01 16:58:18)
flex --version
flex 2.5.35
/usr/bin/lex -> flex
/usr/bin/yacc -> /etc/alternatives/yacc /etc/alternatives/yacc -> /usr/bin/byacc
yacc -V
yacc - 1.9 20070509
bison: not installed
/usr/bin/gcc -> gcc-4.3
gcc -v
Using built-in specs. Target: i486-linux-gnu Configured with: ../src/configure -v --with-pkgversion='Debian 4.3.1-2' --with-bugurl=file:///usr/share/doc/gcc-4.3/README.Bugs --enable-languages=c,c++,fortran,objc,obj-c++ --prefix=/usr --enable-shared --with-system-zlib --libexecdir=/usr/lib --without-included-gettext --enable-threads=posix --enable-nls --with-gxx-include-dir=/usr/include/c++/4.3 --program-suffix=-4.3 --enable-clocale=gnu --enable-libstdcxx-debug --enable-objc-gc --enable-mpfr --enable-targets=all --enable-cld --enable-checking=release --build=i486-linux-gnu --host=i486-linux-gnu --target=i486-linux-gnu Thread model: posix gcc version 4.3.1 (Debian 4.3.1-2)
Would you mind sharing with us, what line, say, 110 - 123 of your /home/sk/opt/MonetDB/include/MonetDB/gdk/gdk_system.h look like?
Here are lines 107-132, you may download the whole file here [1].
typedef size_t MT_Id; /* thread number. will not be zero */
gdk_export int MT_create_thread(MT_Id *t, void (*function) (void *), void *arg); gdk_export void MT_exit_thread(int status); gdk_export void MT_global_exit(int status); gdk_export MT_Id MT_getpid(void); gdk_export int MT_join_thread(MT_Id t); gdk_export int MT_kill_thread(MT_Id t);
#ifdef HAVE_PTHREAD_SIGMASK gdk_export void MT_thread_sigmask(sigset_t * new_mask, sigset_t * orig_mask); #endif
gdk_export MT_Id MT_locktrace;
#if SIZEOF_VOID_P == 4 /* "limited" stack size on 32-bit systems */ /* to avoid address space fragmentation */ #define THREAD_STACK_SIZE ((size_t)2*512*1024) #else /* "increased" stack size on 64-bit systems */ /* since some compilers seem to require this */ /* for burg-generated code in pathfinder */ /* and address space fragmentation is no issue */ #define THREAD_STACK_SIZE ((size_t)4*512*1024) #endif
Thank you very much!!! Stefan
____________________ [1] File 'gdk_system.h', link valid for seven days. https://depot.uni-konstanz.de/get/7clrlt
Stefan Klinger wrote:
Thank you Stefan!
I'll answer all your questions below. The information about which trunks exist really helps, since I don't have an overview, and I'm also not an experienced CVS user.
On 18 July 2008, Stefan Manegold wrote with possible deletions:
The most current *released*/*stable* version or the most current *development* version?
Jan fixed a bug in Pathfinder for me, and I need to test it. He said that fix went to the stable branch, so I think I have to use that one. However, I'd like to be preared in case I need to use the development branch.
Would mind sharing with us, on which platform (HW, OS, version) you try to compile MonetDB, and which tools (incl. version numbers) you are using:
Hardware: Two Intel Core2 Duo CPUs at 2.00GHz (/proc/cpuinfo), total memory is 2068152kB (/proc/meminfo).
OS: Debian GNU/Linux lenny/sid, latest upgrade was Jul 20 2008 12:22:11 +0200. The kernel is Linux 2.6.25-2-686 (uname -a)
tools: Some of the tools are hidden behind symlinks. If so, I listed them in the usual '->' notation.
autoconf --version
autoconf (GNU Autoconf) 2.61
/usr/bin/automake -> /etc/alternatives/automake /etc/alternatives/automake -> /usr/bin/automake-1.10
automake --version
automake (GNU automake) 1.10.1
libtool --version
ltmain.sh (GNU libtool) 1.5.26 Debian 1.5.26-4 (1.1220.2.493 2008/02/01 16:58:18)
flex --version
flex 2.5.35
Hi Stefan,
I remember I got some compilation issues with flex 2.5.34; switching back to 2.5.33 solved them. Hope this helps you!
Marco
/usr/bin/lex -> flex
/usr/bin/yacc -> /etc/alternatives/yacc /etc/alternatives/yacc -> /usr/bin/byacc
yacc -V
yacc - 1.9 20070509
bison: not installed
/usr/bin/gcc -> gcc-4.3
gcc -v
Using built-in specs. Target: i486-linux-gnu Configured with: ../src/configure -v --with-pkgversion='Debian 4.3.1-2' --with-bugurl=file:///usr/share/doc/gcc-4.3/README.Bugs --enable-languages=c,c++,fortran,objc,obj-c++ --prefix=/usr --enable-shared --with-system-zlib --libexecdir=/usr/lib --without-included-gettext --enable-threads=posix --enable-nls --with-gxx-include-dir=/usr/include/c++/4.3 --program-suffix=-4.3 --enable-clocale=gnu --enable-libstdcxx-debug --enable-objc-gc --enable-mpfr --enable-targets=all --enable-cld --enable-checking=release --build=i486-linux-gnu --host=i486-linux-gnu --target=i486-linux-gnu Thread model: posix gcc version 4.3.1 (Debian 4.3.1-2)
Would you mind sharing with us, what line, say, 110 - 123 of your /home/sk/opt/MonetDB/include/MonetDB/gdk/gdk_system.h look like?
Here are lines 107-132, you may download the whole file here [1].
typedef size_t MT_Id; /* thread number. will not be zero */
gdk_export int MT_create_thread(MT_Id *t, void (*function) (void *), void *arg); gdk_export void MT_exit_thread(int status); gdk_export void MT_global_exit(int status); gdk_export MT_Id MT_getpid(void); gdk_export int MT_join_thread(MT_Id t); gdk_export int MT_kill_thread(MT_Id t);
#ifdef HAVE_PTHREAD_SIGMASK gdk_export void MT_thread_sigmask(sigset_t * new_mask, sigset_t * orig_mask); #endif
gdk_export MT_Id MT_locktrace;
#if SIZEOF_VOID_P == 4 /* "limited" stack size on 32-bit systems */ /* to avoid address space fragmentation */ #define THREAD_STACK_SIZE ((size_t)2*512*1024) #else /* "increased" stack size on 64-bit systems */ /* since some compilers seem to require this */ /* for burg-generated code in pathfinder */ /* and address space fragmentation is no issue */ #define THREAD_STACK_SIZE ((size_t)4*512*1024) #endif
Thank you very much!!! Stefan
[1] File 'gdk_system.h', link valid for seven days. https://depot.uni-konstanz.de/get/7clrlt
On Mon, Jul 21, 2008 at 02:48:26PM +0200, Marco Antonelli wrote:
Stefan Klinger wrote:
Thank you Stefan!
I'll answer all your questions below. The information about which trunks exist really helps, since I don't have an overview, and I'm also not an experienced CVS user.
On 18 July 2008, Stefan Manegold wrote with possible deletions:
The most current *released*/*stable* version or the most current *development* version?
Jan fixed a bug in Pathfinder for me, and I need to test it. He said that fix went to the stable branch, so I think I have to use that one. However, I'd like to be preared in case I need to use the development branch.
Would mind sharing with us, on which platform (HW, OS, version) you try to compile MonetDB, and which tools (incl. version numbers) you are using:
Hardware: Two Intel Core2 Duo CPUs at 2.00GHz (/proc/cpuinfo), total memory is 2068152kB (/proc/meminfo).
OS: Debian GNU/Linux lenny/sid, latest upgrade was Jul 20 2008 12:22:11 +0200. The kernel is Linux 2.6.25-2-686 (uname -a)
tools: Some of the tools are hidden behind symlinks. If so, I listed them in the usual '->' notation.
autoconf --version
autoconf (GNU Autoconf) 2.61
/usr/bin/automake -> /etc/alternatives/automake /etc/alternatives/automake -> /usr/bin/automake-1.10
automake --version
automake (GNU automake) 1.10.1
libtool --version
ltmain.sh (GNU libtool) 1.5.26 Debian 1.5.26-4 (1.1220.2.493 2008/02/01 16:58:18)
flex --version
flex 2.5.35
Hi Stefan,
I remember I got some compilation issues with flex 2.5.34; switching back to 2.5.33 solved them. Hope this helps you!
Marco
/usr/bin/lex -> flex
/usr/bin/yacc -> /etc/alternatives/yacc /etc/alternatives/yacc -> /usr/bin/byacc
yacc -V
yacc - 1.9 20070509
bison: not installed
/usr/bin/gcc -> gcc-4.3
gcc -v
Using built-in specs. Target: i486-linux-gnu Configured with: ../src/configure -v --with-pkgversion='Debian 4.3.1-2' --with-bugurl=file:///usr/share/doc/gcc-4.3/README.Bugs --enable-languages=c,c++,fortran,objc,obj-c++ --prefix=/usr --enable-shared --with-system-zlib --libexecdir=/usr/lib --without-included-gettext --enable-threads=posix --enable-nls --with-gxx-include-dir=/usr/include/c++/4.3 --program-suffix=-4.3 --enable-clocale=gnu --enable-libstdcxx-debug --enable-objc-gc --enable-mpfr --enable-targets=all --enable-cld --enable-checking=release --build=i486-linux-gnu --host=i486-linux-gnu --target=i486-linux-gnu Thread model: posix gcc version 4.3.1 (Debian 4.3.1-2)
Would you mind sharing with us, what line, say, 110 - 123 of your /home/sk/opt/MonetDB/include/MonetDB/gdk/gdk_system.h look like?
Here are lines 107-132, you may download the whole file here [1].
typedef size_t MT_Id; /* thread number. will not be zero */
gdk_export int MT_create_thread(MT_Id *t, void (*function) (void *), void *arg); gdk_export void MT_exit_thread(int status); gdk_export void MT_global_exit(int status); gdk_export MT_Id MT_getpid(void); gdk_export int MT_join_thread(MT_Id t); gdk_export int MT_kill_thread(MT_Id t);
#ifdef HAVE_PTHREAD_SIGMASK gdk_export void MT_thread_sigmask(sigset_t * new_mask, sigset_t * orig_mask);
The error /home/sk/opt/MonetDB/include/MonetDB/gdk/gdk_system.h:117: error: expected ‘)’ before ‘*’ token
seems to suggest that for some reason type sigset_t does not seems to be defined by default (in /usr/include/signal.h) on your "Debian GNU/Linux lenny/sid, latest upgrade was Jul 20 2008 12:22:11 +0200". On our "Debian 4.0", we don't have any such problems.
Admittedly, we do not explicitly test whether type sigset_t is defined by default, but just assume it is available in case function pthread_sigmask is available (see also `man pthread_sigmask`).
Hence, I honestly have no solution for your compilation problem, yet(?) ...
Stefan
#endif
gdk_export MT_Id MT_locktrace;
#if SIZEOF_VOID_P == 4 /* "limited" stack size on 32-bit systems */ /* to avoid address space fragmentation */ #define THREAD_STACK_SIZE ((size_t)2*512*1024) #else /* "increased" stack size on 64-bit systems */ /* since some compilers seem to require this */ /* for burg-generated code in pathfinder */ /* and address space fragmentation is no issue */ #define THREAD_STACK_SIZE ((size_t)4*512*1024) #endif
Thank you very much!!! Stefan
[1] File 'gdk_system.h', link valid for seven days. https://depot.uni-konstanz.de/get/7clrlt
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/ _______________________________________________ MonetDB-users mailing list MonetDB-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/monetdb-users
Hello!
Due to a biking accident I have to rest my right hand. Nothin dramatical happened, but I won't do too much typing during the next few days. This message is written left-handed.
So please don't expect me to be responsive this week. I'm going through your suggestions ASAP!
Thank you very much! Stefan
participants (4)
-
Fabian Groffen -
Marco Antonelli -
Stefan Klinger -
Stefan Manegold