This is the mail archive of the cygwin-apps mailing list for the Cygwin 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: GCC4, new package soon?


Yaakov (Cygwin/X) wrote:
> On 14/08/2009 08:13, Dave Korn wrote:
>>    Dunno.  Which "installed .la files" are you referring to?
> 
> Since libtool now treats the GCC libraries (except libgcc) like any
> other libtoolized library, meaning that, e.g. the full path to
> libstdc++.la is included in the $dependency_libs of all C++ dependent
> libtoolized libraries.

  That is soooooo wrong.  Nobody has any business sticking their nose into the
compiler's private directory.  Gah!

>   That means, when you change gcc versions (but
> not releases of the same version), if you don't fix all the existing .la
> files, libtool linking will fail because $dependency_libs will point to
> a nonexistent location for libstdc++.la.  (The same goes for libffi,
> libgfortran, libgomp, etc.)

  If it really /has/ to know, it ought to be doing dependency_lib=`g++-4
--print-file-name=libstdc++.la` or something like that.  Really it should
leave well alone things that are part of the operating environment.  When it
comes to language runtime, all it should want to know is whether or not and
where to add "-lc" or "-lstdc++" or whatever.  Oh well, one more item on the
to-do list.

> However unlike Gentoo, as a binary distro we need to handle the case
> where a package built for 4.3.2 isn't rebuilt for a while and is
> installed *after* a newer GCC.  Perhaps this should be a separate script
> shipped with gcc4 in /usr/sbin which can be called by both gcc4
> postinstalls and by the user as necessary?

  Yeah, I reckon so.  Thanks for the heads-up.

    cheers,
      DaveK


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