Generally, yes. I can't say for sure, but I had this problem when linking programs compiled with gcc to libraries compiled with icc (intell compiler). The difference has to do with how the symbols are named and how the functions are called.
Either compile with aCC or recompile the libraries with gcc (but keep both version of libraries around).
dears i working in solaris and when i type make for report it gives me the error kindly can you help me what is the reason
-bash-3.00$ make BPSEXT130
make: Warning: File `BPSEXT130.rc' has modification time 12 s in the future
make BPSEXT130.c
make: Entering directory... (3 Replies)
All,
I have never comipled C code before and would appricaite if anyone could tell me how to build a .exe from a C program.
Thanks in advance. (5 Replies)
howdy....
I am currently in a project, which needs a new distribution of linux..
At first, we select suse as our platform, but this newest version suse is at least several gigabytes. but recently, we want to run out system in a flash card with capacity of 500M, So, self-customized linux is... (6 Replies)
I am facing a problem while building the device driver code.
I am using suse linux "2.6.31.5-0.1-desktop" on my Laptop.
I have copied a folder containing self written device driver files from Mandriva linux to my system having Suse Linux.
I copied the entire folder in "/home/netuser/sun/".... (4 Replies)
Hey everyone, I'm using Linux Mint Debian Edition Gnome, and I'm trying to add the Oracle JDK to the repositories using this simple script, which has never let me down before, but it keeps giving me this error every time I run it, here's my output:
eddie_nygma@enigmatics ~ $ sudo ./oab-java.sh
... (0 Replies)
Hi,
So I downloaded this kernel source and was able to build it successfully.
But I want to add this SDK source code inside, can anyone help me how to do this? Note that the SDK source can be built by itself.
I added the SDK in the main Makefile:
init-y := init/
#added SDK... (0 Replies)
http://uploads.tapatalk-cdn.com/20160725/0174562490859032f68430fb0fa216cd.jpg
I have created a personally made SUSE-based distro using susestudio.com and it will install just fine on my laptops (32-bit Acer Aspire One ZG5 and MacBook 4,1). However, when installing on an old Emachine desktop, I... (6 Replies)
Just decided to run the benchmark for the heck of it.
-Version-
Dist: Debian GNU/Linux 8.5
CPU/Speed: Intel(R) Core(TM) i7-6700K CPU @ 4.00GHz
RAM: DDR4 DRAM 64 GB 3000 MHz CMK64GX4M4B3000C15
MB: Maximus VIII Ranger
Bus: 8 sata, 1 M.2 Socket 3
Cache: L2=4 x 256KB, L3=8 MB shared... (1 Reply)
Hi Team,
My new build configuration always looking for the files from the build where i copied from.
please help me to resolve this.
I am using Visual studio 2008.It has Qt 4.8. plugins,qml,C++ development
I created new debug_new build configuration with additional preprocessor from the... (1 Reply)
Discussion started by: SA_Palani
1 Replies
LEARN ABOUT SUSE
winegcc
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)