cmucam3-hardware (#1) - GCC Corruption? (#4) - Message List

GCC Corruption?

I installed the CMUCam3 software last night and successfully compiled all the sample projects. Worked like a charm.

However, I think something about yesterday's install has corrupted my local gcc compiler. Whenever I try to compile some (straight-C) existing code, everything appears to proceed smoothly, but the output file does not come out executable. I make it executable with "chmod +x", and when attempting to execute, I get "cannot execute binary file".

Executing "file xxx" generates the following, which looks correct (Intel C2D):

ELF 32-bit LSB relocatable, Intel 80386, version 1 (SYSV), not stripped

What happened? Installing the CMUCam3 software is the *only* thing that changed since the last time I used gcc (when it worked).

Thanks, Randy Steck Geo. Mason University Autonomous Robotics Lab

rsteck
04/15/07 15:13:18
Tree View Flat View (newer first) Flat View (older first)
  • Message #4

    Just to make sure we are on the same page, what OS did you install the CC3 software on? Also, what version of x86 gcc did you have installed (type: gcc --version)?

    -anthony

    agr
    04/16/07 11:00:04
    • Message #5

      Thanks for the reply!

      Debian Etch (2.6.18) using GCC 4.1.2.

      I think this is all the steps I took:

      I have the CD that came with the camera, but rather than use those versions of CC3 software I came here to the download page. I grabbed the CC3 source, the Sourcery compiler and the LPC programmer.

      I added the sourcery bin to my path, went into the CC3 folder, did "make" to compile all the sample programs. Then, downloaded the CMUCam2 emulator and tested it (worked fine). Finally, shut down for the night.

      When I brought up the machine the next day and tried to compile a flex/yacc project for school, I get the results from the first message.

      Randy

      rsteck
      04/16/07 13:06:21
      • Message #6

        Hi,

        Do things still break if you remove the Sourcery stuff from your PATH?

        Thanks,

        Adam

        agoode
        04/16/07 13:46:28
        • Message #7

          Yes. First thing I tried.

          rsteck
          04/16/07 15:32:28
          • Message #8

            Sounds very strange. We haven't seen this problem. I think the best thing to try is to make sure your path is okay (so you don't call any arm-gcc tools by accident) and that you do a make clean and build your application again. If "file" is telling you that it is the correct executable, then it should work. Maybe also try compiling a very simple C program and see if that has the same problem. The arm-gcc toolchain should be contained to a single local directory. Do let us know if you figure out the problem.

            -Anthony

            agr
            04/16/07 16:46:40
            • Message #9

              I'm an idiot...

              A "-c" somehow crept into my Makefile, which causes gcc to compile but not link. All is well.

              Thanks for working with me on this non-problem.

              Randy

              rsteck
              04/16/07 21:08:52
              • Message #10

                Ah, glad you figured it out. Have fun with CMUcam!

                Adam

                agoode
                04/16/07 22:22:36
Tree View Flat View (newer first) Flat View (older first)