This is the mail archive of the
gcc-patches@gcc.gnu.org
mailing list for the GCC project.
PATCH for g77.exp
- To: egcs-patches at cygnus dot com
- Subject: PATCH for g77.exp
- From: Robert Lipe <robertl at dgii dot com>
- Date: Thu, 18 Jun 1998 11:21:09 -0500
This one sent me down the wrong path. I was just tinkering with EGCS
on a new computer with a beta OS and was playing the traditional "gotta
build EGCS before you can build anything else, but you have to have
a functional everythign else so you can build egcs" game. I spent a
long time looking for errors related to the new installation. I think
instead I just found a case where the recent G77 library renaming change
didn't get propogated down and most people (myself included) just still
happen to have copies of the old libf2c.a laying in the "right" place.
It seemed a little wierd that "libf2c/" contains "libg2c.a"2c.a", but
I confirmed that's the way it is right now...
Dave, Craig, or other G77 wizards, does this change look right to you?
Thu Jun 18 11:17:45 1998 Robert Lipe <robertl@dgii.com>
*lib/g77.exp: Replace search for libf2c.a with search for newly
renamed libg2c.a
Inde: g77.exp
===================================================================
RCS file: /egcs/carton/cvsfiles/egcs/gcc/testsuite/lib/g77.exp,v
retrieving revision 1.2
diff -u -p -r1.2 g77.exp
--- g77.exp 1998/02/09 22:54:34 1.2
+++ g77.exp 1998/06/18 16:12:42
@@ -143,10 +143,10 @@ proc g77_target_compile { source dest ty
}
if ![is_remote host] {
set gccpath "[get_multilibs]"
- set libf2c_dir [lookfor_file ${gccpath} libf2c/libf2c.a]
- if { $libf2c_dir != "" } {
- set libf2c_link_flags "-L[file dirname ${libf2c_dir}]"
- lappend options "additional_flags=${libf2c_link_flags}"
+ set libg2c_dir [lookfor_file ${gccpath} libf2c/libg2c.a]
+ if { $libg2c_dir != "" } {
+ set libg2c_link_flags "-L[file dirname ${libg2c_dir}]"
+ lappend options "additional_flags=${libg2c_link_flags}"
}
}
lappend options "compiler=$G77_UNDER_TEST"