Slowdown observed in gcc 4.8.0-1 vs 4.7.2-4

Not sure where the appropriate section is for this post.  Mods feel free to move elsewhere.
tl; dr Conclusions:
1) gcc 4.8.0 compiles ~ 5% slower than gcc 4.7.2 compiles.
2) gcc 4.8.0 produces kernels that run slower when compiling than kernels produced by gcc 4.7.2.
Experiment/Discussion:
I read the Intel i7 gcc 4.8 benchmark piece that Phoronix published a week ago wherein they noted some significant slow downs in the 4.8 series.  Now that 4.8.0-1 hit [testing] I wanted to see how the two version compared using a compilation based endpoint with `make -j8 bzImage` in the latest linux package being the test.  This run was repeated 10 times (threw out the first run as a warm up).  Results were analyzed in a oneway ANOVA.
Test machine: Intel i7-3370k @ 4.5 GHz/16 GB RAM running Arch 86_64.
Four test conditions:
1) linux-ck-3.8.5-1 (build with gcc-4.7.2-4) running the benchmark with gcc-4.7.2-4; blue in the graphic below.
2) linux-ck-3.8.5-1 (build with gcc-4.7.2-4) running the benchmark with gcc-4.8.0-1; green in the graphic below.
3) linux-ck-3.8.5-2 (build with gcc-4.8.0-1) running the benchmark with gcc-4.7.2-4; pink in the graphic below.
4) linux-ck-3.8.5-2 (build with gcc-4.8.0-1) running the benchmark with gcc-4.8.0-1; yellow in the graphic below.
Refer to the data plotted in this graphic below which is compile time on the y-axis and conditions on the x-axis.  This is a oneway so all 9 values are plotted as a distribution:
*Compare median blue to green or compare median pink to yellow; result is the 4.8 version of gcc gives ~5 % decrease in efficiency as measured by compilation time.
*Compare median green to yellow; result is that the kernel compiled with 4.8.0-1 runs slower as measured by this end-point.  Yes, it is a trivial slow down of ~272 ms but that slow down is statistically significant.
References:
Here is the script that did the work.
Here is the raw data I generated.
Last edited by graysky (2013-03-30 14:33:40)

It's the first stable version that uses c++, so I think that is not bad, actually. I saw this some days ago: http://rusty.ozlabs.org/?p=330

