Sponsored Content
Full Discussion: gmake on Mac
Top Forums UNIX for Dummies Questions & Answers gmake on Mac Post 302568532 by kalak on Thursday 27th of October 2011 01:43:33 PM
Old 10-27-2011
Quote:
Originally Posted by xbin
Install the XCode package.
XCode installs gmake as just "make". If the script you're running is looking for "gmake" and not "make" then run this at the terminal and the XCode installed GNU make will been seen as gmake via the symlink:
Code:
sudo ln -s /usr/bin/make /usr/bin/gmake

 

9 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. UNIX for Advanced & Expert Users

CPAM_TWW -gmake utilities

Hi CPAM-TWW, We need to know Whether CPAM-TWW ( cross platform application Management) package comes along With HP-UX11i . if so , Please get Which package needs to be triggered during installation ( We are more intrested on TWWgmake and TWWutilites( 3rd party software The Written Word)) ... (0 Replies)
Discussion started by: vasanthan
0 Replies

4. 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

5. Programming

after gmake size of library gets changes

Hello, I have source code of c. When i compiled it using gmake my library gets created on AIX. But without changing the source code, if i try to do gmake each and every time then every time size of created library gets changed. Can anyone tell me why it's happening? Am i missing something in my... (3 Replies)
Discussion started by: mustus
3 Replies

6. 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

7. 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

8. Solaris

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

9. 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
DH_INSTALLYORICK(1)						     Debhelper						       DH_INSTALLYORICK(1)

NAME
dh_installyorick - install Yorick add-on packages SYNOPSIS
dh_installyorick [debhelper options] [-m] [--no-make-install] DESCRIPTION
dh_installyorick is a debhelper program that installs the files of your Yorick add-on at the right place when building a Debian package. For a simple plug-in package, this is mostly done by calling "make DESTDIR=debian/<package> install" and then moving arch-independent files to usr/share. Note that there is no Y_SITE/contrib directory in the Debian packages, its content is merged into YSITE/i. Calling "make ... install" can be disabled by using the "--no-make-install" flag. This is useful in particular for interpreted add-on pack- ages, which do not ship with a standard Yorick Makefile. If the "-m" flag is used (but not the "-n" one), dh_installyorick will also add lines to your package's postinst and postrm scripts to call "update-yorickdoc --auto" if the yorick-doc package is installed. It is necessary to call dh_installdeb after dh_installyorick for this to work. It is usually not necessary with a recent dpkg supporting triggers, so this possibility is kept mostly for easing backports and should be deprecated soon. dh_installyorick will look for a file named debian/<package>.ynstall for additional files to install (see YNSTALL FILE below). The prefix "<package>." can be omitted for the main binary package being built (usally the first one listed in debian/control). For the time being, Y_SITE=Y_HOME=/usr/lib/yorick. Requests to install a file under Y_SITE results in its installation under /usr/share/yorick. dh_installyorick handles the creation of the necessary symbolic links from Y_HOME to /usr/share/yorick. Files that are installed in a directory ending in "/bin" or "/sbin", as well as files that are pointed at by symbolic link in such a direc- tory, are installed with execution permission for everyone. OPTIONS
-m Modify postinst/postrm scripts to add a call to update-yorickdoc. This is needed only if the target dpkg does not support triggers. If both "-m" and "-n" are specified, the scripts are not modified. --no-make-install Do not call "make DESTDIR=debian/<package> install". --infofile= An additional pkg_mngr .info file to install. Additionally, dh_installyorick abides by the following standard debhelper options: -a/--arch, -i/--indep, --mainpackage, -n, --no-act, -N/--no-package, -p/--package, -P/--tmpdir, -s/--same-arch, and -v/--verbose. YNSTALL FILE
Blank lines are ignored, several blank character are counted as one, and line starting with "#" (possibly following one or more blanks) are ignored. Each non-comment, non-blank line should be of the form: file [directory [link]] Where file is the file to install, directory the directory it should be installed in, and link an optional symbolic link pointing on the installed file. file the relative path from the top directory of the package source to the file. If link is not specified, file can contain shell globs and actually denote sevral files. If directory is not specified, it is guessed from the extension of file: .i files are installed in Y_SITE/i, .gs and .gp in Y_SITE/g, .info in Y_SITE/packages/installed, .packinfo, .aliases and .keywords in /usr/share/yorick-doc, and .so in Y_HOME/lib. directory the full path (without leading "/") into which the file should be installed. If the file is to be installed inside Yorick's Y_SITE or Y_HOME directory (which will almost alway be the case), it is possible (and advisable) to not specify the full path, but to write "Y_SITE/" or "Y_HOME" followed by the relative path from there. It is also possible to omit this "Y_SITE/" or "Y_HOME/" prefix if directory starts whith one of: Y_SITE/i, Y_SITE/i0, Y_SITE/i-start, Y_SITE/g, Y_SITE/packages, Y_HOME/bin or Y_HOME/lib. link the full path to a symbolic link that should point to the installed file. The same shortcuts apply as for directory. EXAMPLES
The four following lines in debian/ynstall would be equivalent: somefile.i /usr/share/yorick/i somefile.i Y_SITE/i somefile.i i somefile.i Likewise, the following are equivalent: somefile.i /usr/share/yorick/i0 somefile.i Y_SITE/i0 somefile.i i0 Example with a symlink. Here, somefile.i is a script that is both useful #included from within Yorick or from the command line. Its first line reads "#!/usr/bin/yorick -batch". somefile.i i usr/bin/command_name SEE ALSO
debhelper(7), update-yorickdoc(1), deb-triggers(5) This program is a part of yorick-dev but is made to work with debhelper. Note that only compatibility level 5 has been implemented and tested. This script is not idempotent, dh_clean -k should be executed between any two runs. AUTHORS
Thibaut Paumard <paumard@users.sourceforge.net> 2008-05-15 DH_INSTALLYORICK(1)
All times are GMT -4. The time now is 01:41 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy