- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- gmake vs make
Categories
Company
Local Language
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Discussions
Discussions
Discussions
Forums
Forums
Discussions
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Community
Resources
Forums
Blogs
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО03-26-2003 02:59 PM
тАО03-26-2003 02:59 PM
We are running gcc 3.2 and gmake-3.79.1-11.00.depot. The system created a make command instead of a gmake and has no -o option. The person who is running it is using a -o option. Is make the same as gmake? Thank you.
g++ -D_HP_UX -DXERCES_TMPLSINC -DHPUX11 +DAportable +eh +Z -Z +a1 +d -ptr/ecomet
ry/ecomxml/xerces-c-src2_2_0/obj/HPUX/ptrepository -c -I/ecometry/ecomxml/xerces
-c-src2_2_0/include -w -O -DPROJ_XMLPARSER -DPROJ_XMLUTIL -DPROJ_PARSERS -DPR
OJ_SAX4C -DPROJ_SAX2 -DPROJ_DOM -DPROJ_VALIDATORS -DXML_USE_NATIVE_TRANSCODER
-DXML_USE_INMEM_MESSAGELOADER -DXML_USE_PTHREADS
-DXML_USE_NETACCESSOR_SOCKET
-o /ecometry/ecomxml/xerces-c-src2_2_0/obj/HPUX/XMLChar.o XMLChar.cpp
g++: cannot specify -o with -c or -S and multiple compilations
make[1]: *** [XMLChar.o] Error 1
make[1]: Leaving directory `/ecometry/ecomxml/xerces-c-src2_2_0/src/xercesc/util
'
make: *** [Util] Error 2
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО03-26-2003 03:29 PM
тАО03-26-2003 03:29 PM
SolutionGenerally, the right thing will happen if you make sure that configure or the utility that builds the makefiles finds the correct "make" by verifying that both make and gmake are in $PATH.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО03-26-2003 03:42 PM
тАО03-26-2003 03:42 PM
Re: gmake vs make
Thank you for your help.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО03-26-2003 03:51 PM
тАО03-26-2003 03:51 PM
Re: gmake vs make
Thank you for your answer. I was thinking that I had everything resolved but I am even more confused now because I found gmake-3.79.1-11.00.depot but when installed, it installed make instead of gmake. Would make do the same as gmake if I have the correct path? if not, Where can I find gmake? I look under gnu.org and found the same 3.79 version.
Thank you again.
Regarding the error: I am still thinking he is using the wrong options.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО03-27-2003 02:39 AM
тАО03-27-2003 02:39 AM
Re: gmake vs make
Enjoy, have FUN! H.Merijn
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО03-27-2003 05:11 AM
тАО03-27-2003 05:11 AM
Re: gmake vs make
Thank you for your reply.