This is the mail archive of the java-patches@gcc.gnu.org mailing list for the Java project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: patch: use $(CXX_FOR_TARGET) in LIBLINK


Tom Tromey <tromey@redhat.com> writes:
>>>>>> "Andrew" == Andrew Haley <aph@redhat.com> writes:

>>> 2006-12-21  Adam Megacz <megacz@cs.berkeley.edu>
>>> * Makefile.am: use $(CXX_FOR_TARGET) in LIBLINK.
>>> * Makefile.in: regenerate.

> There shouldn't be any difference between CXX and CXX_FOR_TARGET in a
> target library.

Yes, I started to wonder about this too.  I've found that the problem
of $(CXX)="g++" happens only if I force the configury to regenerate
$(target)/libjava/Makefile by doing this:

  rm $(target)/libjava/Makefile
  rm $(target)/libjava/config.cache
  cd $(target)/libjava/; ./config.status --recheck
  cd $(target)/libjava/; ./config.status

Is this inappropriate usage of the autoconfigury?  If so, what is the
approved way to force it to rebuild the Makefile?

In general, I've been having a lot of problems with weird stuff
happening whenever I try to avoid a complete clean rebuild (which
takes too long to reasonably do more than once a day, even on my
2core/2ghz/2gb machine).

  - a



Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]