sac2c issueshttps://gitlab.sac-home.org/sac-group/sac2c/-/issues2018-09-29T11:06:49Zhttps://gitlab.sac-home.org/sac-group/sac2c/-/issues/2232GTESTs CMake configuration error2018-09-29T11:06:49ZHans-Nikolai ViessmannGTESTs CMake configuration errorWhen running CMake with `-DFUNCTESTS=OFF`, we get the following error message:
```
$ cmake -DFUNCTESTS=OFF ..
... omitted content ...
CMake Error at tests/CMakeLists.txt:11 (ADD_TEST):
ADD_TEST given test NAME "test-test-condfun-nos...When running CMake with `-DFUNCTESTS=OFF`, we get the following error message:
```
$ cmake -DFUNCTESTS=OFF ..
... omitted content ...
CMake Error at tests/CMakeLists.txt:11 (ADD_TEST):
ADD_TEST given test NAME "test-test-condfun-nostdlib" which already exists
in this directory.
Call Stack (most recent call first):
tests/CMakeLists.txt:49 (REGISTER_TEST)
```
Does MR !67 fix this issue at all?Artem ShinkarovArtem Shinkarovhttps://gitlab.sac-home.org/sac-group/sac2c/-/issues/2231sac2c -h does not list acceptable targets, e.g, mt_pth, etc.2021-05-25T17:25:36ZRobert Berneckysac2c -h does not list acceptable targets, e.g, mt_pth, etc.This makes it difficult to find out what targets are acceptable, without
spelunking...
This as of:
sac2c -V
sac2c 1.3.2-MijasCosta-36-g34023
build-type: RELEASE
built-by: "sac" at 2018-09-07T13:43:08This makes it difficult to find out what targets are acceptable, without
spelunking...
This as of:
sac2c -V
sac2c 1.3.2-MijasCosta-36-g34023
build-type: RELEASE
built-by: "sac" at 2018-09-07T13:43:08https://gitlab.sac-home.org/sac-group/sac2c/-/issues/2230Move gitlab to using internal plugin fascility to launch pipelines2020-12-07T11:38:28ZHans-Nikolai ViessmannMove gitlab to using internal plugin fascility to launch pipelinesGitLab supports plugins now (https://docs.gitlab.com/ee/administration/plugins.html) which mean we can automate a lot of stuff regarding merge requests and pipelines. We currently use an external tool (via HTTPS) that does this, and work...GitLab supports plugins now (https://docs.gitlab.com/ee/administration/plugins.html) which mean we can automate a lot of stuff regarding merge requests and pipelines. We currently use an external tool (via HTTPS) that does this, and works, but its a separate piece of infrastructure we could do without. An example is provided here: https://gitlab.com/gitlab-org/gitlab-ce/issues/23902#note_88958643.Hans-Nikolai ViessmannHans-Nikolai Viessmannhttps://gitlab.sac-home.org/sac-group/sac2c/-/issues/2229Compiler assertion while compiling relaxation.sac from the tutorial files2021-09-01T11:19:47ZGrzegorz GoralCompiler assertion while compiling relaxation.sac from the tutorial filesI was going through the tutorial using the PDF for reading, and the GitHub files for compiling.
The relaxation.sac file from the SacBase/Tutorial L2 folder:
```
use Array: all;
use Math: all;
use StdIO: all;
int main()
{
weights = [ [...I was going through the tutorial using the PDF for reading, and the GitHub files for compiling.
The relaxation.sac file from the SacBase/Tutorial L2 folder:
```
use Array: all;
use Math: all;
use StdIO: all;
int main()
{
weights = [ [0d, 1d, 0d], [1d, 4d, 1d], [ 0d, 1d, 0d]];
vect = [1d, 2d, 3d, 4d];
mat = [ vect, vect+4d, vect+8d, vect+12d];
print( mat);
mat = { [i,j] -> sum( { iv -> weights[iv] * rotate( 1-iv, mat)}[[...,i,j]] ) }
/ sum( weights);
print( mat);
return(0);
}
```
This is the command used and error received from compiling the file.
```
$ sac2c relaxation.sac
Internal compiler error
Assertion "cviv[i] < cvshp[i]" failed at /home/build/sac2c/src/libsac2c/constants/constants_struc_ops.c:1266 -- Index error: iv[1] >= shp[1]
Please file a bug at: http://bugs.sac-home.org
```
My version of sac2c:
```
sac2c -V
sac2c 1.3.2-MijasCosta-18-gce04c
build-type: RELEASE
built-by: "build" at 2018-07-10T14:38:07
```https://gitlab.sac-home.org/sac-group/sac2c/-/issues/2228manual missing from the website2018-07-05T14:16:33ZGhost Usermanual missing from the websiteThe docs page says that there's a manual (and links to http://www.sac-home.org/doku.php?id=docs:main - http://www.sac-home.org/lib/exe/fetch.php?media=docs:manual.pdf for the PDF), but the links seem to be broken.The docs page says that there's a manual (and links to http://www.sac-home.org/doku.php?id=docs:main - http://www.sac-home.org/lib/exe/fetch.php?media=docs:manual.pdf for the PDF), but the links seem to be broken.Sven-Bodo ScholzSven-Bodo Scholzhttps://gitlab.sac-home.org/sac-group/sac2c/-/issues/2227type error treatment leads to compiler warning2018-06-12T11:16:26ZSven-Bodo Scholztype error treatment leads to compiler warning```sac
noinline
int id( int x)
{ return x; }
int main ()
{
kx = (_eq_SxS_(id(0), 0) ? _div_SxS_(1,0) : 42);
return( kx);
}
```
when compiled with sac2c 1.2-beta-BlackForest-681-gfb545 (level version of Mijas 1.3.2 :-)
on OSX lea...```sac
noinline
int id( int x)
{ return x; }
int main ()
{
kx = (_eq_SxS_(id(0), 0) ? _div_SxS_(1,0) : 42);
return( kx);
}
```
when compiled with sac2c 1.2-beta-BlackForest-681-gfb545 (level version of Mijas 1.3.2 :-)
on OSX leads to:
>>>
/Volumes/Users/sbs/sacbase/LivermoreLoops/loop08/a.out.c:1493:114: warning: variable 'SACp_hce_0' is used uninitialized whenever 'if' condition is true [-Wsometimes-uninitialized]
if (SAC_ND_GETVAR((SACp_emal_4688__flat_1, (SCL, (NHD, (NUQ, (INT, (GLO, (NON, (NOT, (NDI, (BOO, )))))))))), SACp_emal_4688__flat_1))
^~~~~~~~~~~~~~~~~~~~~~
/Volumes/Users/sbs/sac2c/build_p/include/runtime/essentials_h/std.h:298:33: note: expanded from macro 'SAC_ND_GETVAR'
#define SAC_ND_GETVAR(nt, name) name
^~~~
/Volumes/Users/sbs/sacbase/LivermoreLoops/loop08/a.out.c:1514:100: note: uninitialized use occurs here
SAC_ND_RET_out( (SAC_arg_1, (SCL, (NHD, (NUQ, (INT, (GLO, (FPM, (NOT, (NDI, (INT, )))))))))), (SACp_hce_0, (SCL, (NHD, (NUQ, (INT, (GLO, (NON, (NOT, (NDI, (INT, )))))))))))
^~~~~~~~~~
/Volumes/Users/sbs/sac2c/build_p/include/runtime/essentials_h/std_gen.h:1661:152: note: expanded from macro 'SAC_ND_RET_out'
#define SAC_ND_RET_out( arg1, nt ) CAT_M4_std_gen_67(SAC_ND_RET_out_, CAT_M4_std_gen_68(NT_SHP(nt), CAT_M4_std_gen_69(NT_HID(nt), NT_UNQ(nt))))( arg1, nt )
^~
/Volumes/Users/sbs/sac2c/build_p/include/runtime/essentials_h/std_gen.h:1662:62: note: expanded from macro 'SAC_ND_RET_out_SCLNHDNUQ'
#define SAC_ND_RET_out_SCLNHDNUQ(...) SAC_ND_RET_out__NODESC(__VA_ARGS__)
^~~~~~~~~~~
/Volumes/Users/sbs/sac2c/build_p/include/runtime/essentials_h/std.h:1339:52: note: expanded from macro 'SAC_ND_RET_out__NODESC'
= SAC_ND_GETVAR (var_NT, SAC_ND_A_FIELD (var_NT)); \
^~~~~~
note: (skipping 3 expansions in backtrace; use -fmacro-backtrace-limit=0 to see all)
/Volumes/Users/sbs/sac2c/build_p/include/runtime/essentials_h/std.h:87:31: note: expanded from macro 'NT_NAME'
#define NT_NAME(var_NT) Item0 var_NT
^~~~~~
/Volumes/Users/sbs/sac2c/build_p/include/runtime/essentials_h/icm.h:68:21: note: expanded from macro 'Item0'
#define Item0(a, b) a
^
/Volumes/Users/sbs/sac2c/build_p/include/runtime/essentials_h/std.h:298:33: note: expanded from macro 'SAC_ND_GETVAR'
#define SAC_ND_GETVAR(nt, name) name
^~~~
/Volumes/Users/sbs/sacbase/LivermoreLoops/loop08/a.out.c:1493:5: note: remove the 'if' if its condition is always false
if (SAC_ND_GETVAR((SACp_emal_4688__flat_1, (SCL, (NHD, (NUQ, (INT, (GLO, (NON, (NOT, (NDI, (BOO, )))))))))), SACp_emal_4688__flat_1))
^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
/Volumes/Users/sbs/sacbase/LivermoreLoops/loop08/a.out.c:1466:103: note: variable 'SACp_hce_0' is declared here
SAC_ND_DECL__DATA( (SACp_hce_0, (SCL, (NHD, (NUQ, (INT, (GLO, (NON, (NOT, (NDI, (INT, )))))))))), int, )
^
1 warning generated.
>>>
However, the code delivers the correct result :-)
ie a type error!
https://gitlab.sac-home.org/sac-group/sac2c/-/issues/2226version naming problem2018-05-25T22:34:44ZSven-Bodo Scholzversion naming problemonce upon a time.... we had only one master branch.... the naming was automated, looked for the latest tag, computed the distance, and assembled something like this: v1.2-beta-BlackForest-681-gfb545b33f
NOW, we have a master and a devel...once upon a time.... we had only one master branch.... the naming was automated, looked for the latest tag, computed the distance, and assembled something like this: v1.2-beta-BlackForest-681-gfb545b33f
NOW, we have a master and a developer branch..... tags are no longer done in the developer branch.... but in the master branch. Consequently, I obtain v1.2-beta-BlackForest-681-gfb545b33f despite the developer branch being base on v1.3.2-beta-Mijas....
I understand that having the same tag in two different branches does not make sense and, most likely, is not even possible.
So here my suggestion: should we use v.1.3.2-Mijas.... for the master and v.1.3.2-beta-Mijas... for the corresponding versions in the two different branches?Hans-Nikolai ViessmannHans-Nikolai Viessmannhttps://gitlab.sac-home.org/sac-group/sac2c/-/issues/2225extend masterrun to build sac2c with/without various features2019-09-26T13:18:39ZHans-Nikolai Viessmannextend masterrun to build sac2c with/without various featuresThis issue was spawned from the MR !43 which made it evident that we need to extend the masterrun to build `sac2c` with or without various combinations of features. This should hopefully more quickly reveal problems like the one solved b...This issue was spawned from the MR !43 which made it evident that we need to extend the masterrun to build `sac2c` with or without various combinations of features. This should hopefully more quickly reveal problems like the one solved by the MR.
It is unclear though what the best way of doing this is; either we extend `.gitlab-ci.yml` to build sac2c with different feature flags, or we run a few more docker images with various installs. Are there other possibilities?https://gitlab.sac-home.org/sac-group/sac2c/-/issues/2224Slight name confusion on sac2c binaries2018-04-30T22:17:12ZRobert BerneckySlight name confusion on sac2c binariesThe DEBUG version of sac2c is called sac2c_d. This is good.
The RELEASE version of sac2c is called sac2c_p. This is bad. Presumably, it
meant PRODUCTION in the bad old days...
If we rename the RELEASE version to be sac2c_r, the name wil...The DEBUG version of sac2c is called sac2c_d. This is good.
The RELEASE version of sac2c is called sac2c_p. This is bad. Presumably, it
meant PRODUCTION in the bad old days...
If we rename the RELEASE version to be sac2c_r, the name will make more sense.https://gitlab.sac-home.org/sac-group/sac2c/-/issues/2223Compiler assertion on incorrect number of arguments to primitive function2018-04-13T23:50:28ZArtem ShinkarovCompiler assertion on incorrect number of arguments to primitive functionHere is a test file:
```sh
$ cat test.sac
int main ()
{
return _add_SxS_ (1);
}
```
Here is what I get when calling sac2c:
```sh
/tmp|=> sac2c test.sac
Internal compiler error
Assertion "TYgetProductSize( args) == 2" failed at /tmp/s...Here is a test file:
```sh
$ cat test.sac
int main ()
{
return _add_SxS_ (1);
}
```
Here is what I get when calling sac2c:
```sh
/tmp|=> sac2c test.sac
Internal compiler error
Assertion "TYgetProductSize( args) == 2" failed at /tmp/sac2c/src/libsac2c/typecheck/ct_prf.c:2476 -- ari_op_SxV called with incorrect number of arguments
Please file a bug at: http://bugs.sac-home.org
```
This should be an error, not a compiler assertion.
https://gitlab.sac-home.org/sac-group/sac2c/-/issues/2222Stdlib build fails, due to dependency error or else confusion on where libsac...2018-01-10T18:44:18ZRobert BerneckyStdlib build fails, due to dependency error or else confusion on where libsac lives```
cd Stdlib/build
cmake ..
make -j
```
This dies with:
```
/home/sac/sac/BASE/Stdlib/src/system/src/RTClock/rtclock.c:11:39: fatal error: libsac/essentials/message.h: No such file or directory
```
Rerunning the make does not help.
``...```
cd Stdlib/build
cmake ..
make -j
```
This dies with:
```
/home/sac/sac/BASE/Stdlib/src/system/src/RTClock/rtclock.c:11:39: fatal error: libsac/essentials/message.h: No such file or directory
```
Rerunning the make does not help.
```
ac@rattler:~/sac/BASE/Stdlib/build$ sac2c -V
sac2c 1.2-beta-BlackForest-611-g777dc
build-type: RELEASE
built-by: "sac" at 2018-01-01T15:26:55
```
I have just rebuilt sac2c_d and sac2c_r, and installed sac2c_r.
Stdlib also cloned a few minutes ago.https://gitlab.sac-home.org/sac-group/sac2c/-/issues/2221[gitlab CI] Build stdlib using sac2c package2019-02-08T14:57:18ZArtem Shinkarov[gitlab CI] Build stdlib using sac2c packageCurrently, as a part of CI pipeline, we always build stdlib using sac2c binaries directly from the working build directory.
The problem with this is that we never test whether resulting package is operational or not.
It would be a better...Currently, as a part of CI pipeline, we always build stdlib using sac2c binaries directly from the working build directory.
The problem with this is that we never test whether resulting package is operational or not.
It would be a better idea to extend the pipeline as follows:
1. Compile sac2c
2. Create sac2c package
3. Install sac2c package & build stdlib
This would allow to identify the cases when packages are not fully operational.Hans-Nikolai ViessmannHans-Nikolai Viessmannhttps://gitlab.sac-home.org/sac-group/sac2c/-/issues/2220Need more distinct package file names2017-12-13T15:07:23ZHans-Nikolai ViessmannNeed more distinct package file namesAfter merge requests like !35, it has become clear that the package generation can cause unintended overwrites of existing package blobs on the release server. A possible solution would be to append a timestamp to the name, or create a n...After merge requests like !35, it has become clear that the package generation can cause unintended overwrites of existing package blobs on the release server. A possible solution would be to append a timestamp to the name, or create a new directory with the timestamp as its name.https://gitlab.sac-home.org/sac-group/sac2c/-/issues/2219Scheduled weekly packages should have different name to distinguish them.2019-02-08T14:57:32ZHans-Nikolai ViessmannScheduled weekly packages should have different name to distinguish them.Currently we jut use the default name given by CPack. We can override this with the `CPACK_PACKAGE_FILE_NAME` variable, making the weekly packages distinguishable from normal releasee packages.Currently we jut use the default name given by CPack. We can override this with the `CPACK_PACKAGE_FILE_NAME` variable, making the weekly packages distinguishable from normal releasee packages.Hans-Nikolai ViessmannHans-Nikolai Viessmannhttps://gitlab.sac-home.org/sac-group/sac2c/-/issues/2218Gitlab-CI running CTest in parallel2017-12-06T13:50:09ZHans-Nikolai ViessmannGitlab-CI running CTest in parallelThe following discussion from !28 should be addressed:
- [ ] @tema started a [discussion](https://www.macs.hw.ac.uk/gitlab/sac-group/sac2c/merge_requests/28#note_7878): (+2 comments)
> You **really** want to run tests in parallel....The following discussion from !28 should be addressed:
- [ ] @tema started a [discussion](https://www.macs.hw.ac.uk/gitlab/sac-group/sac2c/merge_requests/28#note_7878): (+2 comments)
> You **really** want to run tests in parallel. If you use normal CMakeLists.txt, then you can run
> `ctest -j5` or `make test ARGS=-j5`. Whether you can nicely pass these arguments to cpack/CMakeLists.txt, you'll have to find out.https://gitlab.sac-home.org/sac-group/sac2c/-/issues/2217When use/import does not specify module name, parser fails to produce an erro...2017-11-24T23:04:37ZArtem ShinkarovWhen use/import does not specify module name, parser fails to produce an error messageConsider the following sac program:
```
use /* missing */ : {test};
```
As it can be seen, we accidentally missed the name of the module we are using.
The compiler dies, which is correct; but no error message is emitted:
```sh
$ sac2c_p...Consider the following sac program:
```
use /* missing */ : {test};
```
As it can be seen, we accidentally missed the name of the module we are using.
The compiler dies, which is correct; but no error message is emitted:
```sh
$ sac2c_p y.sac
abort: Failed to construct a syntax tree for `y.sac'
compilation failed while Loading SAC program.
```
The sac2c version is:
```
sac2c 1.2-beta-BlackForest-611-g777dc
build-type: RELEASE
built-by: "tema" at 2017-11-23T15:59:10
```https://gitlab.sac-home.org/sac-group/sac2c/-/issues/2216ArrayIO::show(vector) fills universe, doesn't display2018-05-04T17:02:14ZRobert BerneckyArrayIO::show(vector) fills universe, doesn't display| | |
| --- | --- |
| Bugzilla Link | [1201](http://bugs.sac-home.org/show_bug.cgi?id=1201) |
| Created on | Aug 08, 2017 20:11 |
| Version | svn |
| OS | Linux |
| Architecture | PC |
| Attachments | [bugshow.sac](/uploads/016ec1dab52...| | |
| --- | --- |
| Bugzilla Link | [1201](http://bugs.sac-home.org/show_bug.cgi?id=1201) |
| Created on | Aug 08, 2017 20:11 |
| Version | svn |
| OS | Linux |
| Architecture | PC |
| Attachments | [bugshow.sac](/uploads/016ec1dab5247dbabbd00705e8018bd8/bugshow.sac) |
## Extended Description
Created an attachment (id=1066)
source code to reproduce failure
The show() function no longer works.
A little research suggests that its subfunction, format([2.3])
is broken.
I do not have time to fix this now, but it is on my list.Robert BerneckyRobert Berneckyhttps://gitlab.sac-home.org/sac-group/sac2c/-/issues/2215POGO fails to optimize guard on select from shape() expression.2017-11-23T23:25:32ZRobert BerneckyPOGO fails to optimize guard on select from shape() expression.| | |
| --- | --- |
| Bugzilla Link | [1200](http://bugs.sac-home.org/show_bug.cgi?id=1200) |
| Created on | Aug 03, 2017 17:24 |
| Resolution | FIXED |
| Resolved on | Aug 07, 2017 23:16 |
| Version | svn |
| OS | Linux |
| Architectu...| | |
| --- | --- |
| Bugzilla Link | [1200](http://bugs.sac-home.org/show_bug.cgi?id=1200) |
| Created on | Aug 03, 2017 17:24 |
| Resolution | FIXED |
| Resolved on | Aug 07, 2017 23:16 |
| Version | svn |
| OS | Linux |
| Architecture | PC |
| Attachments | [SCSprf_val_le_val_VxV.sac](/uploads/9f7a24808639831a851d6f4b42e6ef79/SCSprf_val_le_val_VxV.sac) |
## Extended Description
<pre>Created an attachment (id=1065)
source code to reproduce failure
This unit test fails:
~/sac/testsuite/optimizations/pogo$ vi SCSprf_val_le_val_VxV.sac
sac@rattler:~/sac/testsuite/optimizations/pogo$ UnitTestRunGrep1 SCSprf_val_le_val_VxV.sac
...
Greptest: SCSprf_val_le_val_VxV.sac -check c -dopogo -noggs -dolacsi -dowlf -nopwlf -noawlf -noctz -norelcf -noainl -doplur failed with 3 hits on phrase "val_l". Wanted 2 hits
sac@rattler:~/sac/testsuite/optimizations/pogo$ vi grepd
sac@rattler:~/sac/testsuite/optimizations/pogo$ ^C
sac@rattler:~/sac/testsuite/optimizations/pogo$ sac2c -V
sac2c 1.2-beta-BlackForest-569-ge881c2
build-type: DEBUG
built-by: "sac" at 2017-07-21T17:03:33
The offending code is:
_flat_3 = 0;
v1 = _MAIN::id( _flat_2, _flat_7) ;
_isaa_3058_v1 = _shape_A_( v1);
_isaa_3059_v1 = _saabind_( _flat_4, _isaa_3058_v1, v1);
_uprf_2654 = _idx_sel_( _flat_3, _isaa_3058_v1);
_uprf_2643, _uprf_2644 = _val_le_val_SxS_( _flat_3, _uprf_2654);
The fault is likely in PHUT, which should be able to deduce that
_uprf_2654 is an element of a shape vector, and hence is non-negative.</pre>Robert BerneckyRobert Berneckyhttps://gitlab.sac-home.org/sac-group/sac2c/-/issues/2214Can't build release version of sac2c on Linux2017-11-23T23:25:26ZRobert BerneckyCan't build release version of sac2c on Linux| | |
| --- | --- |
| Bugzilla Link | [1199](http://bugs.sac-home.org/show_bug.cgi?id=1199) |
| Created on | Jul 17, 2017 22:00 |
| Resolution | FIXED |
| Resolved on | Jul 18, 2017 22:16 |
| Version | svn |
| OS | Linux |
| Architectu...| | |
| --- | --- |
| Bugzilla Link | [1199](http://bugs.sac-home.org/show_bug.cgi?id=1199) |
| Created on | Jul 17, 2017 22:00 |
| Resolution | FIXED |
| Resolved on | Jul 18, 2017 22:16 |
| Version | svn |
| OS | Linux |
| Architecture | PC |
## Extended Description
<pre>Debug version builds okay. Release version is not happy:
sac2c -V
sac2c 1.2-beta-BlackForest-567-g6ae5f
build-type: DEBUG
built-by: "sac" at 2017-07-17T16:33:55
Here's the release version build:
[ 29%] Building C object src/libsacphmc-mt_pth/CMakeFiles/libsacphmc-mt_pth.dir/wrappers/nophm.c.o
Internal compiler error
Assertion "sacargudt != UT_NOT_DEFINED" failed at /home/sac/sac2c/src/libsac2c/generics/generate_generic_type_conversions.c:370 -- Cannot find sacarg udt!
Please file a bug at: http://bugs.sac-home.org
src/libsacprelude-seq/CMakeFiles/libsacprelude-seq.dir/build.make:62: recipe for target 'lib/prelude/host/seq/libsacprelude_pMod.so' failed
make[5]: *** [lib/prelude/host/seq/libsacprelude_pMod.so] Error 1
CMakeFiles/Makefile2:438: recipe for target 'src/libsacprelude-seq/CMakeFiles/libsacprelude-seq.dir/all' failed
make[4]: *** [src/libsacprelude-seq/CMakeFiles/libsacprelude-seq.dir/all</pre>BugZillaBugZillahttps://gitlab.sac-home.org/sac-group/sac2c/-/issues/2213stdlib build fails even after make clean2021-05-27T12:39:32ZRobert Berneckystdlib build fails even after make clean| | |
| --- | --- |
| Bugzilla Link | [1181](http://bugs.sac-home.org/show_bug.cgi?id=1181) |
| Created on | Sep 05, 2016 21:01 |
| Version | svn |
| OS | Linux |
| Architecture | PC |
## Extended Description
<pre>This was preceeded ...| | |
| --- | --- |
| Bugzilla Link | [1181](http://bugs.sac-home.org/show_bug.cgi?id=1181) |
| Created on | Sep 05, 2016 21:01 |
| Version | svn |
| OS | Linux |
| Architecture | PC |
## Extended Description
<pre>This was preceeded by a "make clean" and "./configure":
make[2]: Entering directory '/home/sac/sac/BASE/stdlib'
** Note: modules Dislin DislinBars DislinQuick DislinCanvas DislinPage DislinPlot3d DislinSystem IplImage CvCapture RGB disabled due to configuration.
SAC2C targets/seq/ArrayBasics.done
abort: The module 'ScalarArith'
abort: (/usr/local/libexec/sac2c/1.2.beta-BlackForest-294-7460/tree/host/libScalarArithTree.so) uses an incompatible syntax tree layout. Please update the module and compiler to the most recent version.
compilation failed while Loading SAC program.
targets/seq/GNUmakefile:188: recipe for target 'targets/seq/ArrayBasics.done' failed
make[2]: *** [targets/seq/ArrayBasics.done] Error 1
make[2]: Leaving directory '/home/sac/sac/BASE/stdlib'
GNUmakefile:988: recipe for target 'subtarget-seq-activate-recursive' failed
make[1]: *** [subtarget-seq-activate-recursive] Error 2
make[1]: Leaving directory '/home/sac/sac/BASE/stdlib'
GNUmakefile:841: recipe for target 'install' failed
make: *** [install] Error 2
sac@rattler:~/sac/BASE/stdlib$
sac@rattler:~/sac/BASE/stdlib$ ./configure; make -j8; sudo make install
The problem goes away when I do:
sudo rm -r /usr/local/libexec/sac2c.*
and redo the whole stdlib build.</pre>Sven-Bodo ScholzSven-Bodo Scholz