Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
| From | Ian Collins <ian-news@hotmail.com> |
|---|---|
| Newsgroups | comp.lang.c |
| Subject | Re: OT - gcc for Windows not being recognized by Windows 7 |
| Date | 2015-07-06 10:39 +1200 |
| Message-ID | <cvtq1dFb0gvU1@mid.individual.net> (permalink) |
| References | (10 earlier) <mn9rse$903$1@dont-email.me> <cvrkqbFeu8iU1@mid.individual.net> <mnb1hp$ge9$1@dont-email.me> <20150705210821.6bd31567@maxa-pc> <mnc0b8$1o6$1@dont-email.me> |
Bartc wrote: > On 05/07/2015 20:08, Melzzzzz wrote: >> > >> Windows command line sucks, badly. On Unix libs and include files >> are system global so that every compiler knows where to look for, while >> on Windows no such thing. > > I find Linux utterly impossible. > > And why should there actually be any difficulty in knowing where to > look? In the same place as the executable is a good start! A short > relative distance from the executable is also acceptable (eg. ..\include > when "." is where the executable has been started from). On Unix and Linux, the standard libraries and headers are part of the platform and they all live in standard places (/usr/include and /usr/lib). Compiler specific file locations are known to the compiler (in the case of gcc, these are specified at build time). > (Since, after all, programs can be packaged so that all the support > files are added to the executable. So it's a natural place to look when > the files happen to be discrete.) > > But I remember from previous investigations that in Linux, it is > apparently impossible to find out where the executable was started from, > so there's no way to access any support files that way if they're in the > same place, unless the location is hard-coded. (And then you have > problems with multiple versions because they can't all be in the same > place.) Eh? For the two version I have on this box: /opt/gcc4.9/bin/gcc -v Using built-in specs. COLLECT_GCC=/opt/gcc4.9/bin/gcc COLLECT_LTO_WRAPPER=/opt/gcc4.9/libexec/gcc/i386-pc-solaris2.11/4.9.2/lto-wrapper Target: i386-pc-solaris2.11 Configured with: ../gcc_4_9_2_release/configure --prefix=/opt/gcc4.9 --enable-languages=c,c++ Thread model: posix gcc version 4.9.2 (GCC) gcc -v Using built-in specs. COLLECT_GCC=/opt/local/gcc47/bin/gcc COLLECT_LTO_WRAPPER=/opt/local/gcc47/libexec/gcc/x86_64-sun-solaris2.11/4.7.2/lto-wrapper Target: x86_64-sun-solaris2.11 Configured with: ../gcc-4.7.2/configure --enable-languages='c fortran c++' --enable-shared --enable-long-long --with-local-prefix=/opt/local/gcc47 --enable-libssp --enable-threads=posix --with-boot-ldflags='-static-libstdc++ -static-libgcc -Wl,-R/opt/local/lib' --disable-nls --enable-__cxa_atexit --with-gxx-include-dir=/opt/local/gcc47/include/c++/ --without-gnu-ld --with-ld=/usr/bin/ld --with-gnu-as --with-as=/opt/local/bin/gas --prefix=/opt/local/gcc47 --build=x86_64-sun-solaris2.11 --host=x86_64-sun-solaris2.11 --infodir=/opt/local/gcc47/info --mandir=/opt/local/gcc47/man Thread model: posix gcc version 4.7.2 (GCC) -- Ian Collins
Back to comp.lang.c | Previous | Next — Previous in thread | Next in thread | Find similar
Re: OT - gcc for Windows not being recognized by Windows 7 raltbos@xs4all.nl (Richard Bos) - 2015-07-03 17:36 +0000
Re: OT - gcc for Windows not being recognized by Windows 7 Ben Bacarisse <ben.usenet@bsb.me.uk> - 2015-07-03 19:22 +0100
Re: OT - gcc for Windows not being recognized by Windows 7 Bartc <bc@freeuk.com> - 2015-07-03 23:37 +0100
Re: OT - gcc for Windows not being recognized by Windows 7 Bartc <bc@freeuk.com> - 2015-07-05 00:58 +0100
Re: OT - gcc for Windows not being recognized by Windows 7 Ian Collins <ian-news@hotmail.com> - 2015-07-05 14:58 +1200
Re: OT - gcc for Windows not being recognized by Windows 7 Bartc <bc@freeuk.com> - 2015-07-05 11:41 +0100
Re: OT - gcc for Windows not being recognized by Windows 7 Bartc <bc@freeuk.com> - 2015-07-05 11:50 +0100
Re: OT - gcc for Windows not being recognized by Windows 7 gazelle@shell.xmission.com (Kenny McCormack) - 2015-07-05 12:18 +0000
Re: OT - gcc for Windows not being recognized by Windows 7 gazelle@shell.xmission.com (Kenny McCormack) - 2015-07-05 12:20 +0000
Re: OT - gcc for Windows not being recognized by Windows 7 Geoff <geoff@invalid.invalid> - 2015-07-05 11:30 -0700
Re: OT - gcc for Windows not being recognized by Windows 7 Melzzzzz <mel@zzzzz.com> - 2015-07-05 21:08 +0200
Re: OT - gcc for Windows not being recognized by Windows 7 Bartc <bc@freeuk.com> - 2015-07-05 20:26 +0100
Re: OT - gcc for Windows not being recognized by Windows 7 Lew Pitcher <lew.pitcher@digitalfreehold.ca> - 2015-07-05 15:45 -0400
Re: OT - gcc for Windows not being recognized by Windows 7 Melzzzzz <mel@zzzzz.com> - 2015-07-05 21:57 +0200
Re: OT - gcc for Windows not being recognized by Windows 7 gazelle@shell.xmission.com (Kenny McCormack) - 2015-07-05 21:28 +0000
Re: OT - gcc for Windows not being recognized by Windows 7 Bartc <bc@freeuk.com> - 2015-07-05 23:39 +0100
Re: OT - gcc for Windows not being recognized by Windows 7 Lew Pitcher <lew.pitcher@digitalfreehold.ca> - 2015-07-05 23:39 -0400
Re: OT - gcc for Windows not being recognized by Windows 7 Bartc <bc@freeuk.com> - 2015-07-06 12:56 +0100
Re: OT - gcc for Windows not being recognized by Windows 7 gazelle@shell.xmission.com (Kenny McCormack) - 2015-07-06 12:58 +0000
Re: OT - gcc for Windows not being recognized by Windows 7 Lew Pitcher <lew.pitcher@digitalfreehold.ca> - 2015-07-06 09:55 -0400
Re: OT - gcc for Windows not being recognized by Windows 7 Richard Kettlewell <rjk@greenend.org.uk> - 2015-07-06 16:26 +0100
Re: OT - gcc for Windows not being recognized by Windows 7 Phil Carmody <pc+usenet@asdf.org> - 2015-07-08 19:55 +0300
Re: OT - gcc for Windows not being recognized by Windows 7 Ian Collins <ian-news@hotmail.com> - 2015-07-06 10:39 +1200
Re: OT - gcc for Windows not being recognized by Windows 7 luser droog <luser.droog@gmail.com> - 2015-07-05 20:30 -0700
csiph-web