Sponsored Content
Special Forums News, Links, Events and Announcements Software Releases - RSS News gccwrap 32bit 2 (Default branch) Post 302180312 by Linux Bot on Sunday 30th of March 2008 10:50:15 PM
Old 03-30-2008
gccwrap 32bit 2 (Default branch)

gccwrap 32bit is a set of simple wrapper scripts to make it easy to compile 32-bit only programs with uncooperative Makefiles on 64-bit systems. You can just use "32bit make" to compile them and the wrappers will transparently add any -m32 options needed and also do some other transparent fixups. This package requires a Linux distribution with proper FHS compliant -m32 / multilib support like SUSE, Fedora, or Mandriva. License: BSD License (revised) Changes:
An xmkmf wrapper was added to fix up autoconf X11R6 detection. A makefile was added for installing the scripts. An explicit notice of the license was put in.Image

More...
 

10 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

change solaris to 32bit

Hi Any one know how to change solaris 7 from 64 bit, back to 32 bit,, i know its on sunsolve somewhere but i cant see it. thanks:D (2 Replies)
Discussion started by: thangorn
2 Replies

2. UNIX for Dummies Questions & Answers

32bit vs 64bit

Whats the difference between 32bit and 64bit OS's or applications. I understand it a little but its just not clicking the way the teacher explained to me thanks, any info would be much appreciated (1 Reply)
Discussion started by: eloquent99
1 Replies

3. UNIX for Dummies Questions & Answers

64bit- or 32bit- processor

when using the command : cat /proc/cpuinfo I get some basic info back on the cpu.. but it doesn't tell me if I am using a 64 or 32 bit processor .. a) is this the right command to find this ? b) if it is not what is ? and how do I get that information.. thanx moxxx68 (2 Replies)
Discussion started by: moxxx68
2 Replies

4. Linux

Linux 32bit or 64bit

Hi, I want to know what is command to know which will tell wheather linux is 32 or 64 bit (5 Replies)
Discussion started by: manoj.solaris
5 Replies

5. Programming

32bit to 64bit conversion.

Is there an 'easy' way to convert 32Bit code to 64Bit code. I have this benchmark i need to run on different machines and it would be nice if i could run it on the 64 bit machines ass wel. The output when compiling(1) and running(2) are the following: (1) linux:/home/user1/subbench/heapsort #... (7 Replies)
Discussion started by: demuynckr
7 Replies

6. Solaris

32bit or 64 bit

Not really a Unix question as such :o, but what advantages or disadvantages are there between using 32bit or 64bit applications on a T5220 running Solaris 10? What about mixing them e.g. 64 bit app using 32 bit libraries or vice versa? (1 Reply)
Discussion started by: JerryHone
1 Replies

7. Solaris

Compiler - 32bit or 64bit?

Hi Gurus, I need to check whether the compiler installed in my system supports 64bit compilation. Server - Sun fire v490 OS - Solaris 5.9 Processor - Sparcv9 (64bit) Install Directory - /opt/SUNWSpro Compiler Model - Sun Forte C Compiler. My development team is claiming that there... (20 Replies)
Discussion started by: Hari_Ganesh
20 Replies

8. SuSE

Libcap.so.2 for SuSE 10 (32bit)

Hello, I am trying to use a worktool on SLES 10 (32-bit) and it is saying I do not have libcap.so.2: error while loading shared libraries: libcap.so.2: cannot open shared object file: No such file or directory Is there an easy way for me to install this library? A quick Google search... (4 Replies)
Discussion started by: bstring
4 Replies

9. UNIX for Advanced & Expert Users

32bit GTK2 application

Hi all, So, I have a 32 bit gtk2.22 application that I run flawlessly in Fedora 14. When I compile it on the 32bit machine run it on Fedora 20 64bit machine I get: (myprogram:6736): Gtk-WARNING **: Unable to locate theme engine in module_path: "adwaita", (myprogram.:6736): Gtk-WARNING **:... (15 Replies)
Discussion started by: fedora18
15 Replies

10. Solaris

Solaris 10 32bit installation

Hi sorry for the novice question. i need to install Solaris 10 32bit version. i downloaded the ISO from oracle website. as i understand the same ISO is for the 64bit as well as the 32bit install??? i ran the install and didn't have the option to choose which architecture to choose? Thanks... (9 Replies)
Discussion started by: guy3145
9 Replies
mpif77(1)							     Open MPI								 mpif77(1)

