Sponsored Content
Full Discussion: Help with Vim
Special Forums UNIX and Linux Applications Help with Vim Post 302197814 by led3234 on Wednesday 21st of May 2008 06:55:51 PM
Old 05-21-2008
Question Help with Vim

How do I use compilers and syntax highlighting in (g)Vim?

Specifically, I need a Common Lisp compiler and a C++ compiler.

Thanks in advance!

(Note: Disregard my other topic.)
 

10 More Discussions You Might Find Interesting

1. Solaris

Vim 7.0

I want to install VIM 7.0 from sunfreeware.com onto a server. The security guys are giving me a hard time because they found this security vulnerability. http://xforce.iss.net/xforce/xfdb/6259 This vulnerability came out in 2001, and it looks like it was mostly for linux, but I cant be... (1 Reply)
Discussion started by: BG_JrAdmin
1 Replies

2. UNIX for Dummies Questions & Answers

how to configure VIM ?

hi today i was working on AIX server and faced many problem while working with VIM. some issues were like configuring VIM where can i configure vim such as ruler was not displayed by default no hlsearch as well as when you try to execute prveious RE with up arrow its not working how to configure... (1 Reply)
Discussion started by: zedex
1 Replies

3. Shell Programming and Scripting

Vim color

How can I change the color in Vim for *sh scripts for words which in brackets "words". In another words for string variables. As I know id depends on /usr/share/vim/vim71/syntax/sh.vim. But I can not find where exactly. (1 Reply)
Discussion started by: mirusnet
1 Replies

4. UNIX for Dummies Questions & Answers

Need some help with vim

I use vim for writing code. I was using nano but found that vim is a much advanced editor. I am trying to achieve something like this: When trying a loop or a function, I generally type: function name() {} Now when I take my cursor one position to the left and press the return key, it give... (4 Replies)
Discussion started by: Legend986
4 Replies

5. UNIX for Advanced & Expert Users

About Vim

Hello, what is the maximum size of a file that we can open using vim. (3 Replies)
Discussion started by: nagalenoj
3 Replies

6. Shell Programming and Scripting

Vim - Question

Hi, I'm not sure whether this is the right place for my question. For scripting I use very often Vim because it's almost available on all unix stations. Sometimes it would be very helpful to exchange text inside Vim with other programs and the other way round! For example I want to copy... (4 Replies)
Discussion started by: climber
4 Replies

7. UNIX for Advanced & Expert Users

vim

Does anyone know the fast way to go to tab/2 distance in vim. I mean set four spaces. (1 Reply)
Discussion started by: mirusnet
1 Replies

8. Solaris

Very Importan - Vim Settings - Error while opening a File using vim

I downloaded vim.7.2 and compiled the vim source . Added the vim binary path to PATH (Because iam not the root of the box) when i load the file using vim it throws me an error Error detected while processing /home2/e3003091/.vimrc: line 2: E185: Cannot find color scheme darkblue line... (0 Replies)
Discussion started by: girija
0 Replies

9. Linux

VI/VIM ERROR ^Z

Dear Unix user, I'm using putty 0.60 (on Windows Vista) to connect by ssh protocol to other Linux computer. I have a problem with VI/VIM. When I key button "n" or "b", it returns me n^Z or b^Z. What could the problem be?! Thanx a lot, Maria Elena (0 Replies)
Discussion started by: mesana
0 Replies

10. UNIX for Advanced & Expert Users

Vim :f

Can someone please tell me what this does? :f word I thought that was the way to save files with a different name but after a quick google search I saw it was like this. :w filename (4 Replies)
Discussion started by: cokedude
4 Replies
mpicc(1)							     Open MPI								  mpicc(1)

NAME
mpicc -- Open MPI C wrapper compiler SYNTAX
mpicc [-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 "mpicc --showme" and "mpicc --showme my_source.c" will show all the wrapper-supplied flags. But "mpicc -showme -v" will only show the underlying compiler name and "-v". -showme:compile Do not invoke the underlying C compiler. Instead, show the compiler flags that would be supplied to the C compiler. -showme:link Do not invoke the underlying C compiler. Instead, show the linker flags that would be supplied to the C compiler. See the man page for your underlying compiler for other options that can be passed through mpicc 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 mpicc is a convenience wrappers for the underlying C 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. mpicc passes its arguments to the underlying C 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 mpicc. 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/mpicc-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 OMPI
Open MPI mpicc(1)
All times are GMT -4. The time now is 08:45 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy