I have made make install to build cdrtools under solaris 8 i86 and
that issue have faced me down is my profile .


# make install
sh ./conf/cc-config.sh cc incs/Dcc.i386-sunos5
Trying to find cc
Found cc
Creating empty 'incs/Dcc.i386-sunos5'
==> MAKING "install" ON SUBDIRECTORY "SRCROOT/conf"
==> MAKING DIRECTORY "../incs/i386-sunos5-cc/Inull"
==> CONFIGURING RULES "../incs/i386-sunos5-cc/rules.cnf"
creating cache ./config.cache
checking host system type... i386-pc-solaris2.8
checking for Cygwin environment... no
checking for mingw32 environment... no
checking for EMX/OS2 environment... no
checking for executable suffix... configure: error: installation or
configuration problem: compiler cannot create executables.
*** Error code 1
make: Fatal error: Command failed for target
`../incs/i386-sunos5-cc/rules.cnf'
Current working directory /export/home/cdrtools/cdrtools-2.00.3/conf
*** Error code 1
make: Fatal error: Command failed for target `install'
#

/etc/profile:

#ident "@(#)profile 1.18 98/10/03 SMI" /* SVr4.0 1.3 */

# The profile that all logins get before using their own .profile.

trap "" 2 3
export LOGNAME PATH

if [ "$TERM" = "" ]
then
if /bin/i386
then
TERM=sun-color
else
TERM=sun
fi
export TERM
fi

# Login and -su shells get /etc/profile services.
# -rsh is given its environment in its .profile.

case "$0" in
-sh | -ksh | -jsh)

if [ ! -f .hushlogin ]
then
/usr/sbin/quota
# Allow the user to break the Message-Of-The-Day only.
trap "trap '' 2" 2
/bin/cat -s /etc/motd
trap "" 2

/bin/mail -E
case $? in
0)
echo "You have new mail."
;;
2)
echo "You have mail."
;;
esac
fi
esac

umask 022
trap 2 3
#PS1="$PWD>"
#export PS1
PATH=$PATH:/usr/local/bin:/usr/ccs/bin:/export/home/cdrecord_valid/binaries/MZcdrec/reloc/bin
PATH=$PATH:/export/home/cdrecord_valid/binaries/MZcdrec/reloc/include
PATH=$PATH:/export/home/cdrecord_valid/binaries/MZcdrec/reloc/lib
PATH=$PATH:/usr/include/sys
PATH=$PATH:/usr/local/include/c++/3.2.3/backward
PATH=$PATH:/usr/local/include/c++/3.2.3
PATH=$PATH:/usr/lib/lp
export PATH
MANPATH=$MANPATH:/usr/local/man:/export/home/cdrecord_valid/binaries/MZcdrec/reloc/man
export MANPATH
#------These variables are concerned with cdrtools
LC_ALL=C
export LC_ALL
#------These variables are concerned with GCC
CC=gcc
CFLAGS=-l/usr/local/include
CXX=g++
CPPFLAGS=-l/usr/local/include
LDFLAGS="-l/usr/local/lib -R/usr/local/lib"
LD_LIBRARY_PATH=/usr/lib:/usr/local/lib
TMPDIR=/var/tmp
export CC CFLAGS CXX CPPFLAGS TMPDIR LDFLAGS LD_LIBRARY_PATH

In article <b4f59294.0307100310.67dd1657@posting.google.com >,
hpy_azizy@yahoo.com (ehab) writes:
> I have made make install to build cdrtools under solaris 8 i86 and
> that issue have faced me down is my profile .
>
>
> # make install
> sh ./conf/cc-config.sh cc incs/Dcc.i386-sunos5
> Trying to find cc
> Found cc

Remove /usr/ucb from your PATH. cc is shell script not a C compiler.

> checking for executable suffix... configure: error: installation or
> configuration problem: compiler cannot create executables.

Duh

> /etc/profile:

Leave /etc/profile alone. Youe PATH statements below boder on the idiotic!

> #ident "@(#)profile 1.18 98/10/03 SMI" /* SVr4.0 1.3 */
>
> # The profile that all logins get before using their own .profile.
>
> trap "" 2 3
> export LOGNAME PATH
>
> if [ "$TERM" = "" ]
> then
> if /bin/i386
> then
> TERM=sun-color
> else
> TERM=sun
> fi
> export TERM
> fi
>
> # Login and -su shells get /etc/profile services.
> # -rsh is given its environment in its .profile.
>
> case "$0" in
> -sh | -ksh | -jsh)
>
> if [ ! -f .hushlogin ]
> then
> /usr/sbin/quota
> # Allow the user to break the Message-Of-The-Day only.
> trap "trap '' 2" 2
> /bin/cat -s /etc/motd
> trap "" 2
>
> /bin/mail -E
> case $? in
> 0)
> echo "You have new mail."
> ;;
> 2)
> echo "You have mail."
> ;;
> esac
> fi
> esac
>
> umask 022
> trap 2 3

OK to here

