fresh_build.py error in libcppunit

Mark Histed's Avatar

Mark Histed

04 Aug, 2010 08:42 PM

I couldn't get mw_supporting/fresh_build.py from latest git to compile libcppunit except with this patch:
For some reason gcc was not happy with -mtune=core2. I didn't investigate in detail.
Mark1

diff --git a/fresh_build.py b/fresh_build.py
index 47574c2..cf6d264 100644
--- a/fresh_build.py
+++ b/fresh_build.py
@@ -43,7 +43,7 @@ elif sdk == '10.6':
     use_gcc_40 = False
     gcc_path = "/usr/bin/gcc-4.2"
     gplusplus_path = "/usr/bin/g++-4.2"
- opt_cflags = "-mtune=core2 "
+ opt_cflags = "-mtune=nocona"
     python_version = "2.6"
 else:
     assert False, "unknown sdk option: %s" % sdk

  1. Support Staff 1 Posted by Christopher Sta... on 05 Aug, 2010 04:14 PM

    Christopher Stawarz's Avatar

    Hi Mark,

    For some reason gcc was not happy with -mtune=core2.

    Interesting. Are you using the latest Xcode (3.2.3)? What kind of CPU is in your build machine? (Presumably, it's not a Core 2. Is it a Xeon?)

    Chris

  2. 2 Posted by Mark Histed on 05 Aug, 2010 05:27 PM

    Mark Histed's Avatar

    Yes,

    Xcode 3.2.3; gcc points at gcc-4.2, and gcc 4.2 exists.

    from system_profiler:
        Hardware Overview:

          Model Name: Mac Pro
          Model Identifier: MacPro4,1
          Processor Name: Quad-Core Intel Xeon

    I got the impression that the error was due to gcc not recognizing that option (perhaps somehow gcc-4.0 was being used??). But I could be wrong. Anyway. If other people see this problem they now know how to fix it.

    Thanks,
    Mark

  3. Support Staff 3 Posted by Christopher Sta... on 05 Aug, 2010 07:38 PM

    Christopher Stawarz's Avatar

    I got the impression that the error was due to gcc not recognizing that option (perhaps somehow gcc-4.0 was being used??)

    The fresh_build.py script runs every night as part of the nightly build, so gcc 4.2 definitely recognizes that option.

    I thought maybe the build was failing because you were on a system that didn't support all of the Core 2 extensions. Although gcc shouldn't have any trouble targeting non-native extensions (after all, it can build for completely different architectures like ARM and PowerPC), it's possible that part of cppunit's build process involves executing some compiled code (e.g. in the capability tests done by configure), and that code failed to run.

    If you're able to reproduce the problem, can you send me the output from fresh_build.py, so I can try to figure out exactly how and why it's failing?

    Thanks,
    Chris

  4. Christopher Stawarz closed this discussion on 17 Aug, 2010 05:42 PM.

Comments are currently closed for this discussion. You can start a new one.

Keyboard shortcuts

Generic

? Show this help
ESC Blurs the current field

Comment Form

r Focus the comment reply box
^ + ↩ Submit the comment

You can use Command ⌘ instead of Control ^ on Mac

Recent Discussions

17 May, 2022 02:12 PM
16 May, 2022 03:12 PM
04 May, 2022 06:02 PM
03 May, 2022 01:30 PM
02 May, 2022 10:47 PM