Sponsored Content
Full Discussion: Compiler issue I think...
Homework and Emergencies Homework & Coursework Questions Compiler issue I think... Post 302369453 by pludi on Sunday 8th of November 2009 02:29:25 PM
Old 11-08-2009
What do you mean by "get my compiler to work"? Perl scripts usually aren't compiled like C programs. Or do you get a syntax error? Because I can see 3 definite syntax errors in the code you provided (all in the first 3 code lines). That, plus your total price will be way off (hint: if you reverse something, you'll have to reverse it again to be right again), and your output won't look like you'll expect it to look.
 

9 More Discussions You Might Find Interesting

1. Programming

cc compiler issue

Quick Question, may be very easy to answer. I've just got a Sparc 5 for my home with Solaris 2.6 pre installed onto it. When I go to use the Solaris Compiler 'cc' it comes back to me with the message '/usr/ucb/cc: language optional software package not installed'. Is this something that can be... (2 Replies)
Discussion started by: fishman2001
2 Replies

2. UNIX for Advanced & Expert Users

CC compiler

Hi, If you you have CC installed, then where does it defaultly lives. Thanks (3 Replies)
Discussion started by: vtran4270
3 Replies

3. UNIX for Dummies Questions & Answers

xl C/C++ compiler to GCC compiler

Hi, we are converting from IBM-AIX(xl c/c++ compiler) to Linux(GCC complier). As a part of this i need to change the CFLAGS. The xl c/c++ complier CFLAGS is CFLAGS := $(CDEBUG) $(PROJECT_INCLUDE_DIRS) $(COBJECT_MODE) -qcpluscmt -qmakedep -qcheck=all \ -qalign=bit_packed $(LINT_FLAGS)... (0 Replies)
Discussion started by: pbattu1
0 Replies

4. Solaris

CC 5.5 compiler flag to issue 64bit porting warnings on sparc-solaris

Hi, We are porting our application from 32bit to 64bit. We tried -xarch=v9, -xarc=v9a and -xport64=full options so that compiler to issue 64bit porting warnings. But we are not getting any porting warninings WE are using CC 5.5 compiler on sparc-solaris m/c. Please tell us some powerful... (0 Replies)
Discussion started by: shobhah
0 Replies

5. Linux

GCC compiler issue on redhat4.5

Hi all, I am using gcc4.1.1 on redhat4.5 and when i rethrow an exception and I am catching it .. The application aborts and throws the following error message to stdout - the error that's been thrown is been caught but never gets that far as it falls over on throw statement Has anyone ever... (0 Replies)
Discussion started by: nano2
0 Replies

6. Red Hat

g++ compiler issue

Hi i need to install g++ compiler in RHEL 5.1 and i downloaded the compiler from the below mentioned site g++ - Free Software Directory - Free Software Foundation its in format gcc-g++-4.0.2.tar.bz2 and i have unziped it...... can any one tell me the procedure to install it ..it dont... (1 Reply)
Discussion started by: vasanthan
1 Replies

7. Programming

How Can a Machine Reads a Compiler Since A Compiler is Written in Text! Not Binaries?

To make a programming language you need a compiler, so what was the first programming language and how was is created if you need the compiler first? The compiler itself is considered as a high language comparing to the machine! since the compiler is not created in 1's and 0's... Eventhough i... (12 Replies)
Discussion started by: f.ben.isaac
12 Replies

8. UNIX for Dummies Questions & Answers

cc compiler and gcc compiler

hi, can we install gcc compiler in unix based OS(sun solar,IBM AIX,HP,etc) and also can we install sun cc compiler in AIX environment and vice versa. and more ..is linux support cc compiler regards Ajay (3 Replies)
Discussion started by: ajaysahoo
3 Replies

9. Shell Programming and Scripting

shc compiler issue

I am using the shc shell compiler, it works fine, just that when i execute it, it displays the code at the terminal. Is there any way to hide this as well? otherwise it beats the purpose of hiding the code. Thanks ! (7 Replies)
Discussion started by: ysvsr1
7 Replies
CVSBUG(8)						      System Manager's Manual							 CVSBUG(8)