> #PS1="$PWD>"
> #export PS1
> PATH=$PATH:/usr/local/bin:/usr/ccs/bin:/export/home/cdrecord_valid/binaries/MZcdrec/reloc/bin
> PATH=$PATH:/export/home/cdrecord_valid/binaries/MZcdrec/reloc/include
> PATH=$PATH:/export/home/cdrecord_valid/binaries/MZcdrec/reloc/lib
> PATH=$PATH:/usr/include/sys
> PATH=$PATH:/usr/local/include/c++/3.2.3/backward
> PATH=$PATH:/usr/local/include/c++/3.2.3
> PATH=$PATH:/usr/lib/lp
> export PATH

This is mostly garbage

> MANPATH=$MANPATH:/usr/local/man:/export/home/cdrecord_valid/binaries/MZcdrec/reloc/man
> export MANPATH
> #------These variables are concerned with cdrtools
> LC_ALL=C
> export LC_ALL
> #------These variables are concerned with GCC
> CC=gcc
> CFLAGS=-l/usr/local/include
> CXX=g++
> CPPFLAGS=-l/usr/local/include
> LDFLAGS="-l/usr/local/lib -R/usr/local/lib"
> LD_LIBRARY_PATH=/usr/lib:/usr/local/lib
> TMPDIR=/var/tmp
> export CC CFLAGS CXX CPPFLAGS TMPDIR LDFLAGS LD_LIBRARY_PATH

More rubbish. Get rid of it. To get cdrtools to compile all you need
to do is unpack the source, cd to the source tree and run:

(PATH=/usr/local/bin:/usr/bin:/usr/ccs/bin make)

to install you need to be root. run:
(PATH=/usr/local/bin:/usr/bin:/usr/ccs/bin make install)

Also if you MUST destroy your profile at least make it local by
creating .profile in the root directory on a per user basis as in:
/.profile for the root account. Leave /etc/profile as is.

