09-07-2001
Yu can use "smitty" to check to see what
you have installed. You can check for *gnu*
(for gcc and g++) or ibmcxx* (for the IBM C/C++
compiler) and this should list any installed
packages. It is also possible to install gnu
software "manually" (not using SMIT) and in this
case, your best bet is to use "find".
10 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
I have just been made responsible for setting up Apache on our office SCO
box. I have searched the internet, but
haven't found any details that I can make
sense of. I'm unfamiliar with Unix and would appreciate any help members of
the forum have to offer. (1 Reply)
Discussion started by: cstovall
1 Replies
2. UNIX for Advanced & Expert Users
hi all expert, can antone tell me ho to install apache-1.3.20-16.src.rpm into redhat 7.3. I ready try many many time and using many method i still can not install this apache.
Please help me................................... (1 Reply)
Discussion started by: foong
1 Replies
3. Web Development
Is there any cheap hosting service that allow me to compile and install my own apache and php ?
thanks (1 Reply)
Discussion started by: aneuryzma
1 Replies
4. Solaris
I am trying to install apache on a sun server (Solaris 10 x86) but when I execute the compile i have the following error;
configure failed for srclib/apr
Can anybody help with this.
Thanks for the usual help
oh-daa (2 Replies)
Discussion started by: oh-daa
2 Replies
5. UNIX for Dummies Questions & Answers
I want to setup apache tomcat on my linux distribution .
I Have downloaded apache tomcat from below mentioned link.
Administration Web Application:
Apache Tomcat - Apache Tomcat 5 Downloads
The setup was in following format.
apache-tomcat-5.5.29-admin.tar.gz
Below are the command i... (7 Replies)
Discussion started by: pinga123
7 Replies
6. SCO
Hello, I have a problem to run the the Web aplication Cincom Mantis XML on a SCO 6.0 with MP2.
My Tomcat is 4.1.31
The Cincom support tell me tha I need the Apache Tomcat 5.5 and Java JRE 1.4.0
Can I install a linux version into SCO 6.0 system ?
Thank you for your help.
... (1 Reply)
Discussion started by: hrmaldonado
1 Replies
7. UNIX for Dummies Questions & Answers
My current apache has the following listing.
ls
admin bin cgi corefiles htdocs include logs manual openssl
build conf error icons lib man modules
It has httpd.conf inside the conf directory and many .so files... (6 Replies)
Discussion started by: mohtashims
6 Replies
8. Solaris
Ok who wants to play with this server and assist me? I'm super stuck and need to get it up and running. :) (6 Replies)
Discussion started by: Ragingbull
6 Replies
9. Solaris
Hi all,
This is Solaris 10 OS
I received this error
on Server,
-bash-3.00$ /usr/local/apache2/bin/httpd -v
ld.so.1: httpd: fatal: libaprutil-1.so.0: open failed: No such file or directory
Killed
-bash-3.00$
How to resolve this dependencies which are not resolved?
... (0 Replies)
Discussion started by: manalisharmabe
0 Replies
10. Shell Programming and Scripting
Hi,
I need to install php 5.5.30 as an apache (2.4.17) module on Solaris 10.
Please any help is wellcome.
Some aditional info:
/usr/sfw/bin/gcc -v
Reading specs from /usr/sfw/lib/gcc/sparc-sun-solaris2.10/3.4.3/specs
bash-3.2# g++ -v
Reading specs from... (1 Reply)
Discussion started by: lbslbs
1 Replies
LEARN ABOUT DEBIAN
go-build
GO-BUILD(1) General Commands Manual GO-BUILD(1)
NAME
go - tool for managing Go source code
SYNOPSIS
go build [-o output] [ build flags ] [ packages ]
DESCRIPTION
Build compiles the packages named by the import paths, along with their dependencies, but it does not install the results.
If the arguments are a list of .go files, build treats them as a list of source files specifying a single package.
When the command line specifies a single main package, build writes the resulting executable to output. Otherwise build compiles the pack-
ages but discards the results, serving only as a check that the packages can be built.
The -o flag specifies the output file name. If not specified, the name is packagename.a (for a non-main package) or the base name of the
first source file (for a main package).
OPTIONS
The build flags are shared by the build, install, run, and test commands:
-a force rebuilding of packages that are already up-to-date.
-n print the commands but do not run them.
-p n the number of builds that can be run in parallel. The default is the number of CPUs available.
-v print the names of packages as they are compiled.
-work print the name of the temporary work directory and do not delete it when exiting.
-x print the commands.
-compiler name
name of compiler to use, as in runtime.Compiler (gccgo or gc)
-gccgoflags 'arg list'
arguments to pass on each gccgo compiler/linker invocation
-gcflags 'arg list'
arguments to pass on each 5g, 6g, or 8g compiler invocation
-ldflags 'flag list'
arguments to pass on each 5l, 6l, or 8l linker invocation
-tags 'tag list'
a list of build tags to consider satisfied during the build. See the documentation for the go/build package for more information
about build tags.
For more about specifying packages, see go-packages(7).
For more about where packages and binaries are installed, see go-gopath(1).
SEE ALSO
go-install(1), go-get(1), go-clean(1).
AUTHOR
This manual page was written by Michael Stapelberg <stapelberg@debian.org>, for the Debian project (and may be used by others).
2012-05-13 GO-BUILD(1)