OSDN Git Service
(root)
/
pf3gnuchains
/
gcc-fork.git
/ blobdiff
commit
grep
author
committer
pickaxe
?
search:
re
summary
|
shortlog
|
log
|
commit
|
commitdiff
|
tree
raw
|
inline
| side by side
* Makefile.in (local-distclean): Also remove fastjar.
[pf3gnuchains/gcc-fork.git]
/
libf2c
/
Makefile.in
diff --git
a/libf2c/Makefile.in
b/libf2c/Makefile.in
index
886f7e2
..
9075360
100644
(file)
--- a/
libf2c/Makefile.in
+++ b/
libf2c/Makefile.in
@@
-67,7
+67,12
@@
FLAGS_TO_PASS= \
AR='$(AR)' \
RANLIB='$(RANLIB)' \
PICFLAG='$(PICFLAG)' \
AR='$(AR)' \
RANLIB='$(RANLIB)' \
PICFLAG='$(PICFLAG)' \
- RUNTESTFLAGS='$(RUNTESTFLAGS)'
+ RUNTESTFLAGS='$(RUNTESTFLAGS)' \
+ prefix='$(prefix)' \
+ exec_prefix='$(exec_prefix)' \
+ libdir='$(libdir)' \
+ libsubdir='$(libsubdir)' \
+ tooldir='$(tooldir)'
LIBG2C = libg2c.a
LIBG2C = libg2c.a
@@
-139,18
+144,12
@@
$(LIBG2C): s-libi77 s-libf77 s-libu77 s-libe77
$(AR) $(AR_FLAGS) $(LIBG2C) $$objs
$(RANLIB) $(LIBG2C)
$(AR) $(AR_FLAGS) $(LIBG2C) $$objs
$(RANLIB) $(LIBG2C)
-s-libi77: i77
-
i77:
cd libI77; $(MAKE) $(FLAGS_TO_PASS) all
i77:
cd libI77; $(MAKE) $(FLAGS_TO_PASS) all
-s-libf77: f77
-
f77:
cd libF77; $(MAKE) $(FLAGS_TO_PASS) all
f77:
cd libF77; $(MAKE) $(FLAGS_TO_PASS) all
-s-libu77: u77
-
u77:
cd libU77; $(MAKE) $(FLAGS_TO_PASS) all
u77:
cd libU77; $(MAKE) $(FLAGS_TO_PASS) all
@@
-180,7
+179,7
@@
g2c.h: g2c.hin config.status Makefile
# lines below, since g2c.h isn't necessarily brought up to date.
# mv g2c.h g2c.x
$(SHELL) config.status
# lines below, since g2c.h isn't necessarily brought up to date.
# mv g2c.h g2c.x
$(SHELL) config.status
-# $(srcdir)/../move-if-change g2c.h g2c.x && mv g2c.x g2c.h
+# $(
SHELL) $(
srcdir)/../move-if-change g2c.h g2c.x && mv g2c.x g2c.h
Makefile: Makefile.in config.status
# Autoconf doc uses `./config.status'. Is there a good reason to use $(SHELL)?
Makefile: Makefile.in config.status
# Autoconf doc uses `./config.status'. Is there a good reason to use $(SHELL)?