Bug List: (This bug is not in your last search results)   Show last search results      Search page      Enter new bug
Bug#: 20263
Alias:
Product:
Component:
Status: RESOLVED
Resolution: FIXED
Assigned To: Martin Holzer (RETIRED) <mholzer@gentoo.org>
Hardware:
OS:
Version:
Priority:
Severity:
Reporter: Daniel Tourde <daniel.tourde@bredband.net>
Add CC:
CC:
URL:
Summary:
Status Whiteboard:
Keywords:

Filename Description Type Creator Created Size Actions
Create a New Attachment (proposed patch, testcase, etc.) View All

Bug 20263 depends on: Show dependency tree
Bug 20263 blocks:
Votes: 0    Show votes for this bug    Vote for this bug

Additional Comments: (this is where you put emerge --info)


Not eligible to see or edit group visibility for this bug.






View Bug Activity   |   Format For Printing   |   XML   |   Clone This Bug


Description:   Opened: 2003-05-01 05:49 0000
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"

------- Comment #1 From Martin Holzer (RETIRED) 2003-05-01 06:58:16 0000 -------
fixed in cvs

------- Comment #2 From Daniel Tourde 2003-05-01 09:51:24 0000 -------
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 

------- Comment #3 From Priit Laes (IRC: plaes) 2003-05-01 11:34:27 0000 -------
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...

Bug List: (This bug is not in your last search results)   Show last search results      Search page      Enter new bug