WelcomeWelcome | FAQFAQ | DownloadsDownloads | WikiWiki
« previous next »
Pages: [1]   Go Down

Author Topic: floating point exception  (Read 3949 times)

Offline jpeters

  • Restricted
  • Hero Member
  • *****
  • Posts: 1017
floating point exception
« on: February 05, 2009, 05:51:54 PM »
This message seems to be the end of the line after attempting to satisfy dependencies. I've seen it several times now. Does this mean the libraries don't work correctly with the core, or is there something that can be corrected?  Thanks 
Logged

Offline ^thehatsrule^

  • Retired Admins
  • Hero Member
  • *****
  • Posts: 1726
Re: floating point exception
« Reply #1 on: February 05, 2009, 08:51:21 PM »
What kind of system (cpu, platform) are you using?  When and where do you see this?  Which extension?
Logged

Offline jpeters

  • Restricted
  • Hero Member
  • *****
  • Posts: 1017
Re: floating point exception
« Reply #2 on: February 05, 2009, 10:00:17 PM »
Quote from: ^thehatsrule^ on February 05, 2009, 08:51:21 PM
What kind of system (cpu, platform) are you using?  When and where do you see this?  Which extension?

I'm using a Dell C610 laptop with a Pentium 111 -M 1000MHZ.  Most recently, I was trying to
build the latest 2.0.0.72 version of Skype on tc, and got this message after loading the gt4, libX, and other libs that it called for. 

Edit:  I got it going and loading....
« Last Edit: February 06, 2009, 04:31:13 AM by jpeters »
Logged

Offline curaga

  • Administrator
  • Hero Member
  • *****
  • Posts: 11044
Re: floating point exception
« Reply #3 on: February 06, 2009, 05:18:23 AM »
It's a bug in Skype code or the libs (guess which is more likely :p)
Logged
The only barriers that can stop you are the ones you create yourself.

Offline jpeters

  • Restricted
  • Hero Member
  • *****
  • Posts: 1017
Re: floating point exception
« Reply #4 on: February 07, 2009, 10:48:29 AM »
Quote from: curaga on February 06, 2009, 05:18:23 AM
It's a bug in Skype code or the libs (guess which is more likely :p)

I  think it may have been a permission issue. I was using  LD_LIBRARY _PATH to point to libs while testing, which seemed to work except that it didn't  :)
« Last Edit: February 07, 2009, 10:51:21 AM by jpeters »
Logged
Pages: [1]   Go Up
« previous next »