In article <b4f59294.0307100310.67dd1657@posting.google.com >,
ehab <hpy_azizy@yahoo.com> wrote:
>I have made make install to build cdrtools under solaris 8 i86 and
>that issue have faced me down is my profile .
>
>
># make install
>sh ./conf/cc-config.sh cc incs/Dcc.i386-sunos5
>Trying to find cc
>Found cc
>Creating empty 'incs/Dcc.i386-sunos5'
> ==> MAKING "install" ON SUBDIRECTORY "SRCROOT/conf"
> ==> MAKING DIRECTORY "../incs/i386-sunos5-cc/Inull"
> ==> CONFIGURING RULES "../incs/i386-sunos5-cc/rules.cnf"
>creating cache ./config.cache
>checking host system type... i386-pc-solaris2.8
>checking for Cygwin environment... no
>checking for mingw32 environment... no
>checking for EMX/OS2 environment... no
>checking for executable suffix... configure: error: installation or
>configuration problem: compiler cannot create executables.
>*** Error code 1
>make: Fatal error: Command failed for target
>`../incs/i386-sunos5-cc/rules.cnf'
>Current working directory /export/home/cdrtools/cdrtools-2.00.3/conf
>*** Error code 1

You have a hosed shell environment and use an outdated version of cdrtools

http://www.fokus.fhg.de/research/cc/.../problems.html

--
EMail:joerg@schily.isdn.cs.tu-berlin.de (home) Jörg Schilling D-13353 Berlin
js@cs.tu-berlin.de (uni) If you don't have iso-8859-1
schilling@fokus.fraunhofer.de (work) chars I am J"org Schilling
URL: http://www.fokus.fraunhofer.de/usr/schilling ftp://ftp.berlios.de/pub/schily

In article <jIfPa.2348$Fy1.104881@localhost>, <gerryt@gtconnect.net> wrote:
>In article <b4f59294.0307100310.67dd1657@posting.google.com >,
> hpy_azizy@yahoo.com (ehab) writes:
>> I have made make install to build cdrtools under solaris 8 i86 and
>> that issue have faced me down is my profile .
>>
>>
>> # make install
>> sh ./conf/cc-config.sh cc incs/Dcc.i386-sunos5
>> Trying to find cc
>> Found cc
>
>Remove /usr/ucb from your PATH. cc is shell script not a C compiler.


A well known fact for more than 10 years is that "thou should not have /usr/ucb
in your PATH" if you like to compile.

Recent cdrtools version (starting on May 30th) will even auto-detect that
/usr/ucb/cc is not a working C-compiler.

Bad things may happen if people try to use outdated versions of cdrtools.

http://www.fokus.fhg.de/research/cc/.../problems.html

--
EMail:joerg@schily.isdn.cs.tu-berlin.de (home) Jörg Schilling D-13353 Berlin
js@cs.tu-berlin.de (uni) If you don't have iso-8859-1
schilling@fokus.fraunhofer.de (work) chars I am J"org Schilling
URL: http://www.fokus.fraunhofer.de/usr/schilling ftp://ftp.berlios.de/pub/schily

In article <bekcp3$aa4$1@news.cs.tu-berlin.de>,
Joerg Schilling <js@cs.tu-berlin.de> wrote:
[...]
>A well known fact for more than 10 years is that "thou should not have /usr/ucb
>in your PATH" if you like to compile.

You shouldn't have /usr/ucb on your PATH even if you never compile ...

Chris Thompson
Email: cet1 [at] cam.ac.uk

[newsgroup list trimmed to comp.unix.solaris,comp.sys.sun.admin]

cet1@cus.cam.ac.uk (Chris Thompson) writes:

> In article <bekcp3$aa4$1@news.cs.tu-berlin.de>,
> Joerg Schilling <js@cs.tu-berlin.de> wrote:
> [...]
> >A well known fact for more than 10 years is that "thou should not have /usr/ucb
> >in your PATH" if you like to compile.
>
> You shouldn't have /usr/ucb on your PATH even if you never compile ...
>
> Chris Thompson
> Email: cet1 [at] cam.ac.uk

Why does it still exist then? I know that it is for UCB compatibility but
it has been a while since Solaris in not UCB any more so even backward
compatibility is not a good reason anymore.

In other words, except for maybe /usr/ucb/ps, is there any other program in
/usr/ucb that is essential and that justifies the existence of /usr/ucb?

Can we have RFE for Solaris for /usr/ucb removal :-) ?

Bye, Dragan

--
Dragan Cvetkovic,

To be or not to be is true. G. Boole No it isn't. L. E. J. Brouwer

In comp.unix.solaris Dragan Cvetkovic <d1r2a3g4a5n.NOSPAM@spam.t6h7t.net> wrote:
> In other words, except for maybe /usr/ucb/ps, is there any other program in
> /usr/ucb that is essential and that justifies the existence of /usr/ucb?

I still have users which prefer using lpr/lpq (no idea why, especially
as lpr doesn't support -o like lp for printer specific optiosn). While
lpr/lpq are only links in /usr/ucb to /usr/bin/lp and /usr/bin/lpstat,
removing /usr/ucb from the PATH would make them disappear.

Some applications still come with "lpr" configured as the default
printing command under Solaris (can't remember one off-hand, but
I think mozilla was/is one of them).

> Can we have RFE for Solaris for /usr/ucb removal :-) ?

I guess links in /usr/bin from lp->lpr and lpstat->lpq would be a good
idea before removing /usr/ucb.

mp.
--
Martin Paul | Systems Administrator
Institute for Software Science | martin@par.univie.ac.at
University of Vienna, Austria | http://www.par.univie.ac.at/

hpy_azizy@yahoo.com (ehab) writes:

> I have made make install to build cdrtools under solaris 8 i86 and
> that issue have faced me down is my profile .

> # make install

....

> checking for executable suffix... configure: error: installation or
> configuration problem: compiler cannot create executables.
> *** Error code 1


> PATH=$PATH:/usr/local/bin:/usr/ccs/bin:/export/home/cdrecord_valid/binaries/MZcdrec/reloc/bin
> PATH=$PATH:/export/home/cdrecord_valid/binaries/MZcdrec/reloc/include
> PATH=$PATH:/export/home/cdrecord_valid/binaries/MZcdrec/reloc/lib
> PATH=$PATH:/usr/include/sys
> PATH=$PATH:/usr/local/include/c++/3.2.3/backward
> PATH=$PATH:/usr/local/include/c++/3.2.3
> PATH=$PATH:/usr/lib/lp
> export PATH

There are several directories with include headers in your PATH, why?

> #------These variables are concerned with GCC
> CC=gcc
> CFLAGS=-l/usr/local/include
> CXX=g++
> CPPFLAGS=-l/usr/local/include

The -l option (in your CFLAGS/CPPFLAGS) tells the linker to link in a
shared or static library.

"-l/usr/local/include" expands to "lib/usr/local/include.a" !!

You probably meant "-I/usr/local/include" (uppercase letter 'i') here...

> LDFLAGS="-l/usr/local/lib -R/usr/local/lib"

Another bogus "-l" option. This one should be "-L/usr/local/lib"


It does not supprise me that cdrtools is unable to create executables,
with all these bogus "-l" options in your environment.

Martin Paul <martin@par.univie.ac.at> writes:

> In comp.unix.solaris Dragan Cvetkovic <d1r2a3g4a5n.NOSPAM@spam.t6h7t.net> wrote:
> > In other words, except for maybe /usr/ucb/ps, is there any other program in
> > /usr/ucb that is essential and that justifies the existence of /usr/ucb?
>
> I still have users which prefer using lpr/lpq (no idea why, especially
> as lpr doesn't support -o like lp for printer specific optiosn). While
> lpr/lpq are only links in /usr/ucb to /usr/bin/lp and /usr/bin/lpstat,
> removing /usr/ucb from the PATH would make them disappear.

Link from /usr/bin/lp to /usr/bin/lpr should work as well. In my case, I am
using link from /usr/bin/lp to $HOME/bin/lpr and it works just fine.


Bye, Dragan

--
Dragan Cvetkovic,

To be or not to be is true. G. Boole No it isn't. L. E. J. Brouwer

Joerg Schilling wrote:

> Bad things may happen if people try to use outdated versions of cdrtools.

Well ... where are they getting them from then?

-am © 2003