RE: Building from source

> sources from
> sapdb.org ("Quick Download"), the development environment didn't build
> because of missing PATH settings, ptoc etc. Well, this is 
> documented in
> the mailing list archives (to use CVS sources), but could be improved
> anyhow.

We now have found someone with enough time to test the source packages regularly, so I hope this situation improves.

> because of errors in dependencies made of 'sqlpy.mac', 
> command 'PYTHONPATH=$INSTMISC python -c "import sapdb.sql"...' not

The important error comes before this one. It looks as if the python extension could not be built.

You get a protocol of all the errors in $WRK/fast/prot/all.mac.e0

> Inbetween, there are some compile errors like the following, but the
> build process doesn't stop, so one waits for hours (on a P4 2.8GHz) to
> get the notice that there were some problems at the 
> beginning. I propose
> a regular make behaviour aborting on errors.

I've asked the vmake developer if he could add such an option and at least, he didn't say that it's impossible. For our work, we prefer it of course the way it is. We either edit a small number of files, then the difference between 'make' and 'make -k' is negligible. Or we make big changes, in which case we want to compile as much as possible while we're doing something else.

And in the case of supporting external developers, I also prefer to get all the errors at once instead of one per day.

You could open a second xterm and do a tail -f on the file mentioned above if you want to see at a glance if there were any errors.

> vls14_scan.cpp:68: syntax error before `[' token

vls14_scan.cpp gets generated by flex from sys/src/ls/vls14_scan.l. Please look into $WRK/fast/tmp/ for this file and post this line and possible a few around it.

Daniel Dittmar

-- 
Daniel Dittmar
SAP DB, SAP Labs Berlin
[email protected]
http://www.sapdb.org/