Sponsored Content
Operating Systems AIX Migrating C Application from AIX to Linux Post 302344046 by fpmurphy on Friday 14th of August 2009 12:05:14 PM
Old 08-14-2009
Please provide the output from gcc -v on Linux box. "HP UNIX GCC" simply does not sound to be right for such output.

Even better would be the output from gcc -### for both systems.

Can you provide an example of some of the errors you are getting?
Which particular version of GNU/Linux are you porting the application to?
 

9 More Discussions You Might Find Interesting

1. AIX

Problem with migrating from AIX 5.1 to 5.3

I'am migrating from AIX 5.1 to 5.3 during migration installation a receive message enough space for dir /usr. My question is : how i can resolve this problem ? i can't reboot my server i hope that there is a command to obtain a spece without go out from installation procedure pannel... I'am... (0 Replies)
Discussion started by: tt155
0 Replies

2. AIX

Migrating AIX users to Linux

Hi all, I was wondering if anyone out there knew if it was possible to migrate users from AIX to Linux. What we want to do is install OpenLDAP on a Linux machine and port all the users over to LDAP. I've googled around and could only find a few things, such as mrgpwd - but that only comes... (0 Replies)
Discussion started by: djcronos
0 Replies

3. AIX

Can I make application for AIX while working on Linux Box

Hi all, I had a large application created using Visual C++. I ported that application using WINE to the Linux platform (ofcourse x86). Now I have to port the same application to AIX which runs over IBM mainframe. I dont have mainframe available but it is required for me to port my application to... (1 Reply)
Discussion started by: noble_curious
1 Replies

4. AIX

migrating easytrieve from Z/OS to AIX platform

Hi, my requirement is to migrate easytrieve running on Z/OS to AIX platform. can anyone let me know what changes should be made if we do such a migration. (0 Replies)
Discussion started by: rohit510
0 Replies

5. AIX

AIX Servers Ugrading or Migrating

:( Hi Grue, I am very new in AIX/UNIX environment. Please give me answer that during the upgrading or Migrating to 6.1 the AIX Server the applications of this server is accessible to Apps users or not? Thanks (2 Replies)
Discussion started by: Tahniet
2 Replies

6. AIX

Migrating a NIM Server to AIX 6.1

Guys, We are planning to upgrade one of our NIM server to AIX 6.1 from 5.3... Since the server itself is a NIM Server we can't perform it via NIM & I'm choosing to do CD install.. The Install method would be Upgrade installation. Is there anything special that I need to consider before... (5 Replies)
Discussion started by: kkeng808
5 Replies

7. AIX

Migrating from HP Unix to IBM AIX 6.1

HI , We are in process to migrate from UNIX to AIX 6.1 version . I need to understand differences between commands that are used in UNIX and AIX. I want to make sure AIX has all command options avaliable from HP Unix.If any mismatch it should be addressed . Since many commands are used it... (2 Replies)
Discussion started by: Perlbaby
2 Replies

8. AIX

Upgrading to AIX 7 vs migrating

Hi all, I have this weird notion that upgrading the TL does not cause the machine to wipe, but upgrading a major version (from aix 6 to 7) means it's actually a fresh install and will wipe the date and i have to install the software again (TSM server, for instance). Trying to google it, i came... (3 Replies)
Discussion started by: tde3000
3 Replies

9. AIX

Migrating NFSv3 to NFSv4 in AIX

Hello, I worked on setting up NFSv3 and NFSv4 (novice) shares separately. I was trying to find a way to migrate existing NFSv3 fileshares to NFSv4 as is. I found a redbook online called "Securing NFS in AIX". It has good info. I am able to create a new NFSv4 share, do not know how to... (4 Replies)
Discussion started by: System Admin 77
4 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 03:17 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy