The International Simutrans Forum

 

Author Topic: r5899 nightly fails to start  (Read 24058 times)

0 Members and 1 Guest are viewing this topic.

Offline wernieman

  • Devotees (Inactive)
  • *
  • Posts: 713
    • Werniemans-Webside (only German)
Re: r5899 nightly fails to start
« Reply #140 on: November 14, 2012, 09:11:31 PM »
Did somebody else can give me Information?

Or is the Bug solved (at the Moment)?

Offline Dwachs

  • DevTeam, Coder/patcher
  • Administrator
  • *
  • Posts: 4601
  • Languages: EN, DE, AT
Re: r5899 nightly fails to start
« Reply #141 on: November 21, 2012, 07:46:27 PM »
I am in the process of setting up mingw. If I run the grep command like Ters suggested, it is showing these fisttp instructions. These instructions are in sections named .gcc_except_table. (~ 12 hits)

Are these instructions executed at all ? Or is this just data lying in a table?

Offline wernieman

  • Devotees (Inactive)
  • *
  • Posts: 713
    • Werniemans-Webside (only German)
Re: r5899 nightly fails to start
« Reply #142 on: November 21, 2012, 08:13:05 PM »
My last Version i testet have no hits.

The Problem:
I compile on an Gentoo.System and there the mingw use the wrong make.conf

Offline prissi

  • Developer
  • Administrator
  • *
  • Posts: 9566
  • Languages: De,EN,JP
Re: r5899 nightly fails to start
« Reply #143 on: November 21, 2012, 08:31:26 PM »
50% offtopic: With the next upcoming processor of intel with 64 hyperthreading pentium cores, there might again arise the need for pure pentium settings at least for servers ...

Other than that, the may issue seems to be solved? (Unsure where to put this thread for now.)

Offline Ters

  • Coder/patcher
  • Devotee
  • *
  • Posts: 5543
  • Languages: EN, NO
Re: r5899 nightly fails to start
« Reply #144 on: November 21, 2012, 09:20:53 PM »
I am in the process of setting up mingw. If I run the grep command like Ters suggested, it is showing these fisttp instructions. These instructions are in sections named .gcc_except_table. (~ 12 hits)

Are these instructions executed at all ? Or is this just data lying in a table?

If you have proper symbols throughout the rest of the disassembly, it might be that it has disassembled data, but I don't think it should with my command. It is also possible that you have built an executable targetting a newer architecture (not specifying one might pick the host architecture, or the default is Pentium 3 now).

If there are almost no symbols, then you need to stop removing them.