Sponsored Content
Full Discussion: man gcc
Top Forums UNIX for Dummies Questions & Answers man gcc Post 13304 by thehoghunter on Tuesday 15th of January 2002 12:58:58 PM
Old 01-15-2002
Rachel,

You need to find where gcc is located. The example that given (/usr/local/gcc) was just that, an example. Your gcc may have been added to any of the filesystems. It may be in a gcc-versionnumber directory (this is again another example). Use find from / and search for "gcc*". Once you find the root path of gcc, then you should find the man pages.
thehoghunter
 

10 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

man pages

Hi folks, I want to know all the commands for which man pages are available. How do i get it? Cheers, Nisha (4 Replies)
Discussion started by: Nisha
4 Replies

2. Programming

man

If i have my own application ( say 'myTool'), then is it possible to create a man page for it? such that "man myTool" will give information about it. if so how to go about it? thanks in advance, Nads (3 Replies)
Discussion started by: Nads
3 Replies

3. UNIX for Dummies Questions & Answers

need help how to use man

hello every one im a new to unix i use solaris 9 experimental i would like to use real unix system but there are to many versions and i need someone to recommend a good one for me i also need help on how to use "man" (3 Replies)
Discussion started by: abu_malek
3 Replies

4. Solaris

Installing gcc - recieve error message gcc : cannot execute

AIM- Install Oracle 11g on Solaris using VMWare Steps 1.Logged on as root 2.Created subfolders à /usr/local/bin & /usr/local/bin/gcc 3.Downloaded gcc & libiconv & unzipped them on my harddrive & burnt them on CD 4.Copied files from CD to /usr/local/bin/gcc 5.Terminal (root) à pkgadd -d... (8 Replies)
Discussion started by: Ackers
8 Replies

5. Solaris

man and ldm man

According to Sun documentation (Ldoms 1.1 Administration Guide), To access the ldm(1M) man page, add the directory path /opt/SUNWldm/man to the variable $MANPATH. When I add the lines: MANPATH=$MANPATH:/opt/SUNWldm/man export MANPATH to .profile, exit root and re-login, I would have "man ldm"... (5 Replies)
Discussion started by: StarSol
5 Replies

6. Linux

man command

Hey people do u know how to disable the man command in linux??? i am not able to do anythg apart from disabling the permission for /usr/bin/... i dont wanna uninstall the man / man pages also... this has been one of the toughest challenges i have come across in linux... can anybody... (5 Replies)
Discussion started by: linux.user
5 Replies

7. Shell Programming and Scripting

Man command

How to get only the options and arguments of a command excluding the descriptive help? (1 Reply)
Discussion started by: mayur_verma
1 Replies

8. Post Here to Contact Site Administrators and Moderators

Man tags

Is it possible to specify the section as well as the OS when using tags? I played with a few combinations but without success. (3 Replies)
Discussion started by: CarloM
3 Replies

9. UNIX for Dummies Questions & Answers

gcc man pages not found under Solaris 10

Hi friends, When I try to see the man pages of gcc, man gcc I see No manual entry for gcc. Could you help me please. I am running solaris 10 Thanks! (4 Replies)
Discussion started by: gabam
4 Replies

10. UNIX for Dummies Questions & Answers

what man*x directories should contain ?

man pages are located beneath /usr/share/man. e.g., manual pages for "section 1" are located in /usr/share/man/man1/. And /usr/share/man/man*p should contain manual pages for POSIX programmers. I need to know what /usr/share/man/man*x directories should contain ? (1 Reply)
Discussion started by: new0h
1 Replies
WINEGCC(1)						      Wine Developers Manual							WINEGCC(1)

NAME
winegcc - Wine C and C++ MinGW Compatible Compiler SYNOPSIS
winegcc [options] infile... DESCRIPTION
winegcc is a gcc wrapper which tries to provide a MinGW compatible compiler under Linux. This is most useful to Win32 developers who can simply take their MinGW code from Windows, and recompile it without modifications under Winelib on Linux. wineg++ accepts mostly the same options as winegcc. The goal of winegcc is to be able to simply replace gcc/g++/windres with winegcc/wineg++/wrc in a MinGW Makefile, and just recompile the application using Winelib under Wine. While typically there are small adjustments that must be made to the application source code and/or Makefile, it is quite easy to do them in a fashion that is compatible between the MinGW and Wine environments. This manual will document only the differences from gcc; please consult the gcc manual for more information on those options. OPTIONS
gcc options: All gcc options are supported, and are passed along to the backend compiler. -Bprefix This option specifies where to find the executables, libraries, include files, and data files of the compiler itself. This is a standard gcc option that has been extended to recognize a prefix ending with '/tools/winebuild', in which case winegcc enters a spe- cial mode for building Wine itself. Developers should avoid prefixes ending with the magic suffix, or if that is not possible, sim- ply express it differently, such as '/tools/winebuild/', to avoid the special behaviour. -fno-short-wchar Override the underlying type for wchar_t to be the default for the target, instead of using short unsigned int, which is the default for Win32. -mconsole This option passes '--subsystem console' to winebuild, to build console applications. It is the default. -mno-cygwin Use Wine's implementation of MSVCRT, instead of linking against the host system's libc. This is necessary for the vast majority of Win32 applications, as they typically depend on various features of MSVCRT. This switch is also used by the MinGW compiler to link against MSVCRT on Windows, instead of linking against Cygwin's libc. Sharing the syntax with MinGW makes it very easy to write Make- files that work under Wine, MinGW+MSYS, or MinGW+Cygwin. -municode Set the default entry point of the application to be the Unicode wmain() instead of the standard main(). -mwindows This option adds -lgdi32, -lcomdlg32, and -lshell32 to the list of default libraries, and passes '--subsystem windows' to winebuild to build graphical applications. -nodefaultlibs Do not use the standard system libraries when linking. These include at a minimum -lkernel32, -luser32, -ladvapi32, and any default libraries used by the backend compiler. The -mwindows option augments the list of default libraries as described above. -nostartfiles Do not add the winecrt0 library when linking. -Wb,option Pass option as an option to winebuild. If option contains commas, it is split into multiple options at the commas. DEFINES
winegcc defines __WINE__, for code that needs to know when it is being compiled under Wine. It also defines WIN32, _WIN32, __WIN32, __WIN32__, __WINNT, and __WINNT__ for compatibility with MinGW. BUGS
The dllimport/dllexport attributes are not supported at the moment, due to lack of support for these features in the ELF version of gcc. Static linking is not currently supported against Wine's DLL. As a result, the -static, --static, and -Wl,-static options will generate an error. AUTHORS
winegcc was written by Dimitrie O. Paun. SEE ALSO
gcc(1), winebuild(1), wrc(1), wine(1), Winelib User Guide, Wine Developers Guide. Wine 1.2-rc6 October 2005 WINEGCC(1)
All times are GMT -4. The time now is 07:22 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy