Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.lang.c > #126168
| From | Keith Thompson <kst-u@mib.org> |
|---|---|
| Newsgroups | comp.lang.c |
| Subject | Re: understanding C issues in geany install |
| Date | 2018-02-01 12:19 -0800 |
| Organization | None to speak of |
| Message-ID | <lnvafg5upo.fsf@kst-u.example.com> (permalink) |
| References | <fdh9l6Fhh6eU1@mid.individual.net> |
fred flintstone <fred@server.invalid> writes:
[...]
> Enough with the prologue.
>
> Q1) Does contemporary standard C have any defined relationship to the
> shell, from the point of view of C?
No. A shell is just a program (which may or may not be written in C).
> Running ./configure ...
> checking for a BSD-compatible install... /usr/bin/install -c
> checking whether build environment is sane... yes
> checking for a thread-safe mkdir -p... /bin/mkdir -p
>
> Q2) What does -c entail in the above?
"man install" will answer that. (On my system, it's ignored; apparently
it meant something in earlier versions.)
> Q3) When I script, I write
> mkdir -p boulder
> , without really knowing why. Is there a place I can look at the C
> source of mkdir on my machine to ascertain why?
Looking at the source would frankly be a silly way to find out what
"mkdir -p" means. Try "man mkdir".
> $ lsb_release -a
> No LSB modules are available.
> Distributor ID: Ubuntu
> Description: Ubuntu 16.04.3 LTS
> Release: 16.04
> Codename: xenial
> $
>
> checking for gcc... gcc
> checking whether the C compiler works... yes
> checking for C compiler default output file name... a.out
> checking for suffix of executables...
> checking whether we are cross compiling... no
> checking for suffix of object files... o
> checking whether we are using the GNU C compiler... yes
> checking whether gcc accepts -g... yes
> checking for gcc option to accept ISO C89... none needed
> checking whether gcc understands -c and -o together... yes
> checking dependency style of gcc... gcc3
> checking how to run the C preprocessor... gcc -E
>
> Nothing crazy looking here. Do I gather correctly that g is an alias for
> gcc?
No. If you're referring to "-g", that's an option that can be passed to
the gcc command. It tells it to produce debugging information. Again,
"man gcc" can tell you more. "info gcc" shows the gcc documentation in
another form that's likely to be more complete (you might need to
install the "gcc-doc" package for that to work).
Incidentally, none of your questions so far are about the C language.
> Also, curious how C 89 and 99 were made to gyve:
> checking for gcc option to accept ISO C99... none needed
>
> checking if gcc static flag -static works... yes
> checking if gcc supports -c -o file.o... yes
> checking if gcc supports -c -o file.o... (cached) yes
>
> Again, cloudy about -c in this context.
Again, it's an option to the gcc command.
> Finally, I have one Big Question:
>
> Does the C Programming Language, as defined by C99, define anything
> about the shells that surround it? It's alright if the answer is no; I
> just want to know what it is.
No.
> From C's point of view, what is bash? Does bash have a standard it
> adheres to? Is that POSIX?
C says nothing about bash. It's a program that happens to be written in
C. "info bash" (if bash-doc is installed) will tell you about bash.
POSIX does impose some requirements on the behavior of the standard
shell; bash follows most of those requirements and adds some
bash-specific features.
[...]
comp.unix.programmer probably would have been a better place for most or
all of these questions.
--
Keith Thompson (The_Other_Keith) kst-u@mib.org <http://www.ghoti.net/~kst>
Working, but not speaking, for JetHead Development, Inc.
"We must do something. This is something. Therefore, we must do this."
-- Antony Jay and Jonathan Lynn, "Yes Minister"
Back to comp.lang.c | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread
understanding C issues in geany install fred flintstone <fred@server.invalid> - 2018-02-01 11:55 -0800
Re: understanding C issues in geany install Malcolm McLean <malcolm.arthur.mclean@gmail.com> - 2018-02-01 12:04 -0800
Re: understanding C issues in geany install Keith Thompson <kst-u@mib.org> - 2018-02-01 12:19 -0800
Re: understanding C issues in geany install Jorgen Grahn <grahn+nntp@snipabacken.se> - 2018-02-04 19:24 +0000
Re: understanding C issues in geany install David Kleinecke <dkleinecke@gmail.com> - 2018-02-04 16:02 -0800
Re: understanding C issues in geany install "James R. Kuyper" <jameskuyper@verizon.net> - 2018-02-01 15:39 -0500
Re: understanding C issues in geany install fred flintstone <fred@server.invalid> - 2018-02-07 07:44 -0800
Re: understanding C issues in geany install Joe Pfeiffer <pfeiffer@cs.nmsu.edu> - 2018-02-01 16:08 -0700
Re: understanding C issues in geany install gordonb.669da@burditt.org (Gordon Burditt) - 2018-02-05 20:56 -0600
Re: understanding C issues in geany install John Bode <jfbode1029@gmail.com> - 2018-02-06 09:26 -0800
Re: understanding C issues in geany install Keith Thompson <kst-u@mib.org> - 2018-02-06 12:36 -0800
Re: understanding C issues in geany install "James R. Kuyper" <jameskuyper@verizon.net> - 2018-02-06 15:49 -0500
Re: understanding C issues in geany install scott@slp53.sl.home (Scott Lurndal) - 2018-02-06 21:37 +0000
csiph-web