Similar Messages

  • Exception handling is not working in GCC compile shared object

    Hello,
    I am facing very strange issue on Solaris x86_64 platform with C++ code compiled usging gcc.3.4.3.
    I have compiled shared object that load into web server process space while initialization. Whenever any exception generate in code base, it is not being caught by exception handler. Even though exception handlers are there. Same code is working fine since long time but on Solaris x86, Sparc arch, Linux platform
    With Dbx, I am getting following stack trace.
    Stack trace is
    dbx: internal error: reference through NULL pointer at line 973 in file symbol.cc
    [1] 0x11335(0x1, 0x1, 0x474e5543432b2b00, 0x59cb60, 0xfffffd7fffdff2b0, 0x11335), at 0x11335
    ---- hidden frames, use 'where -h' to see them all ----
    =>[4] __cxa_throw(obj = (nil), tinfo = (nil), dest = (nil), , line 75 in "eh_throw.cc"
    [5] OBWebGate_Authent(r = 0xfffffd7fff3fb300), line 86 in "apache.cpp"
    [6] ap_run_post_config(0x0, 0x0, 0x0, 0x0, 0x0, 0x0), at 0x444624
    [7] main(0x0, 0x0, 0x0, 0x0, 0x0, 0x0), at 0x42c39a
    I am using following link options.
    Compile option is
    /usr/sfw/bin/g++ -c -I/scratch/ashishas/view_storage/build/coreid1014/palantir/apache22/solaris-x86_64/include -m64 -fPIC -D_REENTRANT -Wall -g -o apache.o apache.cpp
    Link option is
    /usr/sfw/bin/g++ -shared -m64 -o apache.so apache.o -lsocket -lnsl -ldl -lpthread -lthread
    At line 86, we are just throwing simple exception which have catch handlers in place. Also we do have catch(...) handler as well.
    Surpursing things are..same issue didn't observe if we make it as executable.
    Issue only comes if this is shared object loaded on webserver. If this is plain shared object, opened by anyother exe, it works fine.
    Can someone help me out. This is completly blocking issue for us. Using Solaris Sun Studio compiler is no option as of now.

    shared object that load into web server process space
    ... same issue didn't observe if we make it as executable.When you "inject" your shared object into some other process a well-being of your exception handling depends on that other process.
    Mechanics of x64 stack traversing (unwind) performed when you throw the exception is quite complicated,
    particularly involving a "nearly-standartized" Unwind interface (say, Unwind_RaiseException).
    When we are talking about g++ on Solaris there are two implementations of unwind interface, one in libc and one in libgcc_s.so.
    When you g++-compile the executable you get it directly linked with libgcc_s.so and Unwind stuff resolves into libgccs.
    When g++-compiled shared object is loaded into non-g++-compiled executable's process _Unwind calls are most likely already resolved into Solaris libc.
    Thats why you might see the difference.
    Now, what exactly causes this difference can vary, I can only speculate.
    All that would not be a problem if _Unwind interface was completely standartized and properly implemented.
    However there are two issues currently:
    * gcc (libstdc++ in particular) happens to use additional non-standard _Unwind calls which are not present in Solaris libc
    naturally, implementation details of Unwind implementation in libc differs to that of libgccs, so when all the standard _Unwind
    routines are resolved into Solaris version and one non-standard _Unwind routine is resolved into gcc version you get a problem
    (most likely that is what happens with you)
    * libc Unwind sometimes is unable to decipher the code generated by gcc.
    However that is likely to happen with modern gcc (say, 4.4+) and not that likely with 3.4.3
    Btw, you can check your call frame to see where _Unwind calls come from:
    where -h -lIf you indeed stomped on "mixed _Unwind" problem then the only chance for you is to play with linker
    so it binds Unwind stuff from your library directly into libgccs.
    Not tried it myself though.
    regards,
    __Fedor.

  • Bridge CS3 slowdown, upgrade to 5 or 6 on Mac?

    My OSX is 10.8.4 and I use PSE10 for mac with Bridge CS3. Recently, I have observed a major slowdown in bridge and some annoying interactions with PSE10. I have about 17,000 jpegs (of insects) organized in hierarchical folders, i.e., taxonomically. I have 4 GB of memory, recently installed.
    1) It now takes several seconds to scroll down through the images in any folder.
    2) Often, when I shift-click to highlight files (to move or rename them), PSE10 opens the files when I don't want it to. Very annoying. I have taken to waiting for a full second or two before I do anything.
    3) Bridge also crashes frequently, at least once a day, and I use it every day.
    OK, would upgrading to Bridge CS5 or 6 fix this problem? Or is this a system thing? And would Bridge CS5 or 6 work with PSE10?

    I agree with Curt, 
    in addition to his post:
    OK, would upgrading to Bridge CS5 or 6 fix this problem? Or is this a system thing? And would Bridge CS5 or 6 work with PSE10?
    Bridge is designed for use with Creative Suite applications an PS elements is not part of the Creative Suite or the Creative Cloud. It might be possible to use Bridge with PSE for opening files in but the advantage of using start up scripts for Photoshop is not available for PS elements.
    I believe PSE 8 for Mac is the only version of PSE that came with Bridge (version 3, part of CS4) so that might be a route for you to follow as the cheapest option.
    Also every new version of Bridge needs a new cache for all the files. (not a big deal but it takes some time with all your files. You have to select the main folder and use 'show items from subfolders' and then let it run overnight to recache again.
    Can you specify what computer you are using. While the minimum required RAM is still advertised as 1 GB you certainly will gain from putting as much RAM as possible in your machine.

  • *** FOUND and SOLVED: Flash Player/Mac slowdown*** DO NOT return your iMacs

    Fellow Apple enthusiasts,
    Sorry for the multiple posts, but I want to get this info out as soon as possible. I've found the cause of the infamous Mac "slowdown." I haven't seen this information posted anywhere yet, and hope to introduce a PROVEN solution to alleviate some frustrations with many Mac users out there. Don't return your iMac! Your hardware is fine. It is an Apple software issue that should be easily remedied with an update.
    I'm posting this here in the iMac section first, because many seem to believe that only the iMac is affected. This is false. It will probably affect any Snow Leopard machine, but the iMacs are the first Macs to come with the Wireless Mouse drivers pre-installed alongside the Magic Mouse.
    THE PROBLEM: Resource leakage, system slowdown, and slow/choppy Flash video playback while pegging CPU utilization for Flash Player, as observed in the Activity Monitor.
    THE CAUSE: MAGIC MOUSE drivers. Yes, the Wireless Mouse update is the cause. With the update installed, the problem will occur as long as the mouse is paired with the Mac.
    It will occur REGARDLESS if:
    - The Magic Mouse is in standby mode
    - The mouse is switched off via power switch underneath
    - The mouse is disconnected under the Bluetooth drop down menu at top of screen
    The reason I'm reporting the Wireless Mouse Update as the culprit is:
    I have a 13" unibody MacBook Pro (Early 2009) and purchased a Magic Mouse online. Received it yesterday - Monday, November 2nd, and updated the Wireless Mouse driver files via Software Update under the Apple menu.
    After the update, I noticed the same Flash Player problems mentioned online, and indeed, System Monitor showed about 104% utilization. Flash videos appeared to be running with 1/2 to 1/3 frame rates.
    * THE SOLUTION: Remove your Magic Mouse using the Bluetooth Utility.
    - Click on the Bluetooth icon at top of screen, and choose "Open Bluetooth Preferences." Or, use equivalent steps via System Prefs.
    - Highlight the Magic Mouse, and then click on the "-" minus at the bottom of the window.
    - Your Magic Mouse will no longer function with your Mac, obviously. Use a different mouse to avoid the problems you've experienced.
    - The Flash video problem will no longer occur, and suspect the resource leakage may cease as well.
    A restart may or may not be necessary, but upon restarting my MBP, Flash video playback returned to normal, with about 40% utilization while streaming a single Flash video.
    The steps above are simply what I used to rectify the problem. I don't know if other bluetooth mice will cause this problem. I have not tested any other wired or wireless mice either.
    I'm just an average user who experienced and recognized the Flash video playback issue on my system. Upon seeing the problem occur, I simply reversed the last change I made to my computer, and found that this solved the problem. Both the problem and the fix are repeatable. The information here has been reported to Apple.
    DON'T RETURN YOUR COMPUTERS! I'm confident that once Apple is aware, a software fix will be made. Again, this will probably occur on any machine running Snow Leopard, and may be even more widespread. I will continue conversation with Apple on this subject.
    Good luck to us all in resolving this issue as quickly and easily as possible.

    Posting here won't get Apple's attention. File a bug report with Apple if you want it to fix the issue. To do ths, join the Apple Developer Connection (ADC)—it's free and available for all Mac users and gets you a look at some development software. Since you already have an Apple username/ID, use that. Once a member, go to Apple BugReporter and file your bug report. The nice thing with this procedur is that you get a response and a follow-up number; thus, starting a dialog with engineering about the issue.

  • Slow File I/O with newer compilers (SPARCompiler 5 and gcc 3)

    Well it's more like slow File I, as I'm only really testing Input, but anyway, here goes...
    I have a simple program that takes a file of about 250mb and simply loops through the file reading it in chunks of 8,192 bytes.
    Basically I'm timing the read speed to try and figure out why there is such a large discrepancy between the older SPARCompiler 3.0.1 : C++ 4.0.1 and the newer 5.0 as well as gcc 3.0 in reading a file. I realize that the old compiler doesn't support STL and that SPARCompiler 5's .h headers basically point to the STL headers, so there is a difference there, but the numbers I get are around 35s with SC 3.0.1 : C++ 4.0.1 to about 90s with SC 5.0 and 76s with gcc 3.0. I understand the numbers are going to vary depending on the test input file size and the machine you're running on, but the ratio's should stay relatively similar if you do run your own tests. That slowdown is pretty much unacceptable in my opinion and I really want the benefits of a new compiler, am I doing something wrong, is this a known issue??
    Command Lines (I did my best to try with different versions of the OS, but Sun licensing makes it hard!):
    With C++ 4.0.1 (tried on Solaris 2.6 and 2.7)
    CC -fast -o IOtest.CC io_read_tst.cpp
    With C++ 5 (used on Solaris 2.5.1 and 2.8)
    CC -O3 -o IOtest.CC5 io_read_tst.cpp
    With gcc 3.0 (tried on Solaris 2.5.1, 2.6, 2.7, and 2.8)
    gcc -O3 -o IOtest.gcc3 io_read_tst.cpp
    I've got the latest patches for the OS and compilers, I've tried compiling on multiple versions of the OS (Solaris 2.5.1, 2.6, 2.7, and 2.8) and always I get similar results, I know I haven't tested every OS possibility, but you have to re-install the OS to test since the compiler is licensed to only one machine, at least for the SUN Compilers anyway! Any help would be greatly, greatly appreciated, code is as follows:
    #include <iostream.h>
    #include <fstream.h>
    #include <time.h>
    int main( )
    char sBuffer[8192];
    time_t startTime, endTime;
    ifstream TestFile;
    TestFile.open( "/data4/tax101/taxtab" ); // Change this to a large file local to your system (~250mb)
    if( TestFile.fail() )
    return( EXIT_FAILURE );
    time( &startTime );
    while( !TestFile.eof() )
    TestFile.read( sBuffer, 8192 );
    time( &endTime );
    cout << endl << "Read Time: " << endTime - startTime << "s\n";
    return( EXIT_SUCCESS );
    Thanks,
    Lance Beddawi
    [email protected]

    Alright, here is my code reposted:
    // Warning.java
    // Reads student data from a text file and writes data to another text file.
    import java.util.;
    import java.io.;
    public class Warning
    // // Reads student data (name, semester hours, quality points) from a
    // text file, computes the GPA, then writes data to another file
    // if the student is placed on academic warning.
    public static void main (String[] args)
    int creditHrs; // number of semester hours earned
    double qualityPts; // number of quality points earned
    double gpa; // grade point (quality point) average
    Scanner scan=null;
    PrintWriter outFile=null;
    String name, inputName = "students.txt";
    String outputName = "warning.txt";
    try
    // Set up Scanner to input file
    scan=new Scanner(new FileInputStream(inputName));
    // Set up the output file stream
    outFile = new PrintWriter(new FileWriter(outputName));
    // Print a header to the output file
    outFile.println ();
    outFile.println ("Students on Academic Warning");
    outFile.println ();
    // Process the input file, one token at a time
    while (scan.hasNext())
    // Get the credit hours and quality points and
    // determine if the student is on warning. If so,
    // write the student data to the output file.
    name=scan.next();
    creditHrs=scan.nextInt();
    qualityPts=scan.nextDouble();
    gpa=qualityPts/creditHrs;
    if ((gpa < 1.5 && creditHrs < 30) || (gpa < 1.75 && creditHrs < 60) || (gpa < 2.0 && creditHrs >= 60))
    outFile.print(name " ");
    outFile.print(creditHrs " ");
    outFile.print(qualityPts " ");
    outFile.print(gpa);
    //Add a catch for each of the specified exceptions, and in each case
    //give as specific a message as you can
    catch (FileNotFoundException e)
    System.out.println("The file " inputName " was not found.");
    catch (IOException e)
    System.out.println("The I/O operation failed and " outputName + " could not be created.");
    catch (InputMismatchException e)
    System.out.println("The input information was not of the right type.");

  • Internet connection slowdown on Macbook

    Over the past few weeks, my internet connection on my Macbook (new 2/08) has become extremely slow, often giving time-out error messages on Safari & Firefox. Previous to this, it was the expected DSL high speed throughput. I have a Cat 5 wired network, and other computers on the network don't have the problem. I've changed the hub to the network on my Mac; still slow. I've repaired privileges and observed CPU, memory, disk and network graphs on the Activity Monitor during internet access without seeing anything that smacks of the problem. Slow at startup and 4 hours later. The Mac acts the same when I'm on the road on a hotel's WiFi, etc. A PC laptop with XP and the same ISP login has no slowdown on my network, so I'm convinced the problem is in the Macbook Anyone experienced this and can give me help? I'm at the point that I'm going to have to quit using my Macbook.

    My slow down in my home office is on a wired Cat5 connection, not wireless. Yesterday I had to work from corp offices, and connected both wired and wireless. Both were near instant download from the internet on all the corporate stuff and on my personal email, and web sites I tested which would seem to indicate there's nothing wrong on my Macbook. Yet, when I got home and tested again on my home network, my Mac had the old slow problem, but all the PCs with MSIE were OK. It's a puzzle. Has anyone figured this one out, or am I hallucinating.

  • Major slowdown causing Aperture to become unusable on MacPro

    I posted this message back in September 08, but the thread has been archived so I cannot reply to it. But the issue is on-going.
    I'm at my wits end with Aperture on my desktop Mac (Mac Pro, 2 x 2.66 Ghz Duel Core, 9GB Ram, Radeon X1900 512Mb video card).
    My library is currently running at over 115,000 managed images divided into projects each around 100-200 images, these are organised into folders for each month of the year, residing in folders for each year. Images pre-2006 are JPEG and the rest, around 31,000, are RAW files.
    When I go into a project and try to edit a caption, select an images, make an adjustment, or just 'Select All' I get the spinning beachball of death, sometimes for up to 5 minuets. Even just clicking on an image to select it in browser mode results in a SBBoD for 20-30 seconds. Adjustments are painful and frustrating. This happens with no other apps running and without Aperture doing any background tasks.
    My library of managed images used to resides on a dedicated 1Tb drive installed in an internal bay of the Mac Pro, vaulted to a third drive. The was rather full so recently U have RAID-ed two drives together to provide more storage and now I have 476GB free, about 1/3 of the drives.
    There is quite obviously something wrong, as once in a while I can edit a project fairly swiftly, making adjustments, using the sliders fluidly and use full-screen mode etc. However, most of the time it is as slow as described.
    It has got to the point when I am editing on my Mac Book Pro (which only contains a few projects, around 500 RAW files) and then transferring the finished project to my Mac Pro for archiving purposes. In fact I have recently exported a project of 1800 RAW files to my laptop to edit, and when finished re-imported to the Mac Pro library as just selecting just a few images to export was taking me half an hour.
    Does anyone have a suggestion as to what might be casing the colossal slowdowns and any tips for fixing it? I have already rebuilt the library and moved it to a drive with more free storage.
    I'd like to hear from users who have over 100k managed RAW images in their libraries and hear what performance is like on certain systems. I'm convinced that Aperture is capable of running fast and smoothly with this size of archive and that I have a more than powerful set-up.

    There is quite obviously something wrong
    We agree that something is wrong. The problem is that with heaviest-graphics work almost anything or any combination of things can compromise performance as described. So...
    • What version of Aperture?
    • What are the files (e.g. mostly 20 MB Nikon NEFs or whatever)?
    • What do you observe long term watching Activity Monitor?
    • What exactly are your hard drive setups including how full, what types of arrays, what lives on what drives, what connectivity, etc.?
    • What routine maintenance have you done on the box since it was new? Not just what you did last week, what was done 2007/2008? Have you ever "migrated" an install?
    • What kinds of apps are on the box? Any free ones? Plug-ins? Any bargain buys that potentially could have been pirate versions carrying malware? Any other users with access to the box?
    • Does this happen after a reboot with only Aperture open and after all hard drives are for sure up and fully running? A common problem is one or more hard drives spinning down, perhaps intermittently. That would exactly describe your symptoms. Note also that some small apps and most plug-ins get installed to auto-launch, so verify that none are running.
    IMO running a Managed-Masters-Library with 100k image files probably requires a perfect RAID array setup for the Library running perfectly along with additional arrays to properly back it all up. Personally I use a RAID0 Library arrayed on two internal drives but use a Referenced-Masters-Library with Masters on external drives to keep Library size reasonable. (Note this para is just an observation, we have a lot more to discuss in order to troubleshoot)
    Buy Disk Warrior (be sure to get the exact version appropriate for your OS) and run it if you have not yet done so.
    Try creating and running as a new user.
    Trash Preferences and restart.
    Repair Permissions immediately before and immediately after any installation that asks for the admin password.
    Although repairing Permissions is not a fix for poor performance, many of us on the Photoshop forums do find that religiously repairing Permissions immediately before and immediately after every installation of any kind helps keep a graphics box running more smoothly. In any event repairing Permissions does no harm, only good.
    If we do not come to a solution I will lend you a new unused HD2600 XT graphics card to try in the event your 1900 card is flaky (which is not uncommon). I bought it but it requires OS 10.5.x and I still use 10.4.11.
    -Allen Wicks

  • Mountain Lion login slowdown & hidd timeout

    I've searched in every part of Internet, and also in this forum, to solve my problem, but until now I haven't found a solution.
    Since some weeks I've observed a peculiar slowdown in the startup of my Mac Mini running Mountain Lion.
    My boot is in verbose mode: when the text mode is finished the login screen appears, but for me is impossible to insert the password: I'm forced to wait about five minutes to insert my credentials, then I log in and everithing is fine and my Mac works perfectly.
    You can easily understand that is an harmless but annoying bug, that slow down my work.
    I've tried to remove every program that is started with the operative system, checked the RAM and the HD, cleaned the system with Onyx, but nothing changes...I've also looked on the console log, and found the message hidd [45]: Timeout waiting for IOKit to be quiet , but I really don't know what to do....any suggestions?

    Please test after taking each of the following steps.
    Step 1
    Disconnect all wired peripherals except those needed to boot, and remove anything that's inserted in the card-reader slot, if your model has one, including an empty adapter.
    Step 2
    Reset the System Management Controller.
    Step 3
    Boot in safe mode. This will cause certain caches maintained by the system to be rebuilt.
    Safe mode is much slower to boot than normal.
    When the login screen appears, reboot as usual (not in safe mode) and test. There's no need to log in while in safe mode.
    Note: If FileVault is enabled on some models, or if a firmware password is set, or if the boot volume is a software RAID, you can’t boot in safe mode. In that case, ask for instructions.

  • Attn: ALL APPLE PORTABLE OWNERS -Macbook Pro, MacBook Air Apple portable slowdown / kernel high CPU solution

    Attn: ALL APPLE PORTABLE OWNERS -MacBook Pro, MacBook Air, Mac mini slowdown kernel / high CPU use problem and solution.
    YOU COULD FRY YOUR COMPUTER IF YOU DO NOT FIX THIS PROBLEM SO PLEASE READ THIS ENTIRE MESSAGE!
    YOUR MAC WILL THANK YOU  
    Hey all.
    Like many of you I've got a newer Apple portable which slows down to an unusable level for an unknown reason. In my case a 13" mid 2009 Intel MacBook Pro Core 2 duo laptop. After many failed attempts to figure out what this nutty problem is I have discovered the problem, the solution and I have solved this for my own MacBook Pro. Since this fix it has been working immediately and consistently -without issue 
    I am sharing this with you in hopes that you to can fix your Apple portable yourself or so you know what to tell the Apple techs so they can quickly fix your Mac from this wacky and unfortunate kernel CPU hogging problem.
    User Software Symptoms :
    Your Apple portable computer periodically for an unknown reason slows down making everything frustratingly slow. This happens even when running previous apps that were never a problem; things that your Mac should be able to handle easily but for some reason now it can't.
    Slowdown most often happens during high CPU use such as gaming, video playback/editing, etc. or when running multiple apps (even non CPU intensive apps) at the same time.
    Possible Hardware Symptoms:
    Your computer is making more noise than it did previously.
    Your computer occasionally makes more noise but then gets quieter.
    Your computer is always extremely quiet (too quiet) even during high CPU apps -worst case scenario.
    It feels hotter than it normally does. Test: After several minutes of the slowness/high kernel CPU touch the computer to feel if it's hotter than normal.
    Looking at Activity Monitor (in the Utilities folder) shows the kernel_task is going bonkers eating up CPU but you have no idea why.
    After trying many different things to solve this problem such as :
    PR ram reset, SMC reset, fresh OS install of 10.5 and 10.6 on external hard-drives, calling and speaking to various Apple tech people who had no ideas/solutions, etc. I had no luck.
    Btw, if you're having the symptoms I've decscribed above I would not run the Apple Hardware check (read below as to why). You could fry your Mac!
    After much testing I found the problem :
    It is my belief that "recent" Apple portable computers are using low quality internal fans which soon stop working!
    Fail time period seems to be about 1.0 years to 2.5 years of use but this fail rate could vary depending on use.
    First noticeable symptoms (depending on what you notice) could be computer slowdown or your fan is making more noise than it normally does. This is your fan's lubrication slowly eroding making your fan spin slower and less smooth resulting in the louder noise and slower rpm spin speed. The slower fan spin speed means less cooling is happening for your computer. The effect on your computer is that the CPU and other chips are heating up! Overheating to be more specific. When your computer's chips overheat they get wonky and screw things up. Most often this seems to have the effect of making the kernel hog CPU resulting in a frustratingly slow user experience! Heat kills computer chips and it is extremely bad for them. Extreme overheat or repeated overheating has been said to shorten the life of computer chips or in extreme cases even fry them completely!
    The longer this goes on without being fixed your fan loses more lubrication and spins slower and slower cooling lesser and lesser resulting in your CPU heating up more and more possibly shortening the life of your Mac! Eventually your fan will stop completely and you could fry your chips! My fan stopped completely and my MBP was running very quietly, too quietly. Luckily I did not fry my chips because I was avoiding using high CPU apps because I knew something was wrong due to the massive slow down and wonkiness when I'd run them.
    Side Note:I'm a bit concerned about all those Mac mini servers which may be using the same defective low quality fans which cannot be easily serviced by their owners as they are co-located in some server facility. One positive thing is those facilities are usually well airconditioned keeping temps low.
    I suggest you do not run the Apple hardware test if you suspect your computer is overheating because the hardware test can seriously heat up your Mac! I tried running this test and my Mac got so hot I had to shut it down forcefully and I was concerned I damaged the chips. If you want to run the Apple hardware check make sure your CPU temperature is ok and that your fan works well before you run the test.
    IF YOU DON'T FIX THIS PROBLEM YOU COULD FRY YOUR COMPUTER DUE TO HEAT DAMAGE!
    DO NOT IGNORE THIS PROBLEM YOUR MACS LIFE MAY DEPEND ON IT!
    First you need to properly diagnose this problem and see if your CPU is getting to hot and you need to see if your fans are spinning at high rpms giving proper cooling, or if they are spinning at low rpms when running high intensive apps as your CPU temp increases.
    TEST IF YOUR FAN(s) IS WORKING CORRECTLY :
    Unfortunately Apple does not include CPU temperature reading software nor fan rpm speed software that I am aware of.
    However, There are two free ways that I know of to check your CPU tempurature and your fan speed :
    One app shows fan speed, and CPU heat, etc.
    One app shows fan speed, CPU heat and allows you to adjust your fan speed settings.
    One app is a dashboard widget, the other is a system preference.
    I suggest you download both of these to check your computer statistics.
    http://www.eidac.de/?p=134
    http://www.islayer.com/apps/istatpro/
    http://fan-control.en.softonic.com/mac
    I am not exactly sure what proper CPU temperatures are for the different Apple computers and this will change given different CPU loads.
    My MBP doesn't seem to function properly with anything around 90 degrees or higher (celcius).
    It seems when the fan is operating normally the CPU temp should not stay above 78 degrees even under heavy load, at least with the apps I'm running in the room temperature I'm in.
    I can post back later with more specific temps under longer load, etc. but I wanted to get this post up for people to read as soon as possible so they don't fry their Macs.
    If a bad fan is your problem :
    THERE ARE ONLY TWO SOLUTIONS FOR THIS PROBLEM :
    Fix or replace your fan so it cools the CPU and other chips properly.
    I fixed my fan myself and I didn't need to buy a new one. Total cost was about $8.00 because I had to buy a #00 sized screwdriver and had it shipped to me. Price includes shipping.
    On my mid 2009 model MacBook Pro fixing the fan was incredibly easy :
    Before I started doing this I wasn't 100% this was the problem so I decided to try to fix my fan instead of ordering a new one and replacing it. As it turns out I didn't need a new fan, I only needed to clean the existing fan and relube it's axl so it could spin easier like when it was new.  It also didn't make sense to buy a brand new fan from an Apple authorized parts reseller selling me the same low quality fan for $49.00 which would probably fail in 2 years again. Prices for new comparable fans from different manufactures range from about $15.00 USD + shipping to around $49.00 USD + shipping depending on where you order them from and what brand you get.
    How to fix / replace your internal fan on a mid 2009 MacBook Pro :
    Please note : I am not a hardware technician, nor expert. If you decide to fix your Mac yourself you do so at your own risk through no fault of my own. Prior to opening up your Mac you should google around and learn how to do it correctly and safely so you won't damage your Mac. For example, it is possible for you to damage your Mac by static electricity from your body. To avoid this I believe proper procedure is that you wear a 'ground strap' (around your wrist) which  you clip to your Mac's metal body so your body will not excude a charge into your Mac. I believe the idea here is to keep your body's charge level and your Mac's similar. Since I do not have a ground strap and fixing/replacing the fan doesn't require touching any chips I did not wear a ground strap during my fan fix. What I did was periodically repeatedly touch the metal case of my MBP hoping that would be enough and it was. Avoid unecessary actions that can build up a static charge in you. Once I started the repair I did not walk around the room building up an electrical charge in my body. Walking on carpet can often build up a large charge in us so it is better to be avoided while working on your Mac. Certain clothing can build up static charges. Combing hair, etc. If you need to get up from your repair when you come back make sure you first touch the Mac's metal case and not anything inside.
    Now that we're done with the scary paranoia, below you will find some instructions on how I fixed my MBP's internal fan
    Before you begin:
    Check out someone's video (not mine) on how to remove / replace the fan (but not take it apart and repair it):
    http://www.youtube.com/watch?v=AghE9newvbs
    Check out someone's web page (not mine) on how to replace the fan in a mid 2009 MacBook Pro:
    http://www.ifixit.com/Guide/Installing-MacBook-Pro-13-Inch-Unibody-Mid-2009-Fan/ 1338/1
    How to repair your mid 2009 MacBook Pro fan:
    Make sure you are in a 'secure' environment. No pets, no kids running around, no drinks near the Mac, etc. 
    Make sure your computer is unplugged from it's power supply and turned off. NOT slept. Totally off / powered down.
    1. Get a size #00 phillips screwdriver (Hobby store, Radioshack, Amazon).
    2. Open up your MBP by unscrewing the bottom (yes flip it over so it's resting upsidedown). Note where each screw goes because some are different lengths. I placed each one around my MBP where they go, insuring I know their order (don't jumble them up). Note which direction your MBP is facing when it's upside down so if you spin it around while working on it you still know where the screws go.
    2b. Some recommend removing the MBP's battery but I didn't do this step. You probably should, just to be safe. Follow the online instructions from the web page I listed about disconnecting the battery.
    3. Unscrew the fan's 3 holding screws.
    4. Unplug the fan's electrical connection (lift it straight up off the board). If you need to you can try to pry it up while you lift with a non metal/non electrical conductive object like a spudger if you have one or -perhaps a pen cap. Before you remove it, look closely at how it's attached so when you put it back on you won't wonder if you're doing it correctly. There's only one way it can go because it cannot fit 'the wrong way' but looking at it closely will make you feel more confident popping it back on when the time comes.
    5. Remove the fan - it easily lifts out.
    6. Take the fan apart by unscrewing it's one screw then unlatching the  plastic clips which hold it together.
    7. Seperate the fan blades from the housing. Lift the fan blades off of the fan housing by pulling it straight out away from the housing.
    8. Clean off the dust that's gathered. A can of compressed air helps here (I didn't have one). I used a little brush from my electric shaver kit which worked well. Once you've removed all the dust from the fan and surrounding areas proceed to the next step.
    9. Reapply new lubrication. You need less than 1 drop. Be sure it covers the entire fan blade axl as this is what needs to be well lubricated. Make sure there isn't excess oil that will fly around when the axl/fan spins at high rpms. I used the only oil I had which was olive oil (for cooking!) but I do not suggest this. At the time I was doing this I didn't know my fan was the problem so I wasn't even sure I was going to relube it. You should probably use something more appropriate perhaps like 3 in 1 oil. A good idea would be to call the manufatures of these little fans and ask them. Maybe a hobby store knows of good lubricants for these purposes?
    DO NOT use things like WD 40 as it's not a long term lubricant or so I've read.
    10. Once your fan is now clean and oiled (make sure there isn't too much oil) reassmble the fan.
    Push the fan blades/axl back into the housing shaft. Give it a few spins with your finger.
    Screw together the fan housing then reclip the clips.
    11. Place the now reassembled fan back into your Mac and screw it in place (3 screws).
    12. Reattach the fan's electrical wiring by gently pushing it into place. Make sure you've got the right end facing down before you push it in place.
    13. Once your Mac's internals are clean and reassembled, place the rear cover back on your Mac and screw it in place.
    14. Double check you didn't forget anything like screws, tools, etc.
    15. Boot up your Mac and monitor the temperature and fan speed using those programs.
    Compare the previous temps/fan speed to the current temp/fan speed.
    Run a high CPU intensive app where your computer has been slowing down.
    You should now have a happy Mac
    If you have this problem and this solution fixed it for you please post in this thread letting me and everyone else know!
    Hope that helps.

    Thanks for your lengthy reminder dude, I have a similar Mac with yours. I suspect its a software fault because it happens after I upgraded to Lion, 10.7.2.

  • An alert message observered while appling latest patch MLR 10

    Hi Gurus,
    While applying latest patch MLR10 we observed an alert message as below
    "Creating log file "C:\oracle\midtier\.patch_storage\8404955\Apply_8404955_05-21-
    2009_15-44-27.log"
    Conflicting patches: 8204237,
    Patch(es) 8204237, conflict with the patch currently being installed (8404955).
    If you continue, patch(es) 8204237, will be rolled back and the
    new patch (8404955) will be installed.
    Note: If the patch currently being installed (8404955) is rolled back,
    it is recommended that the fixes being rolled back here (8204237, ) are reinstal
    led.
    If a merge of the new patch (8404955) and the conflicting patch(es)
    8204237, is required, contact Oracle Support Services and request
    a Merged patch.
    Do you want to STOP?
    Please respond Y|N
    Should we rollback the previous patch before applying MLR10 ? or can i continue with patch application ?
    Thanks in advance,
    Regards,
    Cema

    Please continue the MLR10 patch installation, this message would appear for the all patch installation (of course, patch number would be different though).

  • Some observations on my first use of Data Modeler Beta

    First of all, I can see this tool has a lot of promise.
    I hope Oracle keeps at it, it could turn into a real winner if all the features I see being worked on mature.
    Thanks!
    Here are a few observations on things that I found non-obvious or tedious to do.
    1. When designing an entity, I want to give it a name, a definition, attributes and keys. I want that process to be quick and require the minimum amount of mouse-clicking/navigation fiddling as possible. The current way of defining the attribute's datatype and size is painfully slow. I have to click to get a pop-up. Then I have to click to choose from a set of categories. Then I have to click on a dropdown list. If I try to use the down-arrow on the dropdown list, it works, but not if I go past the one I want. The up-arrow won't take me backwards in the list, so more clicking. It's just a nasty, slow interface to do a simple task that I have to do a thousand times in a data model. If I need to change the size of something, back I go thru the entire process all over again.
    That makes it doubly slow to work in the most natural way, which is to list the attributes and the datatypes, then come back and refine the sizes once the model is maturing and relatively stable.
    2. Adding an additional attribute requires a mouse click instead of a down-arrow. That means I have to take my hands off the keyboard to add a new attribute. Maybe there is some short-cut key that does that, but I have better things to do than memorize non-standard keyboard mappings. Make the down/up arrows works as they should.
    3. Adding the comment that describes the attributes is not quite as slow, but still requires more keystrokes/mouse movements than it should. It's hard enough to get developers to document their attributes, don't discourage them.
    4. I can't see the list of attributes, data types, sizes, key/mandatory settings, and the comment at one time while editing the entity. Makes it harder to grasp what all the attributes mean at a glance, which slows down the modeling and the comprehension of an existing model.
    5. All the entities I created had primary keys with columns in them. But when I tried to have it build a physical model, it complained that some relationships had no columns in them. For the life of me, I couldn't figure out how to fix that. Never had that problem in any other case tool.
    6. Getting it to generate DDL was awkward to find. Make it something obvious, like a button on the toolbar that says "Generate DDL".
    7. Apostrophes in the Comments in RDBMS are not escaped, so the generated DDL won't run.
    8. For the ease of use/speed of use testing on high-volume key tasks, make the developers do the task 1000 times in a row. Make them use long names that require typing, not table A with columns c1, c2 and c3. Long before they get to iteration 1000 they will have many ideas on how to make that task easier and faster to do.
    9. Make developers use names of things that are the maximum length allowed. For example, for a table name in oracle, the max length of the name is 30 characters. The name of one testing table should be AMMMMMMMMMMMMMMMMMMMMMMMMMMMMZ. That's a capital A followed by 28 capital M's and a capital Z. For numbers, use the pattern 1555559. If the developers can't see the A and Z or 1 and 9 in the display area for the name in the default layout for the window, they did the display layout wrong. For places where the text can be really long, choose a "supported visible length" for that field and enter data in the pattern AMMMMMMMMMMMMMMMQMMMMMMMMZ, where Q is placed at the supported visible length. if the A and Q don't show, the layout is wrong.
    10. SQL Developer has quite a few truly gooberish UI interaction designs and I can see some of that carrying over to the Data Modeler tool. I really recommend getting a windows UI expert to design the ui interface, not a java expert. I've seen a lot of very productive windows user interfaces and extremely few java interfaces suitable for high-speed data entry. Give the UI expert the authority to tell the java programmers "I don't want to hear about java coding internals - make the user interface perform this way." I think the technical limitations in java UIs are much less than the mindset limitations I've seen in all to many programmers. That, and making the developers use their code 1000 times in a row to perform key tasks will cause the UI to get streamlined considerably.
    Thanks, and keep up the good work!

    Dear David,
    Again thank you for your valuable and highly appreciated feedback. Find included a more elaborated answer to your observations:
    *1. When designing an entity, I want to give it a name, a definition, attributes and keys.*
    In the new Early Adopter Release, a "SQL developer like" property window has been added for Entities and Tables. For each attribute/column you will have the ability to add name, datatype, Primary Key, Mandatory and comment from one and the same screen
    *2. Adding an additional attribute requires a mouse click instead of a down-arrow.*
    An enhancement request has been created
    *3. Adding the comment that describes the attributes is not quite as slow, but still requires more keystrokes/mouse movements than it should.*
    In the new Early Adopter Release, a "SQL developer like" property window has been added for Entities and Tables. For each attribute/column you will have the ability to add name, datatype, PK, M and comment from one and the same screen
    *4. I can't see the list of attributes, data types, sizes, key/mandatory settings, and the comment at one time while editing the entity. Makes it harder to grasp what all the attributes mean at a glance, which slows down the modeling and the comprehension of an existing model.*
    See former answers. For meaning of attributes you can also use the Glossary and Naming Standardization facilities: see Tools Option menu, Glossary and General Options for naming standards
    *5. All the entities I created had primary keys with columns in them. But when I tried to have it build a physical model, it complained that some relationships had no columns in them. For the life of me, I couldn't figure out how to fix that. Never had that problem in any other case tool.*
    A Bug report has been created. Issue will most probably be solved in the nexr Early Adopter release
    *6. Getting it to generate DDL was awkward to find. Make it something obvious, like a button on the toolbar that says "Generate DDL".*
    An enhancement request has been created.
    *7. Apostrophes in the Comments in RDBMS are not escaped, so the generated DDL won't run.*
    A bug report has been created
    *8. For the ease of use/speed of use testing on high-volume key tasks, make the developers do the task 1000 times in a row. Make them use long names that require typing, not table A with columns c1, c2 and c3. Long before they get to iteration 1000 they will have many ideas on how to make that task easier and faster to do.*
    I aplogize, but I don't understand clearly what you want to say with the use/speed of use here.
    *9. Make developers use names of things that are the maximum length allowed.*
    Our relational model is for use for not just Oracle, but also DB2, SQL Server and in the future maybe other database systems. Whicjh means that we can't taylor it to just one of these database systems. However you can set maxinum name lenghts by clicking right on the diagram and select Model Properties and here you can set naming Options. Here you can also use the Glossary and Naming Standardization facilities: see Tools Option menu, Glossary and General Options for naming standards
    *10. SQL Developer has quite a few truly gooberish UI interaction designs and I can see some of that carrying over to the Data Modeler tool.*
    Fully agree. As you will see in our next Early Adopter release we have started to use SQL Developer like UI objects.
    Edited by: René De Vleeschauwer on 17-nov-2008 1:58

  • ID-CS4: Trouble observing XMLTag changes to page elements (or rather their stories)...

    I have created a small project that uses the same approach to monitoring stories as the one used in the GotoLastTextEdit sample project.
    The GotoLastTextEdit project example does the following:
    - Sets up a responder that monitor open/close signals for documents basically to ensure stories in existing documents gets observers attached.
    - The responder also reacts to the NewStory/DeleteStory signals to attach observers to newly created stories.
    - The observer simply listen for IID_ITEXTMODEL events on the stories.
    Since I'm interrested in xml tagging related changes and not changes to the text, I've changed the IID_ITEXTMODEL to IID_IIDXMLELEMENT. I'm however still looking for events on the TextStoryBoss.
    This approach seems to work. If I create a new document and add some textframes i get notifications whenever I tag/untag/change (tagging) one of them. The really weird part is that if I open a previously saved document nothing works. I get no notifications neither for existing nor for new textframes. Debugging reveals that the observer seems to be attached correctly for both existing and new stories.
    If I change IID_IIDXMLELEMENT back to IID_ITEXTMODEL and listen for changes to the text everything works as expected for both new and existing documents.
    So how do I get IID_IIDXMLELEMENT notifications to work for existing documents?
    Any clues would be helpful...
    Additional info: This was only tested on Windows, InDesign CS4.

    I'm confused by your post and code.  Adobe has a function to do this.  In the Insert Toolbar under the Tab "Forms" there is an option to create a jump menu.  The only options that menu gives you is the same window or a frame on the page (a very outdated action looking at it now).  But with basic knowledge of links you insert the menu and you will get code like:
      <select name="jumpMenu" id="jumpMenu" onChange="MM_jumpMenu('parent',this,0)">
    The "parent" denotes that this will open in the same window.  If you change that to "blank" then it will open in a new window.  A "Go" button is optional and also available in the DW GUI when you set up a jump menu.
    http://www.w3schools.com/tags/att_a_target.asp

  • Plans for gcc 4.0.0?

    Just wondering what Archlinux plans are for gcc 4.0.0, now that it's released.  It seems rather interesting the new features for optimizing, which seems to be right up arch's alley.  An i686-optimized linux distribution, after all, would benefit from better optimizations.
    I'm just hoping that not too much is broken with this new release (everyone remembers gcc 2.95 -> 3), but since this release came much faster and isn't an almost complete rewrite like egcs was, hopefully we can expect a smoother transition.
    I for one am excited about this new gcc release, much more than a new kde, gnome or x.org or whatever...  Maybe it's just me that likes compilers so much and hates bytecode.  But still, what is Arch's stance on this?  Any plans to move forward?  Maybe provide a gcc 4 package but keep compiling arch packages with 3.x until bugs get ironed out?  Or be truly bleeding edge (it is stable software afterall though) and take the plunge and compile arch packages with this new fancy gcc?
    Autovectorization seems rather interesting ( http://gcc.gnu.org/projects/tree-ssa/vectorization.html there's the link for anyone interested), yet needs -msse or -msse2 flags to be set.  Is this feasible?  Would this binary nicely optimized for processors with sse or sse2 run that much worse on hardware without such instructions?
    What is arch's stance on instructions like sse or 3dnow?  Are packages compiled with such optimizations?  If so why or if not why not?  I personally think that most arch users use relatively recent hardware and would benefit...  But then again, I'm just wondering aloud.
    Anyways, sorry for all the questions...

    Duke wrote:What is arch's stance on instructions like sse or 3dnow?  Are packages compiled with such optimizations?  If so why or if not why not?  I personally think that most arch users use relatively recent hardware and would benefit...  But then again, I'm just wondering aloud.
    This has been discussed alot - my stance (not Arch's) is that Arch is i686 based - that's the common factor... if you start creeping with that, when will it stop? first we require SSE, then MMX, then SSE2... we may end up switching from "an i686 optimized distro" to "a distro optimized to run on AMD processors produced after November 12th 2004".
    In addition, SSE instructions only make sense in advanced math applications, FFT programs, and multimedia stuff... it's a small subset of the applications... think about it: how could something like vim benefit from loop vectorization? it really can't... sure you may get some things improved... but it's vim, you don't need to do 50 calculations in the time it takes to do 1 - it's not processor intensive.
    And let's look at the apps that do make use of SSE: multimedia - improve the performance of mpegs and mp3s? who watches that much porn?
    :shock:  :shock:
    FFT programs - anyone seriously doing complex FFT/DSP calcs on Arch? I doubt it
    Advanced Math - sure might make sense, but it doesn't warrant a recompile and optimization of the entire set of packages.
    So, in my opinion, enabling SSE/SSE2/MMX/MMX2/whatever else you get:
    - loss of some processor support
    + improvement in MP3 playback
    + faster calculation of PI
    - a bunch of apps you had to redownload with negligable performance gain

  • Gcc not working with compiled glibc from PKGBUILD

    hello folks, please excuse my english
    i like to compile certain parts of my system, between them are the kernel, glibc , zsh, etc.
    i had noticed that using a compiled version of glibc from abs results in gcc not working at all ( C compiler cannot create executables logs says). this is weird especially because i hadn't had problems before, i have looked for the error mesagges on Google and a lot of people has had this problem but  nobody has a "generic" solution for this
    this is the config.log file from one failed compile of mpg123
    This file contains any messages produced by compilers while
    running configure, to aid debugging if configure makes a mistake.
    It was created by mpg123 configure 1.12.3, which was
    generated by GNU Autoconf 2.65. Invocation command line was
    $ ./configure --prefix=/usr --with-audio=alsa esd sdl
    ## Platform. ##
    hostname = Soul
    uname -m = x86_64
    uname -r = 2.6.34.1
    uname -s = Linux
    uname -v = #1 SMP PREEMPT Tue Jul 6 23:23:17 CLT 2010
    /usr/bin/uname -p = unknown
    /bin/uname -X = unknown
    /bin/arch = x86_64
    /usr/bin/arch -k = unknown
    /usr/convex/getsysinfo = unknown
    /usr/bin/hostinfo = unknown
    /bin/machine = unknown
    /usr/bin/oslevel = unknown
    /bin/universe = unknown
    PATH: /bin
    PATH: /usr/bin
    PATH: /usr/local/bin
    PATH: /sbin
    PATH: /usr/sbin
    PATH: /usr/local/sbin
    PATH: /usr/share/java/apache-ant/bin
    PATH: /usr/lib/perl5/core_perl/bin
    ## Core tests. ##
    configure:2849: checking build system type
    configure:2863: result: x86_64-unknown-linux-gnu
    configure:2883: checking host system type
    configure:2896: result: x86_64-unknown-linux-gnu
    configure:2933: checking for a BSD-compatible install
    configure:3001: result: /bin/install -c
    configure:3012: checking whether build environment is sane
    configure:3062: result: yes
    configure:3203: checking for a thread-safe mkdir -p
    configure:3242: result: /bin/mkdir -p
    configure:3255: checking for gawk
    configure:3271: found /bin/gawk
    configure:3282: result: gawk
    configure:3293: checking whether make sets $(MAKE)
    configure:3315: result: yes
    configure:3402: checking for -Werror in CFLAGS (It breaks tests)
    configure:3412: result: no
    configure:3423: checking if you are up to something totally static with LDFLAGS/CFLAGS
    configure:3443: result: no
    configure:3463: checking for style of include used by make
    configure:3491: result: GNU
    configure:3561: checking for gcc
    configure:3577: found /usr/bin/gcc
    configure:3588: result: gcc
    configure:3817: checking for C compiler version
    configure:3826: gcc --version >&5
    gcc (GCC) 4.5.1
    Copyright (C) 2010 Free Software Foundation, Inc.
    This is free software; see the source for copying conditions. There is NO
    warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
    configure:3837: $? = 0
    configure:3826: gcc -v >&5
    Using built-in specs.
    COLLECT_GCC=gcc
    COLLECT_LTO_WRAPPER=/usr/lib/gcc/x86_64-unknown-linux-gnu/4.5.1/lto-wrapper
    Target: x86_64-unknown-linux-gnu
    Configured with: ../configure --prefix=/usr --enable-languages=c,c++,fortran,objc,obj-c++,ada --enable-shared --enable-threads=posix --enable-__cxa_atexit --enable-clocale=gnu --enable-gnu-unique-object --enable-lto --enable-plugin --disable-multilib --disable-libstdcxx-pch --with-system-zlib --with-ppl --with-cloog --libdir=/usr/lib --libexecdir=/usr/lib --mandir=/usr/share/man --infodir=/usr/share/info
    Thread model: posix
    gcc version 4.5.1 (GCC)
    configure:3837: $? = 0
    configure:3826: gcc -V >&5
    gcc: '-V' option must have argument
    configure:3837: $? = 1
    configure:3826: gcc -qversion >&5
    gcc: unrecognized option '-qversion'
    gcc: no input files
    configure:3837: $? = 1
    configure:3857: checking whether the C compiler works
    configure:3879: gcc -march=amdfam10 -O2 -pipe -Wl,--hash-style=gnu -Wl,--as-needed conftest.c >&5
    /usr/lib/gcc/x86_64-unknown-linux-gnu/4.5.1/../../../../lib/crt1.o: In function `_start':
    (.text+0x12): undefined reference to `__libc_csu_fini'
    /usr/lib/gcc/x86_64-unknown-linux-gnu/4.5.1/../../../../lib/crt1.o: In function `_start':
    (.text+0x19): undefined reference to `__libc_csu_init'
    collect2: ld returned 1 exit status
    configure:3883: $? = 1
    configure:3921: result: no
    configure: failed program was:
    | /* confdefs.h */
    | #define PACKAGE_NAME "mpg123"
    | #define PACKAGE_TARNAME "mpg123"
    | #define PACKAGE_VERSION "1.12.3"
    | #define PACKAGE_STRING "mpg123 1.12.3"
    | #define PACKAGE_BUGREPORT "[email protected]"
    | #define PACKAGE_URL ""
    | #define PACKAGE "mpg123"
    | #define VERSION "1.12.3"
    | /* end confdefs.h. */
    |
    | int
    | main ()
    | {
    |
    | ;
    | return 0;
    | }
    configure:3926: error: in `/var/abs/local/mpg123/src/mpg123-1.12.3':
    configure:3930: error: C compiler cannot create executables
    See `config.log' for more details.
    ## Cache variables. ##
    ac_cv_build=x86_64-unknown-linux-gnu
    ac_cv_env_CCASFLAGS_set=
    ac_cv_env_CCASFLAGS_value=
    ac_cv_env_CCAS_set=
    ac_cv_env_CCAS_value=
    ac_cv_env_CC_set=
    ac_cv_env_CC_value=
    ac_cv_env_CFLAGS_set=set
    ac_cv_env_CFLAGS_value='-march=amdfam10 -O2 -pipe'
    ac_cv_env_CPPFLAGS_set=
    ac_cv_env_CPPFLAGS_value=
    ac_cv_env_CPP_set=
    ac_cv_env_CPP_value=
    ac_cv_env_ESD_CFLAGS_set=
    ac_cv_env_ESD_CFLAGS_value=
    ac_cv_env_ESD_LIBS_set=
    ac_cv_env_ESD_LIBS_value=
    ac_cv_env_JACK_CFLAGS_set=
    ac_cv_env_JACK_CFLAGS_value=
    ac_cv_env_JACK_LIBS_set=
    ac_cv_env_JACK_LIBS_value=
    ac_cv_env_LDFLAGS_set=set
    ac_cv_env_LDFLAGS_value='-Wl,--hash-style=gnu -Wl,--as-needed'
    ac_cv_env_LIBS_set=
    ac_cv_env_LIBS_value=
    ac_cv_env_PKG_CONFIG_set=
    ac_cv_env_PKG_CONFIG_value=
    ac_cv_env_PULSE_CFLAGS_set=
    ac_cv_env_PULSE_CFLAGS_value=
    ac_cv_env_PULSE_LIBS_set=
    ac_cv_env_PULSE_LIBS_value=
    ac_cv_env_SDL_CFLAGS_set=
    ac_cv_env_SDL_CFLAGS_value=
    ac_cv_env_SDL_LIBS_set=
    ac_cv_env_SDL_LIBS_value=
    ac_cv_env_build_alias_set=
    ac_cv_env_build_alias_value=
    ac_cv_env_host_alias_set=
    ac_cv_env_host_alias_value=
    ac_cv_env_target_alias_set=
    ac_cv_env_target_alias_value=
    ac_cv_host=x86_64-unknown-linux-gnu
    ac_cv_path_install='/bin/install -c'
    ac_cv_path_mkdir=/bin/mkdir
    ac_cv_prog_AWK=gawk
    ac_cv_prog_ac_ct_CC=gcc
    ac_cv_prog_make_make_set=yes
    ## Output variables. ##
    ACLOCAL='${SHELL} /var/abs/local/mpg123/src/mpg123-1.12.3/build/missing --run aclocal-1.11'
    AIX_CFLAGS=''
    AIX_LDFLAGS=''
    AIX_LIBS=''
    ALIB_CFLAGS=''
    ALIB_LDFLAGS=''
    ALIB_LIBS=''
    ALSA_CFLAGS=''
    ALSA_LDFLAGS=''
    ALSA_LIBS=''
    AMDEPBACKSLASH='\'
    AMDEP_FALSE='#'
    AMDEP_TRUE=''
    AMTAR='${SHELL} /var/abs/local/mpg123/src/mpg123-1.12.3/build/missing --run tar'
    API_VERSION='25'
    AR=''
    ARTS_CFLAGS=''
    ARTS_LDFLAGS=''
    ARTS_LIBS=''
    AS=''
    AUTOCONF='${SHELL} /var/abs/local/mpg123/src/mpg123-1.12.3/build/missing --run autoconf'
    AUTOHEADER='${SHELL} /var/abs/local/mpg123/src/mpg123-1.12.3/build/missing --run autoheader'
    AUTOMAKE='${SHELL} /var/abs/local/mpg123/src/mpg123-1.12.3/build/missing --run automake-1.11'
    AWK='gawk'
    CC='gcc'
    CCAS=''
    CCASDEPMODE=''
    CCASFLAGS=''
    CCDEPMODE=''
    CFLAGS='-march=amdfam10 -O2 -pipe'
    COREAUDIO_CFLAGS=''
    COREAUDIO_LDFLAGS=''
    COREAUDIO_LIBS=''
    CPP=''
    CPPFLAGS=''
    CYGPATH_W='echo'
    DECODER_LOBJ=''
    DECODER_OBJ=''
    DEFS=''
    DEPDIR='.deps'
    DLLTOOL=''
    DSYMUTIL=''
    DUMMY_CFLAGS=''
    DUMMY_LDFLAGS=''
    DUMMY_LIBS=''
    DUMPBIN=''
    ECHO_C=''
    ECHO_N='-n'
    ECHO_T=''
    EGREP=''
    ESD_CFLAGS=''
    ESD_LDFLAGS=''
    ESD_LIBS=''
    EXEC_LT_LDFLAGS=''
    EXEEXT=''
    FGREP=''
    GREP=''
    HAVE_AIX_FALSE=''
    HAVE_AIX_TRUE=''
    HAVE_ALIB_FALSE=''
    HAVE_ALIB_TRUE=''
    HAVE_ALSA_FALSE=''
    HAVE_ALSA_TRUE=''
    HAVE_ARTS_FALSE=''
    HAVE_ARTS_TRUE=''
    HAVE_COREAUDIO_FALSE=''
    HAVE_COREAUDIO_TRUE=''
    HAVE_DUMMY_FALSE=''
    HAVE_DUMMY_TRUE=''
    HAVE_ESD_FALSE=''
    HAVE_ESD_TRUE=''
    HAVE_HP_FALSE=''
    HAVE_HP_TRUE=''
    HAVE_JACK_FALSE=''
    HAVE_JACK_TRUE=''
    HAVE_MINT_FALSE=''
    HAVE_MINT_TRUE=''
    HAVE_MODULES_FALSE=''
    HAVE_MODULES_TRUE=''
    HAVE_NAS_FALSE=''
    HAVE_NAS_TRUE=''
    HAVE_OPENAL_FALSE=''
    HAVE_OPENAL_TRUE=''
    HAVE_OS2_FALSE=''
    HAVE_OS2_TRUE=''
    HAVE_OSS_FALSE=''
    HAVE_OSS_TRUE=''
    HAVE_PORTAUDIO_FALSE=''
    HAVE_PORTAUDIO_TRUE=''
    HAVE_PULSE_FALSE=''
    HAVE_PULSE_TRUE=''
    HAVE_SDL_FALSE=''
    HAVE_SDL_TRUE=''
    HAVE_SGI_FALSE=''
    HAVE_SGI_TRUE=''
    HAVE_SNDIO_FALSE=''
    HAVE_SNDIO_TRUE=''
    HAVE_SUN_FALSE=''
    HAVE_SUN_TRUE=''
    HAVE_WIN32_FALSE=''
    HAVE_WIN32_TRUE=''
    HP_CFLAGS=''
    HP_LDFLAGS=''
    HP_LIBS=''
    INCLUDE_STDIO_H=''
    INCLUDE_STDLIB_H=''
    INCLUDE_SYS_TYPE_H=''
    INSTALL_DATA='${INSTALL} -m 644'
    INSTALL_PROGRAM='${INSTALL}'
    INSTALL_SCRIPT='${INSTALL}'
    INSTALL_STRIP_PROGRAM='$(install_sh) -c -s'
    JACK_CFLAGS=''
    JACK_LDFLAGS=''
    JACK_LIBS=''
    LD=''
    LDFLAGS='-Wl,--hash-style=gnu -Wl,--as-needed'
    LFS_LOBJ=''
    LIBMPG123_VERSION='25:5:25'
    LIBOBJS=''
    LIBS=''
    LIBTOOL=''
    LIPO=''
    LN_S=''
    LTLIBOBJS=''
    LT_LDFLAGS='-export-dynamic'
    MAKEINFO='${SHELL} /var/abs/local/mpg123/src/mpg123-1.12.3/build/missing --run makeinfo'
    MINT_CFLAGS=''
    MINT_LDFLAGS=''
    MINT_LIBS=''
    MKDIR_P='/bin/mkdir -p'
    MODULE_OBJ=''
    NAS_CFLAGS=''
    NAS_LDFLAGS=''
    NAS_LIBS=''
    NM=''
    NMEDIT=''
    OBJDUMP=''
    OBJEXT=''
    OPENAL_CFLAGS=''
    OPENAL_LDFLAGS=''
    OPENAL_LIBS=''
    OS2_CFLAGS=''
    OS2_LDFLAGS=''
    OS2_LIBS=''
    OSS_CFLAGS=''
    OSS_LDFLAGS=''
    OSS_LIBS=''
    OTOOL64=''
    OTOOL=''
    OUTPUT_CFLAGS=''
    OUTPUT_LDFLAGS=''
    OUTPUT_LIBS=''
    OUTPUT_MOD=''
    OUTPUT_OBJ=''
    PACKAGE='mpg123'
    PACKAGE_BUGREPORT='[email protected]'
    PACKAGE_NAME='mpg123'
    PACKAGE_STRING='mpg123 1.12.3'
    PACKAGE_TARNAME='mpg123'
    PACKAGE_URL=''
    PACKAGE_VERSION='1.12.3'
    PATH_SEPARATOR=':'
    PKG_CONFIG=''
    PORTAUDIO_CFLAGS=''
    PORTAUDIO_LDFLAGS=''
    PORTAUDIO_LIBS=''
    PULSE_CFLAGS=''
    PULSE_LDFLAGS=''
    PULSE_LIBS=''
    RANLIB=''
    SDL_CFLAGS=''
    SDL_LDFLAGS=''
    SDL_LIBS=''
    SED=''
    SET_MAKE=''
    SGI_CFLAGS=''
    SGI_LDFLAGS=''
    SGI_LIBS=''
    SHELL='/bin/sh'
    SNDIO_CFLAGS=''
    SNDIO_LDFLAGS=''
    SNDIO_LIBS=''
    STRIP=''
    SUN_CFLAGS=''
    SUN_LDFLAGS=''
    SUN_LIBS=''
    VERSION='1.12.3'
    WIN32_CFLAGS=''
    WIN32_CODES_FALSE=''
    WIN32_CODES_TRUE=''
    WIN32_LDFLAGS=''
    WIN32_LIBS=''
    ac_ct_CC='gcc'
    ac_ct_DUMPBIN=''
    am__EXEEXT_FALSE=''
    am__EXEEXT_TRUE=''
    am__fastdepCCAS_FALSE=''
    am__fastdepCCAS_TRUE=''
    am__fastdepCC_FALSE=''
    am__fastdepCC_TRUE=''
    am__include='include'
    am__isrc=''
    am__leading_dot='.'
    am__quote=''
    am__tar='${AMTAR} chof - "$$tardir"'
    am__untar='${AMTAR} xf -'
    bindir='${exec_prefix}/bin'
    build='x86_64-unknown-linux-gnu'
    build_alias=''
    build_cpu='x86_64'
    build_os='linux-gnu'
    build_vendor='unknown'
    datadir='${datarootdir}'
    datarootdir='${prefix}/share'
    docdir='${datarootdir}/doc/${PACKAGE_TARNAME}'
    dvidir='${docdir}'
    exec_prefix='NONE'
    host='x86_64-unknown-linux-gnu'
    host_alias=''
    host_cpu='x86_64'
    host_os='linux-gnu'
    host_vendor='unknown'
    htmldir='${docdir}'
    includedir='${prefix}/include'
    infodir='${datarootdir}/info'
    install_sh='${SHELL} /var/abs/local/mpg123/src/mpg123-1.12.3/build/install-sh'
    libdir='${exec_prefix}/lib'
    libexecdir='${exec_prefix}/libexec'
    localedir='${datarootdir}/locale'
    localstatedir='${prefix}/var'
    lt_ECHO='echo'
    mandir='${datarootdir}/man'
    mkdir_p='/bin/mkdir -p'
    oldincludedir='/usr/include'
    pdfdir='${docdir}'
    prefix='/usr'
    program_transform_name='s,x,x,'
    psdir='${docdir}'
    sbindir='${exec_prefix}/sbin'
    sharedstatedir='${prefix}/com'
    sysconfdir='${prefix}/etc'
    target_alias=''
    ## confdefs.h. ##
    /* confdefs.h */
    #define PACKAGE_NAME "mpg123"
    #define PACKAGE_TARNAME "mpg123"
    #define PACKAGE_VERSION "1.12.3"
    #define PACKAGE_STRING "mpg123 1.12.3"
    #define PACKAGE_BUGREPORT "[email protected]"
    #define PACKAGE_URL ""
    #define PACKAGE "mpg123"
    #define VERSION "1.12.3"
    configure: exit 77
    the parts i had searched on google are specificaly the
    "/usr/lib/gcc/x86_64-unknown-linux-gnu/4.5.1/../../../../lib/crt1.o: In function `_start':
    (.text+0x12): undefined reference to `__libc_csu_fini'
    /usr/lib/gcc/x86_64-unknown-linux-gnu/4.5.1/../../../../lib/crt1.o: In function `_start':
    (.text+0x19): undefined reference to `__libc_csu_init'"
    does anyone have an idea of what could it be?
    notice that this doesn't bother me because if i use the glibc from the repositories everything works fine, this is just for curiosity of why it doesn't work
    thanks in advance

    slacknatcher wrote:
    the parts i had searched on google are specificaly the
    "/usr/lib/gcc/x86_64-unknown-linux-gnu/4.5.1/../../../../lib/crt1.o: In function `_start':
    (.text+0x12): undefined reference to `__libc_csu_fini'
    /usr/lib/gcc/x86_64-unknown-linux-gnu/4.5.1/../../../../lib/crt1.o: In function `_start':
    (.text+0x19): undefined reference to `__libc_csu_init'"
    does anyone have an idea of what could it be?
    notice that this doesn't bother me because if i use the glibc from the repositories everything works fine, this is just for curiosity of why it doesn't work
    thanks in advance
    You have stripped glibc too much.  See the Arch PKGBUILD and make sure your makepkg.conf has STRIP_BINARY etc defined.

  • Using additional monitor with iMac 17" Core Duo.. SLOWDOWN

    I bought the mini-dvi to vga adapter to connect my IBM 21" CRT to my iMac for dual display purposes. It works and all, but whenever it's connected my mac slows down to a crawl. I thought originally it was a RAM issue, but once I upgraded to 1GB the result was the same.
    Is anyone else noticing this, or have any solutions?
    It does this in both extended and mirror mode, btw. I'm using OS X 10.4.6.

    After messing around with the settings for a while, it seems that the problem goes away if both monitors are set the same refresh rate. I set my CRT to 60Hz and I don't see the slowdown yet.
    This probably is only a problem if you're using a CRT, since LCDs all generally use 60Hz.

Maybe you are looking for

  • How can I access songs that have been uploaded to my iCloud with itunes Match on a different (work) PC?

    I have logged in with Itunes Match on my work PC, but after 'gathering information about itunes' Itunes Match says the maximum songs that can be uploaded that were not purchased in itunes is 25000 and iMatch stops. All I want to do is have access and

  • Homesharing with family members with different iTunes accounts

    I recently got a new MacBook Air as a graduation gift.  Before, I shared a PC Laptop with my brother.  He has his own iTunes account but we both used the same iTunes program.  Some of the songs on the old computer were mine, some were his.  He's also

  • Appointments Not Showing Up In Work Week View

    Hello  I have Outlook 2013 with 3 calendars that overlay in my Calendar. When I am in Month view all the appointments show but when I go into Work Week they all disappear. I have attached screenshots. This worked before but when i re-added my account

  • Qosmio G30: SPDIF option unavailable in Audio Properties

    Qosmio G30, SigmaTel HD Audio Codec, running XP 2 I'm attempting to route the audio signal thru the built in coaxial out to amp. No signal. When I go to Sounds and Audio Devices>Advanced>Volume control panel /Properties there is no slider /column for

  • Images show up only as blue question marks

    I just purchased a new Macbook Pro approximately one week ago, and concitering it's BRAND NEW I don't understand why I have this problem. On sites like www.deviantart.com and also www.weheartit.com images show up as blue question marks... I have down