Sponsored Content
Full Discussion: -bloadmap function in aix
Operating Systems AIX -bloadmap function in aix Post 302343118 by homeyjoe on Tuesday 11th of August 2009 04:04:01 PM
Old 08-11-2009
That an option to save a log of the compiling messages and such. You should be able to ignore that for gcc.
 

10 More Discussions You Might Find Interesting

1. AIX

POLL function fails under AIX v5.3

I am having a strange problem with the poll() routine. I compiled a module under AIX 5.2 using the poll routine, it worked fine. When the OS was upgraded to AIX 5.3 the poll routine return an error code. Here is a summary of the code: #define MAX_EVENTS 300 long eventCount;... (0 Replies)
Discussion started by: TahirNazir
0 Replies

2. Shell Programming and Scripting

Passing global variable to a function which is called by another function

Hi , I have three funcions f1, f2 and f3 . f1 calls f2 and f2 calls f3 . I have a global variable "period" which i want to pass to f3 . Can i pass the variable directly in the definition of f3 ? Pls help . sars (4 Replies)
Discussion started by: sars
4 Replies

3. Shell Programming and Scripting

Return a value from called function to the calling function

I have two scripts. script1.sh looks -------------------------------- #!/bin/bash display() { echo "Welcome to Unix" } display ----------------------------- Script2.sh #!/bin/bash sh script1.sh //simply calling script1.sh ------------------------------ (1 Reply)
Discussion started by: mvictorvijayan
1 Replies

4. Shell Programming and Scripting

SHELL SCRIPT Function Calling Another Function Please Help...

This is my function which is creating three variables based on counter & writing these variable to database by calling another function writeRecord but only one record is getting wrote in DB.... Please advise ASAP...:confused: function InsertFtg { FTGSTR="" echo "Saurabh is GREAT $#" let... (2 Replies)
Discussion started by: omkar.sonawane
2 Replies

5. Programming

How to step in one function after the function be executed in gdb?

In gdb, I can call one function with command "call", but how can I step in the function? I don't want to restart the program, but the function had been executed, gdb will execute next statement, and I don't know how to recall the function. (4 Replies)
Discussion started by: 915086731
4 Replies

6. Shell Programming and Scripting

Help to Modify File Name in each function before calling another function.

I have a script which does gunzip, zip and untar. Input to the script is file name and file directory (where file is located) I am reading the input parameters as follows: FILENAME=$1 FILEDIR=$2 I have created 3 functions that are as follows: 1) gunzip file 2) unzip file... (2 Replies)
Discussion started by: pinnacle
2 Replies

7. UNIX Desktop Questions & Answers

AIX how to read the file in function again and again

dear friends I have a wrote a shell script which works like this. 1.) a command is executed and the log is moved in the file. 2.) this file is copied in to the other file. 3.) used a grep command to find a particular word. 4.) if a particular word is there then the script will go to next... (4 Replies)
Discussion started by: aboy212u
4 Replies

8. Shell Programming and Scripting

AIX function example with "shift" command

Hello, I am reading one of the AIX manuals about shell scripting and (AIX 5) and I found this example when introducing to functions: function usage { prog="$1"; shift print -u2 "$prog: usage: $prog $@" exit 1 } This example is meant to be easy but I don't understand what it is... (5 Replies)
Discussion started by: Kibou
5 Replies

9. Shell Programming and Scripting

Will files, creaetd in one function of the same script will be recognized in another function?

Dear All. I have a script, which process files one by one. In the script I have two functions. one sftp files to different server the other from existing file create file with different name. My question is: Will sftp function recognize files names , which are created in another... (1 Reply)
Discussion started by: digioleg54
1 Replies

10. Shell Programming and Scripting

Function - Make your function return an exit status

Hi All, Good Day, seeking for your assistance on how to not perform my 2nd, 3rd,4th etc.. function if my 1st function is in else condition. #Body function1() { if then echo "exist" else echo "not exist" } #if not exist in function1 my all other function will not proceed.... (4 Replies)
Discussion started by: meister29
4 Replies
BLHC(1) 						User Contributed Perl Documentation						   BLHC(1)