NAME
cvsbug - send problem report (PR) about CVS to a central support site SYNOPSIS
cvsbug [ site ] [ -f problem-report ] [ -t mail-address ] [ -P ] [ -L ] [ --request-id ] [ -v ] DESCRIPTION
cvsbug is a tool used to submit problem reports (PRs) to a central support site. In most cases the correct site will be the default. This argument indicates the support site which is responsible for the category of problem involved. Some sites may use a local address as a default. site values are defined by using the aliases(5). cvsbug invokes an editor on a problem report template (after trying to fill in some fields with reasonable default values). When you exit the editor, cvsbug sends the completed form to the Problem Report Management System (GNATS) at a central support site. At the support site, the PR is assigned a unique number and is stored in the GNATS database according to its category and submitter-id. GNATS automati- cally replies with an acknowledgement, citing the category and the PR number. To ensure that a PR is handled promptly, it should contain your (unique) submitter-id and one of the available categories to identify the problem area. (Use `cvsbug -L' to see a list of categories.) The cvsbug template at your site should already be customized with your submitter-id (running `install-sid submitter-id' to accomplish this is part of the installation procedures for cvsbug). If this hasn't been done, see your system administrator for your submitter-id, or request one from your support site by invoking `cvsbug --request-id'. If your site does not distinguish between different user sites, or if you are not affiliated with the support site, use `net' for this field. The more precise your problem description and the more complete your information, the faster your support team can solve your problems. OPTIONS
-f problem-report specify a file (problem-report) which already contains a complete problem report. cvsbug sends the contents of the file without invoking the editor. If the value for problem-report is `-', then cvsbug reads from standard input. -t mail-address Change mail address at the support site for problem reports. The default mail-address is the address used for the default site. Use the site argument rather than this option in nearly all cases. -P print the form specified by the environment variable PR_FORM on standard output. If PR_FORM is not set, print the standard blank PR template. No mail is sent. -L print the list of available categories. No mail is sent. --request-id sends mail to the default support site, or site if specified, with a request for your submitter-id. If you are not affiliated with site, use a submitter-id of net'. -v Display the cvsbug version number. Note: use cvsbug to submit problem reports rather than mailing them directly. Using both the template and cvsbug itself will help ensure all necessary information will reach the support site. ENVIRONMENT
The environment variable EDITOR specifies the editor to invoke on the template. default: vi If the environment variable PR_FORM is set, then its value is used as the file name of the template for your problem-report editing ses- sion. You can use this to start with a partially completed form (for example, a form with the identification fields already completed). HOW TO FILL OUT A PROBLEM REPORT
Problem reports have to be in a particular form so that a program can easily manage them. Please remember the following guidelines: o describe only one problem with each problem report. o For follow-up mail, use the same subject line as the one in the automatic acknowledgement. It consists of category, PR number and the original synopsis line. This allows the support site to relate several mail messages to a particular PR and to record them automati- cally. o Please try to be as accurate as possible in the subject and/or synopsis line. o The subject and the synopsis line are not confidential. This is because open-bugs lists are compiled from them. Avoid confidential information there. See the GNU Info file cvsbug.info or the document Reporting Problems With cvsbug for detailed information on reporting problems HOW TO SUBMIT TEST CASES, CODE, ETC. Submit small code samples with the PR. Contact the support site for instructions on submitting larger test cases and problematic source code. FILES
/tmp/p$$ copy of PR used in editing session /tmp/pf$$ copy of empty PR form, for testing purposes /tmp/pbad$$ file for rejected PRs INSTALLATION AND CONFIGURATION
See INSTALL for installation instructions. SEE ALSO
gnats(l), query-pr(1), edit-pr(1), gnats(8), queue-pr(8), at-pr(8), mkcat(8), mkdist(8). AUTHORS
Jeffrey Osier, Brendan Kehoe, Jason Merrill, Heinz G. Seidl (Cygnus Support) COPYING
Copyright (c) 1992, 1993 Free Software Foundation, Inc. Permission is granted to make and distribute verbatim copies of this manual provided the copyright notice and this permission notice are preserved on all copies. Permission is granted to copy and distribute modified versions of this manual under the conditions for verbatim copying, provided that the entire resulting derived work is distributed under the terms of a permission notice identical to this one. Permission is granted to copy and distribute translations of this manual into another language, under the above conditions for modified versions, except that this permission notice may be included in translations approved by the Free Software Foundation instead of in the original English. February 1993 xVERSIONx CVSBUG(8)
All times are GMT -4. The time now is 10:24 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy