Re: [Tinycc-devel] Successful Configure/Build, No Output

[David Mertens]

The more I think about this, the more I'm convinced it's a problem with your system's compiler. The code is right there: "gcc -o some-obj-file.o other-args", yet you don't get the .o file. I don't think tcc's makefile is doing anything behind the scenes to circumvent the system compiler's output.

I presume you've managed to compile other C programs with your system compiler on this box?

David

On Wed, Aug 28, 2013 at 7:05 AM, Cayce Pollard <address@hidden> wrote:

To be more specific, no binaries or object files on my CentOS 5.5 build VM

My CentOS 6 build VM compiles successfully.

Since I downloaded a pre-built image for the CentOS 6 VM and built the CentOS 5.5 VM from an ISO, I suspect I may be missing a necessary package (or packages) but I'm not sure how to determine if this is the case.  Not sure I mentioned this before but I'm very new to building in general and building on Linux specifically; my primary platform is Windows.  I didn't want to work with Cygwin because of the massive amounts of issues.

On Wed, Aug 28, 2013 at 4:08 AM, MLO <address@hidden> wrote:

Yes...no binaries or object files.

On Aug 27, 2013 7:46 AM, "Thomas Preud'homme" <address@hidden> wrote:

Le lundi 26 août 2013 19:21:14 Cayce Pollard a écrit :
> I ran sudo make tcc > build.log...hopefully that's what was meant.
> Results are attached to this email

Yes sorry, I forgot there was a mail I didn't reply to. So you are saying
there is no tcc or tcc.o file in the directory where you called make from?

Best regards,

Thomas

_______________________________________________
Tinycc-devel mailing list
address@hidden
https://lists.nongnu.org/mailman/listinfo/tinycc-devel

_______________________________________________
Tinycc-devel mailing list
address@hidden
https://lists.nongnu.org/mailman/listinfo/tinycc-devel

--
 "Debugging is twice as hard as writing the code in the first place.
  Therefore, if you write the code as cleverly as possible, you are,
  by definition, not smart enough to debug it." -- Brian Kernighan