NAME
blhc - build log hardening check, checks build logs for missing hardening flags SYNOPSIS
blhc [options] <dpkg-buildpackage build log file>.. DESCRIPTION
blhc is a small tool which checks build logs for missing hardening flags. It's licensed under the GPL 3 or later. It's designed to check build logs generated by Debian's dpkg-buildpackage (or tools using dpkg-buildpackage like pbuilder or the official buildd build logs) to help maintainers detect missing hardening flags in their packages. Only gcc is detected as compiler at the moment. If other compilers support hardening flags as well, please report them. If there's no output, no flags are missing and the build log is fine. OPTIONS
--all Force check for all +all (+pie, +bindnow) hardening flags. By default it's auto detected. --arch architecture Set the specific architecture (e.g. amd64, armel, etc.), automatically disables hardening flags not available on this architecture. Is detected automatically if dpkg-buildpackage is used. --bindnow Force check for all +bindnow hardening flags. By default it's auto detected. --buildd Special mode for buildds when automatically parsing log files. The following changes are in effect: o Print tags instead of normal warnings, see "BUILDD TAGS" for a list of possible tags. o Don't check hardening flags in old log files (if dpkg-dev << 1.16.1 is detected). o Don't require Term::ANSIColor. o Return exit code 0, unless there was a error (-I, -W messages don't count as error). --color Use colored (ANSI) output for warning messages. --ignore-arch arch Ignore build logs from architectures matching arch. arch is a string. Used to prevent false positives. This option can be specified multiple times. --ignore-arch-flag arch:flag Like --ignore-flag, but only ignore flag on arch. --ignore-arch-line arch:line Like --ignore-line, but only ignore line on arch. --ignore-flag flag Don't print an error when the specific flag is missing in a compiler line. flag is a string. Used to prevent false positives. This option can be specified multiple times. --ignore-line regex Ignore lines matching the given Perl regex. regex is automatically anchored at the beginning and end of the line to prevent false negatives. NOTE: Not the input lines are checked, but the lines which are displayed in warnings (which have line continuation resolved). Used to prevent false positives. This option can be specified multiple times. --pie Force check for all +pie hardening flags. By default it's auto detected. -h -? --help Print available options. --version Print version number and license. Auto detection for --pie and --bindnow only works if at least one command uses the required hardening flag (e.g. -fPIE). Then it's required for all other commands as well. EXAMPLES
Normal usage, parse a single log file. blhc path/to/log/file If there's no output, no flags are missing and the build log is fine. Parse multiple log files. The exit code is ORed over all files. blhc path/to/directory/with/log/files/* Don't treat missing "-g" as error: blhc --ignore-flag -g path/to/log/file Don't treat missing "-pie" on kfreebsd-amd64 as error: blhc --ignore-arch-flag kfreebsd-amd64:-pie path/to/log/file Ignore lines consisting exactly of "./script gcc file" which would cause a false positive. blhc --ignore-line './script gcc file' path/to/log/file Ignore lines matching "./script gcc file" somewhere in the line. blhc --ignore-line '.*./script gcc file.*' path/to/log/file Use blhc with pbuilder. pbuilder path/to/package.dsc | tee path/log/file blhc path/to/file || echo flags missing BUILDD TAGS
The following tags are used in --buildd mode. In braces the additional data which is displayed. I-hardening-wrapper-used The package uses hardening-wrapper which intercepts calls to gcc and adds hardening flags. The build log doesn't contain any hardening flags and thus can't be checked by blhc. W-compiler-flags-hidden (summary of hidden lines) Build log contains lines which hide the real compiler flags. For example: CC test-a.c CC test-b.c CC test-c.c LD test Most of the time either "export V=1" or "export verbose=1" in debian/rules fixes builds with hidden compiler flags. Sometimes ".SILENT" in a Makefile must be removed. And as last resort the Makefile must be patched to remove the "@"s hiding the real compiler commands. W-dpkg-buildflags-missing (summary of missing flags) CPPFLAGS, CFLAGS, CXXFLAGS, LDFLAGS missing. I-invalid-cmake-used (version) By default CMake ignores CPPFLAGS thus missing those hardening flags. Debian patched CMake in versions 2.8.7-1 and 2.8.7-2 to respect CPPFLAGS, but this patch was rejected by upstream and later reverted in Debian. Thus those two versions show correct usage of CPPFLAGS even if the package doesn't correctly handle them (for example by passing them to CFLAGS). To prevent false negatives just blacklist those two versions. I-no-compiler-commands No compiler commands were detected. Either the log contains none or they were not correctly detected by blhc (please report the bug in this case). EXIT STATUS
The exit status is a "bit mask", each listed status is ORed when the error condition occurs to get the result. 0 Success. 1 No compiler commands were found. 2 Invalid arguments/options given to blhc. 4 Non verbose build. 8 Missing hardening flags. 16 Hardening wrapper detected, no tests performed. 32 Invalid CMake version used. See I-invalid-cmake-used under "BUILDD TAGS" for a detailed explanation. AUTHOR
Simon Ruderich, <simon@ruderich.org> Thanks to to Bernhard R. Link <brlink@debian.org> and Jaria Alto <jari.aalto@cante.net> for their valuable input and suggestions. COPYRIGHT AND LICENSE
Copyright (C) 2012 by Simon Ruderich This program is free software: you can redistribute it and/or modify it under the terms of the GNU General Public License as published by the Free Software Foundation, either version 3 of the License, or (at your option) any later version. This program is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License for more details. You should have received a copy of the GNU General Public License along with this program. If not, see <http://www.gnu.org/licenses/>. SEE ALSO
hardening-check(1), dpkg-buildflags(1) perl v5.14.2 2012-06-27 BLHC(1)
All times are GMT -4. The time now is 01:49 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy