07-21-2015
Quote:
Originally Posted by
Ultrix
I'm not sure I know what you're talking about. I already have gcc, make, etc. installed on my machine, and have added their directory to $PATH in my startup script. However, when I run gcc, it tells me certain libraries are missing. I can't link C libraries except through XCode. Will downloading the developer tools change this?
You originally said:
Quote:
This means that open source software that is distributed as source is inaccessible to users of newer versions of Mac OS X, because we can't use gcc or make to compile it.
Now you're saying
gcc and
make work just fine, but don't magically download open source libraries needed by the open source software you downloaded from a 3rd party site. When you're downloading open source software, you also have to download, build, and install the open source libraries upon which it depends.
10 More Discussions You Might Find Interesting
1. UNIX for Advanced & Expert Users
I am running a make file through the gnu make tool and i am getting the following error
jsh1035c:/users/egate453/admegate/kapil/samples $ make -f GNUmakefile queue_c
make -f ./GNUmakefile queue_c in_objdir=1 build_root=/users/egate453/admegate/kapil/samples
make: Entering directory... (2 Replies)
Discussion started by: handak9
2 Replies
2. UNIX for Advanced & Expert Users
Hi,
I often encounter make errors. Many a times, a corresponding error code is also shown, like
make: Error 56 (ignored)
make: Error 91 (ignored)
make: Error 96 (ignored)
et al.
I tried google'ing as well as searching this forum for what these error codes mean.
I know, make... (1 Reply)
Discussion started by: vino
1 Replies
3. UNIX for Dummies Questions & Answers
My system is ubuntu, can I use PMake ? (0 Replies)
Discussion started by: meili100
0 Replies
4. Programming
Is this possible? Right now I'm developing some code for Linux, Windows and OS X. To build on each of the systems I've currently got separate build targets for each platform. Ideally I'd like to set up a single make rule that can detect the appropriate target and build it.
I know this is... (2 Replies)
Discussion started by: G_Morgan
2 Replies
5. SCO
Installed GNU make and the GNU C/C++ compiler on SCO Openserver 5.0.7 recently.
Only a normal user is able to run make and compile programs - root is not able to.
Under root, make do run, but root can't access the compiler at all, even tho I set root's path to point to the compiler.... (0 Replies)
Discussion started by: The_Librarian
0 Replies
6. Programming
Hello everybody,
Currently I'm learning how to build projects (C programming) with GNU make. I have a problem with one Makefile and I would appreciate if you could kindly give me a hand. Here is the environment:
OS: Redhat linux 5
compiler: gcc (GCC) 4.1.2 20080704 (Red Hat 4.1.2-44)... (2 Replies)
Discussion started by: dariyoosh
2 Replies
7. AIX
Hi all
i had installed gcc version 3.3.2 on my AIX 5.3 machine.
which make utility i have to instal so it will fit the gcc version
tnx
skfn (2 Replies)
Discussion started by: skfn1203
2 Replies
8. AIX
Hi team,
I am new to unix,and need your advice on the below.
I am using aix5.3 and have installed make-3.82 on the server.
I need to use gmake for configuring and installing a package ,but it is giving error at the below
root@sapsrp:/usr/tmp/xymon-4.3.2
# ./configure.server
... (7 Replies)
Discussion started by: sonal kumar
7 Replies
9. Shell Programming and Scripting
It's been a while since I had to write a Makefile, but I've managed to clobber this together:
SRC=module1.c module2.c
OBJS=$(SRC:%.c=%.o)
HDR=include1.h include2.h
CC=gcc
CFLAGS=-Wall -ggdb -D_XOPEN_SOURCE -I. -ansi
all: program
program: $(OBJS)
$(CC) $(CFLAGS) -o $@ $(OBJS)
... (3 Replies)
Discussion started by: pludi
3 Replies
10. Shell Programming and Scripting
Hi,
I do "touch poub.mlc"
Download my Makefile,
But when I try : make -f Makefile.txt(.txt in order my file to be accepted for upload), it says:"no rule for poub.mlo target"
What is wrong in my Makefile(test yourself please before posting)? (1 Reply)
Discussion started by: synhedionn
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)