Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 4434 - new version is out and seems needed to compile octave-forge
Summary: new version is out and seems needed to compile octave-forge
Status: RESOLVED FIXED
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: [OLD] Development (show other bugs)
Hardware: All Linux
: Normal enhancement (vote)
Assignee: George Shapovalov (RETIRED)
URL: http://www.octave.org
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2002-07-02 12:06 UTC by Luca Barbato
Modified: 2002-12-13 21:19 UTC (History)
1 user (show)

See Also:
Package list:
Runtime testing required: ---


Attachments
octave-2.1.40.ebuild (octave-2.1.40.ebuild,1.90 KB, application/octet-stream)
2002-12-12 15:44 UTC, George Shapovalov (RETIRED)
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Luca Barbato gentoo-dev 2002-07-02 12:06:56 UTC
As stated on the summary

octave.sf.net for the octave-forge
Comment 1 Matt Matthews 2002-08-07 13:45:14 UTC
I don't know if this is the right bug to attach to, but I can't get the Octave
2.1.36 that's in Portage to run. Here's a simple test:
-----
octave:1> sin( 1:2 )
panic: Segmentation fault -- stopping myself...
attempting to save variables to `octave-core'...
panic: attempted to clean up apparently failed -- aborting...
Abort
-----
Nice, eh?

I was worried that I had a broken lib somewhere, so I tried
emerge --emptytree octave
and recompiled *everything* in that list. Still gets the error. I'm using gcc
3.1.1 now, but I had the same problem with gcc 3.1 that was in Portage before.

Help. :^)
Comment 2 George Shapovalov (RETIRED) gentoo-dev 2002-12-11 23:26:46 UTC
Hi Matt.

Sorry for long silence - this is what you get for putting an actual bug report
under a feature request ;). Really, I looked at this bug as soon as it was
assigned to me but did not respond right away (I apologize about that) and then
got here again only now, going through my looong list of bugs. (Hint: if you
canot find the topic in active bugs, then just create a new one ;)).

Anyway, I think I will need some more information from you, as I cannot
reproduce the problem. In fact while looking at this package I encountered some
sandbox violations, which were fixed in the -r1. This may not be directly
related, but could you please test if you still have this problem with
octave-2.1.36-r1.ebuild?
If you will still be experiencing the problem, please report:
1. your profile (like default-x86-1.4)
2. presently installed versions of glibc/gcc
3. did you do any nonstandard stuff?
4. output of "emerge -pe octave"

I suspect the problem you were experiencing might be related to gcc-3.1*, in
which case it should hopefully go away with gcc-3.2. gcc people has changed
quite a bit of stuff again in there..

Thanks!

George
Comment 3 Matt Matthews 2002-12-11 23:41:55 UTC
There hasn't been an issue for a long time now. Sorry I didn't report back
sooner. I think that this was a GCC 3.1.1 issue and now with GCC 3.2.x it's just
fine. Thanks for checking in on it...seems fine for me.

Now, could we get an Octave 2.1.40 ebuild? ;^)
Comment 4 George Shapovalov (RETIRED) gentoo-dev 2002-12-12 15:44:43 UTC
Created attachment 6444 [details]
octave-2.1.40.ebuild

Hi Matt.

Here you go (kind of).
I just did a quick copy/rename dropping all patches. It compiles fine, but now
I am getting a Segfault :( (possibly due to using all ~x86'd system packages
like glibc and gcc).
Could you please ceck how it works for you?octave-2.1.40.ebuild

George
Comment 5 Matt Matthews 2002-12-12 23:29:55 UTC
What did you do to get a segfault? Your ebuild got me a working Octave, AFAICT,
and no segfaults just trying the basics. I guess I didn't look to see what
patches had been included in the older build...

Anyway, "Works For Me".
Comment 6 George Shapovalov (RETIRED) gentoo-dev 2002-12-13 21:19:44 UTC
Hi Matt.

Thanks for testing.
Well, on me it was segfaulting right after I am trying to run it. Though I am
lately experiencing some semi-random crashed on my main system, I guess time to
clean-up and rebuild ;).
Anyway, I decided to commit this version. It'll stay masked until I collect
sufficient amount of test reports. 
Closing the bug now.

George