Sponsored Content
Full Discussion: Make and gmake issues
Operating Systems Solaris Make and gmake issues Post 302801605 by joeyg on Thursday 2nd of May 2013 09:59:33 AM
Old 05-02-2013
Hard to understand

Wrap your commands & data in CodeTags.
Very difficult to read what is in your message.
 

10 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

gmake

Can somebody tell me about "gmake "utility and its apparent advantage with "Imake" and "Make".??? can somebody send me the URLs where I can get more material on above topics? (1 Reply)
Discussion started by: Abhishek
1 Replies

2. AIX

gmake For AIX 5.3

hello everybody i will be very thankful if someone tells me where i can find the gmake for AIX 5.3 (2 Replies)
Discussion started by: eternalflame
2 Replies

3. Programming

what is the distinguish between gmake and make?

I am working on solaris 9. and use gmake to compile and linke c/c++ program. anybody can tell me the distinguish between gmake and make? :confused: (10 Replies)
Discussion started by: robin.zhu
10 Replies

4. HP-UX

Perl, gmake and make software

Hi, I'm searching website where there is software for HP-UX operating system in free download because I must install Perl, Make and Gmake on HP-UX server. Have you goods URL for me ? Thank you very much! bye Staaan (2 Replies)
Discussion started by: staaan
2 Replies

5. UNIX for Advanced & Expert Users

build - make -gmake: execvp: mcu: Permission denied

Hi All, sorry it was application related.. i am deleting it Thanks & Regards Shihab (0 Replies)
Discussion started by: shihabvk
0 Replies

6. Programming

Two issues in make file, g++, gfortran

Question 1: I have a c++ project that I am trying to re-organize. I am trying to subdivide the src directory to move some src files that seldom are changed to a more out of the way location. The project is a c++ application with a fortran function called from the c. The reorganization went... (9 Replies)
Discussion started by: LMHmedchem
9 Replies

7. Programming

GMAKE error returns - What does that mean ?

I am using xmake which I guess calls gmake which ... whatever. I get an error in my compiling and want to know what the error number means. For example, the message might be "Error 139". Rather then post the exact code fragment and exact output, I want to find the a list of error codes and... (1 Reply)
Discussion started by: intcwrtr
1 Replies

8. UNIX for Dummies Questions & Answers

gmake on Mac

I am using my teminal on Mac to run some files with gmake, (I used unix before,but now I am trying to run it frm my mac) and I get the error message: -bash: gmake: command not found Any idea what the problem might be? Thanks! (10 Replies)
Discussion started by: cosmologist
10 Replies

9. Programming

Make and gmake issues

Hello I am working on a CPP code written for SUN CC 5.5 and make we used make to compile the code then it compilation went smooth now i am using gmake: I have a make file like this WSROOT=.. include $(WSROOT)/etc/wsmkinclude.common all: @for subdir in */Makefile; \ do \... (1 Reply)
Discussion started by: Revathi R
1 Replies

10. UNIX for Dummies Questions & Answers

Gmake

hi with regard that i am new with linux , i don't have any information about GNU make? is it a part of linux or it must be installed in linux separately? thanks in advance for you attention best regard fereshte (1 Reply)
Discussion started by: komijani
1 Replies
IO::Wrap(3)						User Contributed Perl Documentation					       IO::Wrap(3)

NAME
IO::Wrap - wrap raw filehandles in IO::Handle interface SYNOPSIS
use IO::Wrap; ### Do stuff with any kind of filehandle (including a bare globref), or ### any kind of blessed object that responds to a print() message. ### sub do_stuff { my $fh = shift; ### At this point, we have no idea what the user gave us... ### a globref? a FileHandle? a scalar filehandle name? $fh = wraphandle($fh); ### At this point, we know we have an IO::Handle-like object! $fh->print("Hey there!"); ... } DESCRIPTION
Let's say you want to write some code which does I/O, but you don't want to force the caller to provide you with a FileHandle or IO::Handle object. You want them to be able to say: do_stuff(*STDOUT); do_stuff('STDERR'); do_stuff($some_FileHandle_object); do_stuff($some_IO_Handle_object); And even: do_stuff($any_object_with_a_print_method); Sure, one way to do it is to force the caller to use tiehandle(). But that puts the burden on them. Another way to do it is to use IO::Wrap, which provides you with the following functions: wraphandle SCALAR This function will take a single argument, and "wrap" it based on what it seems to be... o A raw scalar filehandle name, like "STDOUT" or "Class::HANDLE". In this case, the filehandle name is wrapped in an IO::Wrap object, which is returned. o A raw filehandle glob, like "*STDOUT". In this case, the filehandle glob is wrapped in an IO::Wrap object, which is returned. o A blessed FileHandle object. In this case, the FileHandle is wrapped in an IO::Wrap object if and only if your FileHandle class does not support the "read()" method. o Any other kind of blessed object, which is assumed to be already conformant to the IO::Handle interface. In this case, you just get back that object. If you get back an IO::Wrap object, it will obey a basic subset of the IO:: interface. That is, the following methods (note: I said methods, not named operators) should work on the thing you get back: close getline getlines print ARGS... read BUFFER,NBYTES seek POS,WHENCE tell NOTES
Clearly, when wrapping a raw external filehandle (like *STDOUT), I didn't want to close the file descriptor when the "wrapper" object is destroyed... since the user might not appreciate that! Hence, there's no DESTROY method in this class. When wrapping a FileHandle object, however, I believe that Perl will invoke the FileHandle::DESTROY when the last reference goes away, so in that case, the filehandle is closed if the wrapped FileHandle really was the last reference to it. WARNINGS
This module does not allow you to wrap filehandle names which are given as strings that lack the package they were opened in. That is, if a user opens FOO in package Foo, they must pass it to you either as "*FOO" or as "Foo::FOO". However, "STDIN" and friends will work just fine. VERSION
$Id: Wrap.pm,v 1.2 2005/02/10 21:21:53 dfs Exp $ AUTHOR
Primary Maintainer David F. Skoll (dfs@roaringpenguin.com). Original Author Eryq (eryq@zeegee.com). President, ZeeGee Software Inc (http://www.zeegee.com). POD ERRORS
Hey! The above document had some coding errors, which are explained below: Around line 212: '=item' outside of any '=over' =over without closing =back perl v5.18.2 2005-02-10 IO::Wrap(3)
All times are GMT -4. The time now is 07:48 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy