On April 30th 2003 I tried to build scilab 2.6 on a fresh and updated Gentoo 1.4 box. Everything seemed to go fine. However when I tried to run scilab nothing happened. I check on /usr/bin/scilab and discovered that this was a link to nothing. The directory /usr/lib/scilab-2.6 supposedling containing the real scilab binary being not there. gcc 3.2.2 based system. glibc 2.3.1. Gentoo Linux kernel 2.4.20. CFLAGS="-O3 -march=pentium2 -pipe" I tried again to rebuild scilab and saw then that some fortran code generated warnings. I don't know if it has had any impact on the missing directory though. Reproducible: Always Steps to Reproduce: 1. emerge scilab 2. try to run scilab with the command 'scilab' 3. check the existence of /usr/lib/scilab-2.6 Actual Results: 'scilab' did nothing. /usr/bin/scilab being a link to the real scilab binary in the missing /usr/lib/scilab-2.6 directory. There is nothing surprising there... Expected Results: A working scilab.... I choose the blocker severity option. I cannot use scilab, I think it corresponds well to the definition of "blocker"
fixed in cvs
So how do I do from emerge? Is there a special command I am supposed to use? Is there a scilab-2.7 that would solve the problem? Can't the patch(es) be applied to the stable tree (2.6)? Daniel
Fixed in cvs means that this ebuild was fixed in main cvs repository and it will take ~30 minutes when it's available @ rsync servers... so emerge sync and emerge scilab to rebuild it...
