Date: Fri, 12 May 2000 12:33:33 -0700 (PDT) From: kensarno@champaign.engr.sgi.com (Ken Sarno) Message-Id: <200005121933.MAA36521@champaign.engr.sgi.com> To: pro64-support@oss.sgi.com Subject: Welcome to pro64-support Sender: owner-pro64-support@oss.sgi.com Precedence: bulk Return-Path: X-Orcpt: rfc822;pro64-support-outgoing I just wanted to take a moment to welcome you to the pro64-support mailing list. We look forward helping you with questions about the Pro64 compilers. Date: Mon, 15 May 2000 13:45:02 -0400 Message-Id: <200005151745.NAA07227@alice.ma.tensilica.com> X-Authentication-Warning: alice.ma.tensilica.com: rutt set sender to rutt@alice.ma.tensilica.com using -f From: John Ruttenberg To: pro64-support@oss.sgi.com Subject: NUE? Reply-to: rutt@tensilica.com Sender: owner-pro64-support@oss.sgi.com Precedence: bulk Return-Path: X-Orcpt: rfc822;pro64-support-outgoing Doesn't seem to be available from the links provided by SGI. The readme provided with the sources says to look at: http://www.software.hp.com/ia64linux But this link seems broken. The web page at http://oss.sgi.com/projects/Pro64/download.html points at: http://www.software.htp.com/ia64linux From: John Ruttenberg MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <14624.20797.472803.368047@alice.ma.tensilica.com> Date: Mon, 15 May 2000 15:34:21 -0400 (EDT) To: pro64-support@oss.sgi.com Subject: gmake in osprey1.0/targia32_ia64_nodebug causes an infinite(?) recursion X-Mailer: VM 6.75 under Emacs 20.5.1 Reply-to: rutt@tensilica.com Sender: owner-pro64-support@oss.sgi.com Precedence: bulk Return-Path: X-Orcpt: rfc822;pro64-support-outgoing Try: cd osprey1.0/targia32_ia64_nodebug gmake clobber I get an infinite recursion of makes that eventually crashes my machine. I get a similar problem with: cd osprey1.0/targia32_ia64_nodebug gmake build -f ../../Make.cross Is anyone else having similar problems? From: John Ruttenberg MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <14624.27876.100729.490943@alice.ma.tensilica.com> Date: Mon, 15 May 2000 17:32:20 -0400 (EDT) To: pro64-support@oss.sgi.com Subject: gmake in osprey1.0/targia32_ia64_nodebug causes an infinite(?) recursion In-Reply-To: <14624.20797.472803.368047@alice.ma.tensilica.com> References: <14624.20797.472803.368047@alice.ma.tensilica.com> X-Mailer: VM 6.75 under Emacs 20.5.1 Reply-to: rutt@tensilica.com Sender: owner-pro64-support@oss.sgi.com Precedence: bulk Return-Path: X-Orcpt: rfc822;pro64-support-outgoing John Ruttenberg: > Try: > > cd osprey1.0/targia32_ia64_nodebug > gmake clobber > > I get an infinite recursion of makes that eventually crashes my machine. > > I get a similar problem with: > > cd osprey1.0/targia32_ia64_nodebug > gmake build -f ../../Make.cross > > Is anyone else having similar problems? I think I have been able to answer my own question. I was having two different problems. The problem with Make.cross is that it assumes that gmake in invoked in the perent directory of osprey1.0. (There might be other problems, but I didn't understand this.) The problem with trying to run gmake in the targia32_ia64 directory is that the Makefiles assume that some subdirectories of osprey1.0/targia32_ia64_nodebug exist that are not in the tarball. In particular: g++3-include libstdc++ libunwind libunwind_gdb dwarfdump elfdump fec_238 medusa are listed as subdirs but are not included in the tarball. Once I removed them from the lists in the Makefile, the build seems to be working. A better solution is to make the loop at the bottom of the Makefiles only visit a subdirectory if it exits. This loop is more forgiving: default clean clobber: @for d in $(SUBDIRS); do \ if [ -d $$d ] ; then \ echo "===> cd $$d; $(MAKE) $@"; \ cd $$d; $(MAKE) $@; cd ..; \ fi; \ done From: mpm@rohi.engr.sgi.com (Michael Murphy) Message-Id: <200005152151.OAA61016@rohi.engr.sgi.com> To: pro64-support@oss.sgi.com, rutt@tensilica.com Subject: Re: gmake in osprey1.0/targia32_ia64_nodebug causes an infinite(?) recursion References: <14624.20797.472803.368047@alice.ma.tensilica.com> Sender: owner-pro64-support@oss.sgi.com Precedence: bulk Return-Path: X-Orcpt: rfc822;pro64-support-outgoing Thanks for figuring out the targia*/Makefile problem. This is a problem with only releasing a subset of our sources. I will check in this fix to the Makefiles. -- Mike Murphy -- mpm@sgi.com -- quote of the day: -- "Love one another and you will be happy. -- It is as simple and as difficult as that." (Michael Leunig) From: John Ruttenberg MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <14625.14195.281993.255558@alice.ma.tensilica.com> Date: Tue, 16 May 2000 07:56:35 -0400 (EDT) To: pro64-support@oss.sgi.com Subject: Need ia32-sgi-linux/bin/f90 to build crayf90 X-Mailer: VM 6.75 under Emacs 20.5.1 Reply-to: rutt@tensilica.com Sender: owner-pro64-support@oss.sgi.com Precedence: bulk Return-Path: X-Orcpt: rfc822;pro64-support-outgoing I get this error when building crayf90: /usr/ia32-sgi-linux/bin/f90 -c -MD ../../../crayf90/fe90/fold.f sh: /usr/ia32-sgi-linux/bin/f90: No such file or directory gmake[2]: *** [fold.o] Error 126 gmake[2]: Leaving directory `/home/rutt/src/sgi/osprey1.0/targia32_ia64_nodebug/crayf90/fe90' gmake[1]: *** [first] Error 2 Not that I really care about crayf90. But how should people build this if they want it? Date: Tue, 16 May 2000 10:41:57 -0700 (PDT) From: mpm@rohi.engr.sgi.com (Michael Murphy) Message-Id: <200005161741.KAA64408@rohi.engr.sgi.com> To: pro64-support@oss.sgi.com, rutt@tensilica.com Subject: Re: Need ia32-sgi-linux/bin/f90 to build crayf90 Cc: georgep@rohi.engr.sgi.com Sender: owner-pro64-support@oss.sgi.com Precedence: bulk Return-Path: X-Orcpt: rfc822;pro64-support-outgoing From: John Ruttenberg I get this error when building crayf90: /usr/ia32-sgi-linux/bin/f90 -c -MD ../../../crayf90/fe90/fold.f sh: /usr/ia32-sgi-linux/bin/f90: No such file or directory gmake[2]: *** [fold.o] Error 126 gmake[2]: Leaving directory `/home/rutt/src/sgi/osprey1.0/targia32_ia64_nodebug/crayf90/fe90' gmake[1]: *** [first] Error 2 Not that I really care about crayf90. But how should people build this if they want it? As the README file says, the mfef90 source doesn't build. One problem is this fold file, and there are also some missing files due to copyright restrictions. We did release a binary mfef90, and hopefully we will soon be able to update the OSS source so that it will build. We felt that it was worth releasing what we have rather than waiting, even if it is not complete. -- Mike Murphy -- mpm@sgi.com -- quote of the day: -- "All men desire peace, -- but very few desire those things that make for peace." (Thomas A. Kempis) Date: Tue, 16 May 2000 13:59:06 -0400 Message-Id: <200005161759.NAA19418@neo.init.com> X-Authentication-Warning: neo.init.com: rshapiro set sender to rshapiro@neo.init.com using -f From: Richard Shapiro To: mpm@rohi.engr.sgi.com CC: pro64-support@oss.sgi.com, rutt@tensilica.com, georgep@rohi.engr.sgi.com In-reply-to: <200005161741.KAA64408@rohi.engr.sgi.com> (mpm@rohi.engr.sgi.com) Subject: Re: Need ia32-sgi-linux/bin/f90 to build crayf90 References: <200005161741.KAA64408@rohi.engr.sgi.com> Sender: owner-pro64-support@oss.sgi.com Precedence: bulk Return-Path: X-Orcpt: rfc822;pro64-support-outgoing Date: Tue, 16 May 2000 10:41:57 -0700 (PDT) From: mpm@rohi.engr.sgi.com (Michael Murphy) Cc: georgep@rohi.engr.sgi.com X-Orcpt: rfc822;pro64-support@oss.sgi.com Sender: owner-pro64-support@oss.sgi.com Precedence: bulk Content-Type: text Content-Length: 1021 From: John Ruttenberg I get this error when building crayf90: /usr/ia32-sgi-linux/bin/f90 -c -MD ../../../crayf90/fe90/fold.f sh: /usr/ia32-sgi-linux/bin/f90: No such file or directory gmake[2]: *** [fold.o] Error 126 gmake[2]: Leaving directory `/home/rutt/src/sgi/osprey1.0/targia32_ia64_nodebug/crayf90/fe90' gmake[1]: *** [first] Error 2 Not that I really care about crayf90. But how should people build this if they want it? As the README file says, the mfef90 source doesn't build. One problem is this fold file, and there are also some missing files due to copyright restrictions. We did release a binary mfef90, and hopefully we will soon be able to update the OSS source so that it will build. We felt that it was worth releasing what we have rather than waiting, even if it is not complete. Getting fold.f to build is a pain in the neck. It needs the f90 compiler (since it's an f90 file). It should probably be translated into C or at least should have a bootstrap version. What files are having copyright problems (just out of curiousity). It might be possible to re-write them, or it mayt be that the copyright notice is out-of-date (as it was for much of the code I re-wrote). Rich Date: Tue, 16 May 2000 13:29:47 -0700 (PDT) From: rat@cchkms.engr.sgi.com (Ross A. Towle) Message-Id: <200005162029.NAA11034@cchkms.engr.sgi.com> To: mpm@rohi.engr.sgi.com, Richard Shapiro Subject: Re: Need ia32-sgi-linux/bin/f90 to build crayf90 Cc: georgep@rohi.engr.sgi.com, rutt@tensilica.com, pro64-support@oss.sgi.com References: <200005161741.KAA64408@rohi.engr.sgi.com> Sender: owner-pro64-support@oss.sgi.com Precedence: bulk Return-Path: X-Orcpt: rfc822;pro64-support-outgoing There are NO files missing from the f90 front end. Mike was thinking about an earlier period where there were files with copyright encumberances. These files turned out to be available with the standard Linux distribution so we deleted them from our source tree. -Ross