Closed p5pRT closed 16 years ago
Please find below the output from Configure which fails to complete on my Tru64 4.0f Unix workstation. I've been building and running Perl for years with no such problems. I'm currently running Perl 5.8.7 which configured and built just fine. Thanks for your help.
# sh Configure -de
Beginning of configuration questions for perl5.
Checking echo to see how to suppress newlines... ...using \c The star should be here-->*
First let's make sure your kit is complete. Checking... Looks good...
Would you like to see the instructions? [n]
Locating common programs... awk is in /usr/bin/awk. cat is in /sbin/cat. chmod is in /sbin/chmod. comm is in /usr/bin/comm. cp is in /sbin/cp. echo is in /usr/bin/echo. expr is in /sbin/expr. grep is in /sbin/grep. ls is in /sbin/ls. mkdir is in /sbin/mkdir. rm is in /sbin/rm. sed is in /usr/bin/sed. sort is in /sbin/sort. touch is in /usr/bin/touch. tr is in /usr/bin/tr. uniq is in /usr/bin/uniq.
Don't worry if any of the following aren't found... I don't see Mcc out there\, offhand. ar is in /usr/bin/ar. I don't see bison out there\, either. I don't see byacc out there\, either. cpp is in /usr/bin/cpp. csh is in /usr/bin/csh. date is in /sbin/date. egrep is in /usr/bin/egrep. I don't see gmake out there\, either. gzip is in /usr/bin/gzip. I don't see less out there\, either. ln is in /sbin/ln. make is in /sbin/make. more is in /usr/bin/more. nm is in /usr/bin/nm. nroff is in /usr/bin/nroff. pg is in /usr/bin/pg. test is in /usr/bin/test. uname is in /usr/bin/uname. I don't see zip out there\, either. Using the test built into your sh.
Checking compatibility between /usr/bin/echo and builtin echo (if any)... They are compatible. In fact\, they may be identical.
Symbolic links are supported.
Checking how to test for symbolic links... You can test for symbolic links with 'test -h'.
Good\, your tr supports [:lower:] and [:upper:] to convert case. Using [:upper:] and [:lower:] to convert case.
First time through\, eh? I have some defaults handy for some systems that need some extra help getting the Configure answers right:
3b1 dos_djgpp irix_6_0 nonstopux sunos_4_0 aix dynix irix_6_1 openbsd sunos_4_1 aix_3 dynixptx isc opus super-ux
aix_4 epix isc_2 os2 svr4 altos486 esix4 linux os390 svr5 amigaos fps lynxos os400 ti1500
apollo freebsd machten posix-bc titanos
atheos genix machten_2 powerux ultrix_4
aux_3 gnu mint qnx umips beos gnukfreebsd mips rhapsody unicos
bsdos gnuknetbsd mpc sco unicosmk
convexos greenhills mpeix sco_2_3_0 unisysdynix cxux hpux ncr_tower sco_2_3_1 utekv cygwin i386 netbsd sco_2_3_2 uts darwin interix newsos4 sco_2_3_3 uwin dcosx irix_4 next_3 sco_2_3_4 vmesa dec_osf irix_5 next_3_0 solaris_2 vos dgux irix_6 next_4 stellar
You may give one or more space-separated answers\, or "none" if appropriate. A well-behaved OS will have no hints\, so answering "none" or just "Policy" is a good thing. DO NOT give a wrong version or a wrong OS.
Which of these apply\, if any? [dec_osf] Appending /usr/local/lib to LD_LIBRARY_PATH. LD_LIBRARY_PATH is now /usr/local/lib:/usr/local/lib.
Configure uses the operating system name and version to set some defaults. The default value is probably right if the name rings a bell. Otherwise\, since spelling matters for me\, either accept the default or answer "none" to leave it blank.
Operating system name? [dec_osf]
Operating system version? [4.0f]
Perl can be built to use the SOCKS proxy protocol library. To do so\, Configure must be run with -Dusesocks. If you use SOCKS you also need to use the PerlIO abstraction layer\, this will be implicitly selected.
If this doesn't make any sense to you\, just accept the default 'n'. Build Perl for SOCKS? [n]
Previous version of perl5 used the standard IO mechanisms as defined in \<stdio.h>. Versions 5.003_02 and later of perl5 allow alternate IO mechanisms via the PerlIO abstraction layer\, but the stdio mechanism is still available if needed. The abstraction layer can use AT&T's sfio (if you already have sfio installed) or regular stdio. Using PerlIO with sfio may cause problems with some extension modules.
If this doesn't make any sense to you\, just accept the default 'y'. Use the PerlIO abstraction layer? [y]
Perl can be built to take advantage of threads on some systems. To do so\, Configure can be run with -Dusethreads.
Note that Perl built with threading support runs slightly slower and uses more memory than plain Perl. The current implementation is believed to be stable\, but it is fairly new\, and so should be treated with caution.
If this doesn't make any sense to you\, just accept the default 'n'. Build a threading Perl? [n] Your platform has some specific hints regarding threaded builds\, using them...
Perl can be built so that multiple Perl interpreters can coexist within the same Perl executable.
If this doesn't make any sense to you\, just accept the default 'n'. Build Perl for multiplicity? [n]
Hmm... Looks kind of like an OSF/1 system\, but we'll see...
Congratulations. You aren't running Eunice.
It's not Xenix...
Nor is it Venix... Use which C compiler? [cc] ld: -no_ansi_alias: Unknown flag ld: Usage: ld [options] file [...] Uh-oh\, the C compiler 'cc' doesn't seem to be working. Configure: gcc: not found ld: -no_ansi_alias: Unknown flag ld: Usage: ld [options] file [...] Uh-oh\, the C compiler 'cc' doesn't seem to be working. You need to find a working C compiler. Either (purchase and) install the C compiler supplied by your OS vendor\, or for a free C compiler try http://gcc.gnu.org/ I cannot continue any further\, aborting. #
Scott McAskill
\(Embedded image moved to file​: pic12382\.gif\)
Senior Systems Analyst
Computer Sciences Corporation
Contractor to the USEPA
voice​: 401 782\-3152
email​: mcaskill\.scott@​epa\.gov
"The journey of a thousand miles sometimes ends very\, very badly."
On Tue\, 16 May 2006\, mcaskill . scott @ epamail . epa . gov wrote:
# New Ticket Created by mcaskill.scott@epamail.epa.gov # Please include the string: [perl #39149] # in the subject line of all future correspondence about this issue. # \<URL: https://rt-archive.perl.org/perl5/Ticket/Display.html?id=39149 >
Please find below the output from Configure which fails to complete on my Tru64 4.0f Unix workstation. I've been building and running Perl for years with no such problems. I'm currently running Perl 5.8.7 which configured and built just fine. Thanks for your help.
[I assume you mean you've been building and running Perl *on this system*]
Use which C compiler? [cc] ld: -no_ansi_alias: Unknown flag ld: Usage: ld [options] file [...] Uh-oh\, the C compiler 'cc' doesn't seem to be working.
The perl-5.8.8 hints/dec_osf.sh hint file added the -no_ansi_alias flag to the linker flags. You can read that file for more detail. You should probably just delete that flag in the hint file. For purposes of keeping the hints file up-to-date and accurate\, however\, it would be useful if you could send along the ld version and whatever other information might be useful to identify your particular set-up. (I know virtually nothing about Tru64\, so I don't know specifically what to suggest or test for.)
-- Andy Dougherty doughera@lafayette.edu
The RT System itself - Status changed from 'new' to 'open'
Andy\,
Thanks for replying so promptly. I am indeed running Perl 5.8.7 on the Tru64 Unix 4.0f system. ld shows a version of 3.11 with a compiler version of: DEC C V5.9-011 on Digital UNIX V4.0 (Rev. 1229) Digital UNIX Compiler Driver 3.11
I have another box running Tru64 5.1 that I built 5.8.8 on successfully. ld on that system is version 5.1 with a compiler version of: Compaq C V6.3-029 on Compaq Tru64 UNIX V5.1 (Rev. 732) Compiler Driver V6.3-030 (sys) cc Driver
FYI\, rather than editing the 5.8.8 dec_osf.sh file\, I simply used the version from the perl 5.8.7 source and was able to run "sh Configure -de" OK on the 4.0f system. Tru64 4.0f is rather old\, but because of installed software considerations\, I haven't upgraded the OS.
Scott McAskill
\(Embedded image moved to file​: pic13151\.gif\)
Senior Systems Analyst
Computer Sciences Corporation
Contractor to the USEPA
voice​: 401 782\-3152
email​: mcaskill\.scott@​epa\.gov
"The journey of a thousand miles sometimes ends very\, very badly."
Andy Dougherty
via RT
\<perlbug-followu To
p@perl.org> Scott McAskill/NAR/USEPA/US@EPA
cc
05/17/2006 01:26
PM Subject
Re: [perl #39149] Perl 5.8.8
configure failure
Please respond
to
perlbug-followup
@perl.org
On Tue\, 16 May 2006\, mcaskill . scott @ epamail . epa . gov wrote:
# New Ticket Created by mcaskill.scott@epamail.epa.gov # Please include the string: [perl #39149] # in the subject line of all future correspondence about this issue. # \<URL: https://rt-archive.perl.org/perl5/Ticket/Display.html?id=39149 >
Please find below the output from Configure which fails to complete on my Tru64 4.0f Unix workstation. I've been building and running Perl for years with no such problems. I'm currently running Perl 5.8.7 which configured and built just fine. Thanks for your help.
[I assume you mean you've been building and running Perl *on this system*]
Use which C compiler? [cc] ld: -no_ansi_alias: Unknown flag ld: Usage: ld [options] file [...] Uh-oh\, the C compiler 'cc' doesn't seem to be working.
The perl-5.8.8 hints/dec_osf.sh hint file added the -no_ansi_alias flag to the linker flags. You can read that file for more detail. You should probably just delete that flag in the hint file. For purposes of keeping the hints file up-to-date and accurate\, however\, it would be useful if you could send along the ld version and whatever other information might be useful to identify your particular set-up. (I know virtually nothing about Tru64\, so I don't know specifically what to suggest or test for.)
-- Andy Dougherty doughera@lafayette.edu
@smpeters - Status changed from 'open' to 'resolved'
Hi gurus\,
This is my first time to install perl in tru64. Please help.
system version: Digital UNIX V4.0G (Rev. 1530)
lmf list: Product Status Users: Total Active
ASE-OA active unlimited OSF-BASE active unlimited OSF-SVR active unlimited OSF-USR active unlimited OSF-USR active\, multiple unlimited
when I run ./Configure -de (or sh Configure -de or ksh Configure -de)\, throw below suspicious messages and end up aborting:
Which of these apply\, if any? [dec_osf] /usr/lib/cmplrs/cc/ftoc: No such file or directory /usr/lib/cmplrs/cc/cord: No such file or directory Appending /usr/local/lib to LD_LIBRARY_PATH. LD_LIBRARY_PATH is now /usr/local/lib. .......... .......... .......... Congratulations. You aren't running Eunice.
It's not Xenix...
Nor is it Venix... Use which C compiler? [cc] ld: -no_ansi_alias: Unknown flag ld: Usage: ld [options] file [...] Uh-oh\, the C compiler 'cc' doesn't seem to be working. Configure: gcc: not found ld: -no_ansi_alias: Unknown flag ld: Usage: ld [options] file [...] Uh-oh\, the C compiler 'cc' doesn't seem to be working. You need to find a working C compiler. Either (purchase and) install the C compiler supplied by your OS vendo +r\, or for a free C compiler try http://gcc.gnu.org/ I cannot continue any further\, aborting.
It seems there is no CC in the system. But unfortunately\, CC is there and works well!. I can compile a a.out file and print "Hello World!!" to screen.
So I have no any idea to go on. Please point out a right way. any insight are appreciated!.
BTW: below is %ENV\, it might be useful to find out reasons. gxtms#> env TERM=ansi GWSOURCE=telnet HOME=/ SHELL=/bin/csh USER=root LOGNAME=root PATH=/sbin:/usr/sbin:/usr/bin:/usr/bin/X11 SHLVL=1 I18NPATH=/usr/i18n EDITMODE=emacs
below is another warning message if I insert "#include "stdio.h" into C file.
gxtms#> cc x.c cc: Severe: x.c\, line 1: Cannot find file "stdio.h" specified in #include direct ive. (noinclfilef) #include "stdio.h"
@smpeters - Status changed from 'resolved' to 'stalled'
On Mon Oct 22 19:25:14 2007\, xyf.xiao@gmail.com wrote:
Hi gurus\,
This is my first time to install perl in tru64. Please help.
system version: Digital UNIX V4.0G (Rev. 1530)
lmf list: Product Status Users: Total Active
ASE-OA active unlimited OSF-BASE active unlimited OSF-SVR active unlimited OSF-USR active unlimited OSF-USR active\, multiple unlimited
when I run ./Configure -de (or sh Configure -de or ksh Configure -de)\, throw below suspicious messages and end up aborting:
Which of these apply\, if any? [dec_osf] /usr/lib/cmplrs/cc/ftoc: No such file or directory /usr/lib/cmplrs/cc/cord: No such file or directory Appending /usr/local/lib to LD_LIBRARY_PATH. LD_LIBRARY_PATH is now /usr/local/lib. .......... .......... .......... Congratulations. You aren't running Eunice.
It's not Xenix...
Nor is it Venix... Use which C compiler? [cc] ld: -no_ansi_alias: Unknown flag ld: Usage: ld [options] file [...] Uh-oh\, the C compiler 'cc' doesn't seem to be working. Configure: gcc: not found ld: -no_ansi_alias: Unknown flag ld: Usage: ld [options] file [...] Uh-oh\, the C compiler 'cc' doesn't seem to be working. You need to find a working C compiler. Either (purchase and) install the C compiler supplied by your OS vendo +r\, or for a free C compiler try http://gcc.gnu.org/ I cannot continue any further\, aborting.
It seems there is no CC in the system. But unfortunately\, CC is there and works well!. I can compile a a.out file and print "Hello World!!" to screen.
So I have no any idea to go on. Please point out a right way. any insight are appreciated!.
BTW: below is %ENV\, it might be useful to find out reasons. gxtms#> env TERM=ansi GWSOURCE=telnet HOME=/ SHELL=/bin/csh USER=root LOGNAME=root PATH=/sbin:/usr/sbin:/usr/bin:/usr/bin/X11 SHLVL=1 I18NPATH=/usr/i18n EDITMODE=emacs
below is another warning message if I insert "#include "stdio.h" into C file.
gxtms#> cc x.c cc: Severe: x.c\, line 1: Cannot find file "stdio.h" specified in #include direct ive. (noinclfilef) #include "stdio.h"
This problem has been resolved in Perl 5.10.
The RT System itself - Status changed from 'new' to 'open'
@smpeters - Status changed from 'open' to 'resolved'
Migrated from rt.perl.org#46729 (status was 'resolved')
Searchable as RT46729$