10-17-2001
Hi Jennifer,
What version of gcc did you end up installing? gcc 2.95.3 or 3.0.1? It does not seem as if the website mentioned of any differences between the two.
I am about to install it but not sure which version should work best for me.
Thanks,
Rachael
10 More Discussions You Might Find Interesting
1. Programming
I packed gcc to /usr/local/ with pkgadd
and when I wan't to compile a c code file it says
gcc: no file
how do I configure gcc on Solaris 8
plz help (1 Reply)
Discussion started by: CreamHarry
1 Replies
2. UNIX for Advanced & Expert Users
Hi, I am having trouble installing gcc 3.4.2-sol8-sparc-local in my sparc machine running solaris 8. It looks like I do not have enough memory in /var , but I have about 3GB free memory in /export/home. I have read some suggestion from previous threads that said it is possible to link /var and... (8 Replies)
Discussion started by: prosper
8 Replies
3. Solaris
Hi,
I tried to install apache web server on solaris 8 and was prompted that i do not have any valid compiler.
I tried to install GCC on solaris 8 using the command
#pkgadd -d gcc-2.95.2-sol17-sparc-local (hit enter). May I know how I should set the environment variables to make it work... (1 Reply)
Discussion started by: sagolo
1 Replies
4. UNIX for Dummies Questions & Answers
I am building gcc-3.4.4 on sol-10 and getting the following error.
my configure is going well but failing in the build stage
***
checking for windres... windres
checking whether to enable maintainer-specific portions of Makefiles... no
updating cache ./config.cache
creating... (0 Replies)
Discussion started by: mobydick
0 Replies
5. Solaris
We are moving from old solaris to new version of solaris. I have copied the gcc compiler installed on old server to new solaris server. But just copying didn't work. So I am trying to build it on the new server. The server version is
sailfish@st-kvar02 -> uname -a
SunOS st-kvar02 5.10... (7 Replies)
Discussion started by: nalina.hv
7 Replies
6. Solaris
Folks -
This may sound like a newbee question - and it is. But a project that I'm managing is under a time crunch and I need a quick answer.
IS it possible to install gcc 2.8.1 on a Solaris 10 Sun box? We have some old libraries that need that version of the compiler in order to work... (2 Replies)
Discussion started by: peridot
2 Replies
7. Solaris
Hi ,
I am installing gcc 3.4.6 on SunOS labcvs001sm 5.9 Generic_117171-07 sun4u sparc
SUNW,Ultra-5_10 . The isa info is 'sparcv'.
I have the following with me
a)gcc-3.4.6.tar
b)gcc-3.4.6-sol9-sparc-local
c)libiconv-1.11-sol9-sparc-local
d) binutils-2.18.tar.gz
e)... (8 Replies)
Discussion started by: sonu2die4
8 Replies
8. Solaris
I have a very simple c++ program like:
> cat easy_gcc.cc
#include <sys/types.h>
#include <sys/ipc.h>
#include <sys/shm.h>
#include <stdio.h>
#include <string.h>
#include <stdlib.h>
#include <unistd.h>
#include <ctype.h>
int debugging = 1;
int main()
{
printf ("This is a... (2 Replies)
Discussion started by: miltony123
2 Replies
9. Solaris
I want to install gcc for Solaris 10 to an alternate location besides /usr/local/bin, so I can't use the pre-compiled package from sunfreeware.com.
So I assume I need to compile gcc for myself and specify --prefix.
How can I accomplish this? Am I pretty much out of luck trying to compile... (3 Replies)
Discussion started by: srhadden
3 Replies
10. Solaris
I just installed gcc from the latest package at sunfreeware.com using pkgadd. I write a simple 'Hello World!' program to test it. I try to compile it and I get this error:
rockstar# gcc hello.c -o hello
ld.so.1: gcc: fatal: libiconv.so.2: open failed: No such file or directory
Killed
I... (0 Replies)
Discussion started by: Bradj47
0 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)