Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > comp.lang.c > #129779

Re: gcc_centric C code

From Ben Bacarisse <ben.usenet@bsb.me.uk>
Newsgroups comp.lang.c
Subject Re: gcc_centric C code
Date 2018-04-26 11:45 +0100
Organization A noiseless patient Spider
Message-ID <87d0ymtff1.fsf@bsb.me.uk> (permalink)
References <I11EC.8185$oo.4543@fx35.am4> <87tvrzpa32.fsf@bsb.me.uk> <y03EC.21289$Hc3.12547@fx30.am4> <87in8forv8.fsf@bsb.me.uk> <uy9EC.13475$zt5.4840@fx11.am4>

Show all headers | View raw


bartc <bc@freeuk.com> writes:

> On 25/04/2018 23:15, Ben Bacarisse wrote:
>> bartc <bc@freeuk.com> writes:
>
>>> It shows that it likes to be compiled with gcc.
>>
>> I think you missed the conditional (and you certainly ignored the
>> question).  Given that the project uses a configuration/build system
>> (which you chose not to use),
>
> I didn't choose not to. I just can't because I don't know how, and
> when I've tried in the past, the results were hit and miss, usually
> miss, so now I don't even bother.

Ah, I see.  That means you have no idea what the build system might
bring to the party, and thus no idea what your numbers show.  For all
you know the files you took a copy of may include complete or partial
configuration for one or other compiler, yes?

>> Are any of these C compilers in default mode?  The ones I know are not,
>> but I don't know them all.  And for those that are, what version of C do
>> they compile?
>
> If you run any of those compilers with the name of a C file, they will
> compile that file. I don't think specifying the C version to be
> compiled would fix any of the errors I was seeing.

I was commenting on the incorrect statement that you cut.  (It's your
style to remove text with out any indication and you prefer me to do
that in my replies -- which I have done -- but it does not add to the
clarity of the discussion.)

> Here's one such error:

The errors you get on an un-configured or partially configured source
are not interesting (well, not to me, you seem to be interested in
them).  In particular they don't help answer the questions I asked.

> Just as a reminder of how it should be done IMO; pcc64.c

Can you link to this file?  It would be interesting so see just how much
simpler this program is than the one you posted about.

> is a
> byte-code interpreter expressed as C code (about 1/4 the line count of
> the src\lib .c and .h files); pasted from actual output with no
> editing other than the indents:
>
>   c:\cx>bcc pcc64
>   BCC Compiling pcc64.c to pcc64.asm
>
>   c:\cx>mxa pcc64
>   Assembling/linking pcc64.asm... to pcc64.exe
>
>   c:\cx>pcc64 hello
>   Hello, World!
>
> No hassle; no fuss; IT JUST WORKS.

It doesn't work for me.

>>>>> The one problem file for gcc was a missing header that I couldn't find
>>>>> anywhere.
>>>>
>>>> Why do you want to keep it secret?
>>>
>>> Keep what a secret?
>>
>> The missing header file.
>
> It's xcb/xcb.h. There is no xcb directory anywhere in the project.

Indeed.  Why did you think there would be?

-- 
Ben.

Back to comp.lang.c | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread


Thread

gcc_centric C code bartc <bc@freeuk.com> - 2018-04-25 16:21 +0100
  gcc_centric C code Chad <cdalten@gmail.com> - 2018-04-25 08:34 -0700
  Re: gcc_centric C code Ben Bacarisse <ben.usenet@bsb.me.uk> - 2018-04-25 16:41 +0100
    Re: gcc_centric C code Spiros Bousbouras <spibou@gmail.com> - 2018-04-25 16:19 +0000
      Re: gcc_centric C code bartc <bc@freeuk.com> - 2018-04-25 18:02 +0100
        Re: gcc_centric C code Nick Bowler <nbowler@draconx.ca> - 2018-04-25 17:15 +0000
          Re: gcc_centric C code Robert Wessel <robertwessel2@yahoo.com> - 2018-04-25 12:33 -0500
          Re: gcc_centric C code bartc <bc@freeuk.com> - 2018-04-25 20:51 +0100
            Re: gcc_centric C code supercat@casperkitty.com - 2018-04-25 13:01 -0700
              Re: gcc_centric C code bartc <bc@freeuk.com> - 2018-04-25 21:21 +0100
            Re: gcc_centric C code jameskuyper@verizon.net - 2018-04-25 13:45 -0700
        Re: gcc_centric C code Spiros Bousbouras <spibou@gmail.com> - 2018-04-25 17:20 +0000
      Re: gcc_centric C code supercat@casperkitty.com - 2018-04-25 10:30 -0700
        Re: gcc_centric C code Robert Wessel <robertwessel2@yahoo.com> - 2018-04-25 12:35 -0500
          Re: gcc_centric C code Keith Thompson <kst-u@mib.org> - 2018-04-25 10:54 -0700
            Re: gcc_centric C code Philipp Klaus Krause <pkk@spth.de> - 2018-04-25 20:27 +0200
              Re: gcc_centric C code Keith Thompson <kst-u@mib.org> - 2018-04-25 12:38 -0700
              Re: gcc_centric C code Robert Wessel <robertwessel2@yahoo.com> - 2018-04-25 19:53 -0500
                Re: gcc_centric C code Keith Thompson <kst-u@mib.org> - 2018-04-25 18:13 -0700
                Re: gcc_centric C code Nick Bowler <nbowler@draconx.ca> - 2018-04-26 15:16 +0000
                Re: gcc_centric C code Tim Rentsch <txr@alumni.caltech.edu> - 2018-04-27 08:17 -0700
                Re: gcc_centric C code Philipp Klaus Krause <pkk@spth.de> - 2018-04-26 08:03 +0200
                Re: gcc_centric C code Nick Bowler <nbowler@draconx.ca> - 2018-04-26 14:30 +0000
                Re: gcc_centric C code jameskuyper@verizon.net - 2018-04-26 08:26 -0700
                Re: gcc_centric C code Philipp Klaus Krause <pkk@spth.de> - 2018-04-26 19:04 +0200
                Re: gcc_centric C code Ian Collins <ian-news@hotmail.com> - 2018-04-27 07:48 +1200
                Re: gcc_centric C code bartc <bc@freeuk.com> - 2018-04-26 21:08 +0100
                Re: gcc_centric C code Ian Collins <ian-news@hotmail.com> - 2018-04-27 08:18 +1200
                Re: gcc_centric C code bartc <bc@freeuk.com> - 2018-04-26 21:44 +0100
                Re: gcc_centric C code Ian Collins <ian-news@hotmail.com> - 2018-04-27 09:01 +1200
                Re: gcc_centric C code bartc <bc@freeuk.com> - 2018-04-26 23:16 +0100
                Re: gcc_centric C code Ian Collins <ian-news@hotmail.com> - 2018-04-27 10:27 +1200
                Re: gcc_centric C code bartc <bc@freeuk.com> - 2018-04-26 23:48 +0100
                Re: gcc_centric C code Ian Collins <ian-news@hotmail.com> - 2018-04-27 20:41 +1200
                Re: gcc_centric C code bartc <bc@freeuk.com> - 2018-04-27 11:51 +0100
                Re: gcc_centric C code Ian Collins <ian-news@hotmail.com> - 2018-04-28 07:32 +1200
                Re: gcc_centric C code Steven Petruzzellis <frelwizzen@gmail.com> - 2018-04-28 04:34 -0700
                Re: gcc_centric C code Steven Petruzzellis <frelwizzen@gmail.com> - 2018-04-26 23:05 -0700
                Re: gcc_centric C code jacobnavia <jacob@jacob.remcomp.fr> - 2018-04-27 00:52 +0200
                Re: gcc_centric C code supercat@casperkitty.com - 2018-04-26 16:23 -0700
                Re: gcc_centric C code bartc <bc@freeuk.com> - 2018-04-28 11:24 +0100
                Re: gcc_centric C code bartc <bc@freeuk.com> - 2018-04-28 01:42 +0100
                Re: gcc_centric C code Dan Purgert <dan@djph.net> - 2018-04-26 21:40 +0000
                Re: gcc_centric C code bartc <bc@freeuk.com> - 2018-04-26 23:34 +0100
                Re: gcc_centric C code "Chris M. Thomasson" <invalid_chris_thomasson@invalid.invalid> - 2018-04-26 14:13 -0700
                Re: gcc_centric C code "Chris M. Thomasson" <invalid_chris_thomasson@invalid.invalid> - 2018-04-26 14:16 -0700
            Re: gcc_centric C code Tim Rentsch <txr@alumni.caltech.edu> - 2018-04-27 08:08 -0700
              Re: gcc_centric C code Keith Thompson <kst-u@mib.org> - 2018-04-27 09:11 -0700
                Re: gcc_centric C code supercat@casperkitty.com - 2018-04-27 09:26 -0700
                Re: gcc_centric C code Tim Rentsch <txr@alumni.caltech.edu> - 2018-04-27 09:49 -0700
          Re: gcc_centric C code supercat@casperkitty.com - 2018-04-25 12:31 -0700
            Re: gcc_centric C code Nick Bowler <nbowler@draconx.ca> - 2018-04-25 20:13 +0000
              Re: gcc_centric C code supercat@casperkitty.com - 2018-04-25 13:50 -0700
        Re: gcc_centric C code Nick Bowler <nbowler@draconx.ca> - 2018-04-25 18:02 +0000
      Re: gcc_centric C code Steven Petruzzellis <frelwizzen@gmail.com> - 2018-04-25 22:39 -0700
    Re: gcc_centric C code bartc <bc@freeuk.com> - 2018-04-25 18:36 +0100
      Re: gcc_centric C code Ben Bacarisse <ben.usenet@bsb.me.uk> - 2018-04-25 23:15 +0100
        Re: gcc_centric C code bartc <bc@freeuk.com> - 2018-04-26 02:02 +0100
          Re: gcc_centric C code Keith Thompson <kst-u@mib.org> - 2018-04-25 18:28 -0700
          Re: gcc_centric C code Ben Bacarisse <ben.usenet@bsb.me.uk> - 2018-04-26 11:45 +0100
            Re: gcc_centric C code bartc <bc@freeuk.com> - 2018-04-26 14:53 +0100
              Re: gcc_centric C code Ben Bacarisse <ben.usenet@bsb.me.uk> - 2018-04-26 23:38 +0100
                Re: gcc_centric C code bartc <bc@freeuk.com> - 2018-04-27 00:31 +0100
                Re: gcc_centric C code Ben Bacarisse <ben.usenet@bsb.me.uk> - 2018-04-27 00:47 +0100
                Re: gcc_centric C code bartc <bc@freeuk.com> - 2018-04-27 02:28 +0100
                Re: gcc_centric C code Thiago Adams <thiago.adams@gmail.com> - 2018-04-27 03:44 -0700
                Re: gcc_centric C code bartc <bc@freeuk.com> - 2018-05-03 13:57 +0100
                Re: gcc_centric C code Thiago Adams <thiago.adams@gmail.com> - 2018-05-03 11:02 -0700
                Re: gcc_centric C code Thiago Adams <thiago.adams@gmail.com> - 2018-05-03 11:07 -0700
                Re: gcc_centric C code Steven Petruzzellis <frelwizzen@gmail.com> - 2018-05-03 11:13 -0700
                Re: gcc_centric C code bartc <bc@freeuk.com> - 2018-05-03 19:50 +0100
                Re: gcc_centric C code Thiago Adams <thiago.adams@gmail.com> - 2018-05-03 13:37 -0700
                Re: gcc_centric C code Thiago Adams <thiago.adams@gmail.com> - 2018-05-03 13:44 -0700
                Re: gcc_centric C code Thiago Adams <thiago.adams@gmail.com> - 2018-05-11 10:25 -0700
            Re: gcc_centric C code Steven Petruzzellis <frelwizzen@gmail.com> - 2018-04-26 07:01 -0700
          Re: Clearly everyone else likes to do things the hard way Noob <root@127.0.0.1> - 2018-04-26 14:51 +0200
            Re: Clearly everyone else likes to do things the hard way mark.bluemel@gmail.com - 2018-04-26 07:09 -0700
              Re: Clearly everyone else likes to do things the hard way gazelle@shell.xmission.com (Kenny McCormack) - 2018-04-26 17:05 +0000
                Re: Clearly everyone else likes to do things the hard way bartc <bc@freeuk.com> - 2018-04-26 18:38 +0100
                Re: Clearly everyone else likes to do things the hard way 1alvinalbrecht1@gmail.com - 2018-04-26 11:34 -0700
                Re: Clearly everyone else likes to do things the hard way bartc <bc@freeuk.com> - 2018-04-26 21:36 +0100
                Re: Clearly everyone else likes to do things the hard way C W Rose <cwr@seckford.org> - 2018-04-27 19:23 +0100
                Re: Clearly everyone else likes to do things the hard way bartc <bc@freeuk.com> - 2018-04-28 14:34 +0100
                Re: Clearly everyone else likes to do things the hard way Steven Petruzzellis <frelwizzen@gmail.com> - 2018-04-28 10:32 -0700
                Re: Clearly everyone else likes to do things the hard way supercat@casperkitty.com - 2018-04-30 10:16 -0700
                Re: Clearly everyone else likes to do things the hard way bartc <bc@freeuk.com> - 2018-04-30 19:41 +0100
                Re: Clearly everyone else likes to do things the hard way supercat@casperkitty.com - 2018-04-30 12:11 -0700
                Re: Clearly everyone else likes to do things the hard way scott@slp53.sl.home (Scott Lurndal) - 2018-04-30 19:14 +0000
                Re: Clearly everyone else likes to do things the hard way scott@slp53.sl.home (Scott Lurndal) - 2018-04-30 19:12 +0000
                Re: Clearly everyone else likes to do things the hard way bartc <bc@freeuk.com> - 2018-04-30 21:19 +0100
                Re: Clearly everyone else likes to do things the hard way Steven Petruzzellis <frelwizzen@gmail.com> - 2018-04-30 19:23 -0700
                Re: Clearly everyone else likes to do things the hard way Philipp Klaus Krause <pkk@spth.de> - 2018-04-26 19:45 +0200
      Re: gcc_centric C code luser droog <luser.droog@gmail.com> - 2018-04-25 21:56 -0700
        Re: gcc_centric C code bartc <bc@freeuk.com> - 2018-04-26 11:06 +0100
          Re: gcc_centric C code bartc <bc@freeuk.com> - 2018-04-26 11:27 +0100
      Re: gcc_centric C code antispam@math.uni.wroc.pl - 2018-04-26 17:00 +0000
  Re: gcc_centric C code Thiago Adams <thiago.adams@gmail.com> - 2018-04-25 09:26 -0700
  Re: gcc_centric C code Jorgen Grahn <grahn+nntp@snipabacken.se> - 2018-04-26 12:39 +0000
    Re: gcc_centric C code gazelle@shell.xmission.com (Kenny McCormack) - 2018-04-26 13:09 +0000
  Re: gcc_centric C code Wouter Verhelst <w@uter.be> - 2018-04-26 13:26 +0200
    Re: gcc_centric C code bartc <bc@freeuk.com> - 2018-04-26 18:03 +0100
    Re: gcc_centric C code Steven Petruzzellis <frelwizzen@gmail.com> - 2018-04-26 14:32 -0700
  Re: gcc_centric C code Tim Rentsch <txr@alumni.caltech.edu> - 2018-04-27 09:41 -0700
    Re: gcc_centric C code bartc <bc@freeuk.com> - 2018-04-27 19:37 +0100

csiph-web