NAME
mpif77 -- Open MPI Fortran 77 wrapper compiler SYNTAX
mpif77 [-showme|-showme:compile|-showme:link] ... OPTIONS
-showme Do not invoke the underlying compiler. Instead, show the command line that would be executed to compile the program. NOTE: If a non-filename argument is passed on the command line, the -showme option will not display any additional flags. For example, both "mpif77 --showme" and "mpif77 --showme my_source.c" will show all the wrapper-supplied flags. But "mpif77 -showme -v" will only show the underlying compiler name and "-v". -showme:compile Do not invoke the underlying Fortran 77 compiler. Instead, show the compiler flags that would be supplied to the Fortran 77 com- piler. -showme:link Do not invoke the underlying Fortran 77 compiler. Instead, show the linker flags that would be supplied to the Fortran 77 compiler. See the man page for your underlying compiler for other options that can be passed through mpif77 DESCRIPTION
Conceptually, the role of these commands is quite simple: transparently add relevant compiler and linker flags to the user's command line that are necessary to compile / link Open MPI programs, and then invoke the underlying compiler to actually perform the command. As such, these commands are frequently referred to as "wrapper" compilers because they do not actually compile or link applications them- selves; they only add in command line flags and invoke the back-end compiler. Background Open MPI is comprised of three software layers: OPAL (Open Portable Access Layer), ORTE (Open Run-Time Environment), and OMPI (Open MPI). There are wrapper compilers for each layer; each layer's wrapper only links in the libraries relevant for that layer. Specifically, each layer provides the following wrapper compilers: OPAL opalcc and opalc++ ORTE ortecc and ortec++ OMPI mpicc, mpic++, mpicxx, mpiCC (only on systems with case-senstive file systems), mpif77, and mpif90. Note that mpic++, mpicxx, and mpiCC all invoke the same underlying C++ compiler with the same options. All are provided as compatibility with other MPI implementa- tions. The Fortran wrapper compilers for MPI (mpif77 and mpif90) will be inoperative and will return an error on use if Fortran 77 / Fortran 90 support was not built into the MPI layer. Overview mpif77 is a convenience wrappers for the underlying Fortran 77 compiler. Translation of an Open MPI program requires the linkage of the Open MPI-specific libraries which may not reside in one of the standard search directories of ld(1). It also often requires the inclusion of header files what may also not be found in a standard location. mpif77 passes its arguments to the underlying Fortran 77 compiler along with the -I, -L and -l options required by Open MPI programs. The Open MPI Team strongly encourages using the wrapper compilers instead of attempting to link to the Open MPI libraries manually. This allows the specific implementation of Open MPI to change without forcing changes to linker directives in users' Makefiles. Indeed, the specific set of flags and libraries used by the wrapper compilers depends on how Open MPI was configured and built; the values can change between different installations of the same version of Open MPI. Indeed, since the wrappers are simply thin shells on top of an underlying compiler, there are very, very few compelling reasons not to use mpif77. When it is not possible to use the wrappers directly, the -showme:compile and -showme:link options should be used to determine what flags the wrappers would have used. For example: shell$ cc -c file1.c `mpicc -showme:compile` shell$ cc -c file2.c `mpicc -showme:compile` shell$ cc file1.o file2.o `mpicc -showme:link` -o my_mpi_program NOTES
It is possible to make the wrapper compilers multi-lib aware. That is, the libraries and includes specified may differ based on the com- piler flags specified (for example, with the GNU compilers on Linux, a different library path may be used if -m32 is seen versus -m64 being seen). This is not the default behavior in a standard build, but can be activated (for example, in a binary package providing both 32 and 64 bit support). More information can be found at: https://svn.open-mpi.org/trac/ompi/wiki/compilerwrapper3264 FILES
The string that the wrapper compilers insert into the command line before invoking the underlying compiler are stored in a text file cre- ated by Open MPI and installed to $pkgdata/mpif77-wrapper-data.txt, where $pkgdata is typically $prefix/share/openmpi, and $prefix is the top installation directory of Open MPI. It is rarely necessary to edit this file, but it can be examined to gain insight into what flags the wrappers are placing on the command line. ENVIRONMENT VARIABLES
By default, the wrappers use the compilers that were selected when Open MPI was configured. These compilers were either found automati- cally by Open MPI's "configure" script, or were selected by the user in the CC, CXX, F77, and/or FC environment variables before "config- ure" was invoked. Additionally, other arguments specific to the compiler may have been selected by configure. These values can be selectively overridden by either editing the text files containing this configuration information (see the FILES sec- tion), or by setting selected environment variables of the form "OMPI_value". Valid value names are: CPPFLAGS Flags added when invoking the preprocessor (C or C++) LDFLAGS Flags added when invoking the linker (C, C++, or Fortran) LIBS Libraries added when invoking the linker (C, C++, or Fortran) CC C compiler CFLAGS C compiler flags CXX C++ compiler CXXFLAGS C++ compiler flags F77 Fortran 77 compiler FFLAGS Fortran 77 compiler flags FC Fortran 90 compiler FCFLAGS Fortran 90 compiler flags 1.4.5 Feb 10, 2012 mpif77(1)
All times are GMT -4. The time now is 02:29 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy