egcs, files out of sync between libiberty and gcc directories

Jeffrey A Law law@cygnus.com
Sun May 3 23:02:00 GMT 1998


  In message <199804280200.TAA07537@rtl.cygnus.com>you write:
  > 	Some files are out of sync between egcs/libiberty and egcs/gcc.
  > 	pexecute.c
  > 	getopt.c
  > 	obstack.c
  > 	Is there a desire to keep these files identical across the two
  > directories?
  > 
  > It would be desirable if they were the same.
  > 
  > Differences can occur because of merging.  The gcc versions of the files get
  > changes merged in from the gcc2 source tree, and the libiberty versions get
  > changes merged in from the Cygnus (i.e. gas/gdb/etc) source tree (assuming
  > such merging is taking place, I am not sure if it is).  I don't think there
  > is any procedure in place yet to resolve such merge differences.
Right.  There's really no procedures in place to keep those files
in sync right now.

  > Ideally, there should be only one file, in libiberty, but who knows when
  > that will happen.
Yup.  This is precisely why I think we need to take the dive and have
gcc link against libiberty.

The first step would be relatively easy -- just link stuff that runs
on the host against libiberty.  Then figure out what to do about
the gen* stuff for the build machine.

jeff




More information about the Gcc-bugs mailing list