HP-UX uses cc -y and cc -g (-y and -g options) C compilation

Login or Register to Reply

Thread Tools Search this Thread
# 8  
I think you can remove the -g option, or perhaps change it to "-ggdb", a popular debugging format for gcc allowing you see symbols when the executable or library is used with gdb, the gnu debugger.

The -y option I'm having more trouble finding. It may refer to "static debugging info", if the HP-UX fortran manpage is relevant, or it may be a corruption of -Y, for "default location for libraries" which I doubt since no folder follows it. So remove it.
Login or Register to Reply

Thread Tools Search this Thread
Search this Thread:
Advanced Search

More UNIX and Linux Forum Topics You Might Find Helpful
Kernel boot options removed by fault, no boot options
Hello Everyone, First of all, I highly appreciate all Linux forum members and whole Linux community. http://forums.linuxmint.com/images/smilies/icon_wink.gif. I wish you the best for all of you ! I will try to be short and concise: I am using Linux Mint 10 for 2 months on 2 ws, and all went...... Ubuntu
Hi All, We have a C program existing in one of the folders which I have to modify a lil bit, When I'm trying to compile the program using GCC or CC command its showing as ksh: gcc: not found is that mean there is no compiler or do I have to verify for something, please advice Thank...... UNIX for Dummies Questions & Answers
UNIX for Dummies Questions & Answers
Compilation Options
hi, currently I have Fedora Core 7 and I use the Compiler ported with FC7. i.e "cc src.c". but I am unable to explore the Compilation Options that can be passed with cc... like cc -c and options like that.. but when I tried man cc, I did not find any mnaual page for CC.. so now how do...... UNIX for Dummies Questions & Answers
UNIX for Dummies Questions & Answers
footprints(1)						      General Commands Manual						     footprints(1)

footprints - summarize information from compiler footprint records
The command scans the named object files, analyzes the compiler footprint records stored in those files, and generates a summary report. This report is intended for use by HP support and lab engineers to assist in problem diagnosis. The report contains the following information: o Total number of compilation units found. o Earliest and latest compiler timestamp, and the linker timestamp (if available). o Total size of text and data segments. o List of compiler versions used, with number of compilation units compiled with each version. o List of options used, with number of compilation units compiled with each option setting. This list is separated into two groups, with the most interesting options in the first group, followed by all remaining options alphabetized in the second group. The following file types are recognized: o Executable files and shared libraries. The command will attempt to find all dependent, non-system shared libraries and will print a separate report for each shared library. If the or environment variable is set, it will search for dependent libraries in the directories listed in the environ- ment variable (if is set, will be ignored). It will also use the embedded search path in the object file. If a shared library cannot be located, a diagnostic will be printed and execution will continue. o Archive libraries. The command will scan each object file member of the archive. o Relocatable object files. The command will scan the named object files. The command supports SOM and ELF object file formats, 32-bit and 64-bit code, and PA-RISC and Integrity systems. It supports compiler footprints produced by the HP C and C++ compilers. Compilation units produced by other compilers may not be reflected in the summary. Options The command recognizes the following options: Print the version number and quit. Verbose mode: prints detail information about each compilation unit found. Prints warnings for possible compatibility problems. Currently, it prints a warning for any compilation units built for Integrity systems with a C/C++ compiler earlier than Version A.05.50. Warnings are printed to stderr with three asterisks at the beginning of the line.
The following example shows the beginning of a typical summary report: Scanning /usr/bin/ksh ... Compiler footprint summary Number of compilation units: 51 Earliest compiler timestamp: N/A Latest compiler timestamp: N/A Linker timestamp: 15-Jul-2006 13:07 UTC Total size: 425.8K (text) 24.8K (data) version [A.06.11/ANSI C 51] architecture [ipf32 51] -O [01 1] [02 50] PBO [off 51] -g [off 51] debugopt [off 51] +Ointeger_overflow [moderate 51] +Olit [const 51] +eh [off 51] -fpeval [float 51] -inline [1 1] [2 50] -link_type [dynamic 51] -mt [(off) 51] -rodata [cond 51] ... The line shows that all 51 compilation units were compiled with Version A.06.11 of the ANSI C compiler. The line shows that the applica- tion was compiled for Integrity systems (Itanium(R) Product Family) in the 32-bit data model. The line shows that one compilation unit was compiled at the default level of optimization (level 01), and the other 50 were compiled at level 02. According to the line, all 51 were compiled without profile-based optimization. The line shows that no compilation units were compiled with the symbolic debug option. Otherwise, the line would show the number of compi- lation units compiled with various combinations of symbolic debug and higher optimization levels. For on/off options like settings listed in parentheses represent a default setting not overridden by a compiler option. Many of the options in the footprint record do not correspond directly to a command-line compiler switch, or have a different spelling, and are included in this report for use by HP support and lab engineers. See cc(1) for a description of supported command-line switches.
was developed by HP.
cc(1), elfdump(1), odump(1). footprints(1)

Featured Tech Videos