Ken Brown wrote on 15 October 2008 20:48:
> I've just used gcc-4 to (successfully) build emacs 22.3 under both
> cygwin 1.5 and cygwin 1.7. In my first attempt for 1.7, I initially had
> gcc4 installed, but none of the regular gcc packages. The result was
> that the emacs configure script failed to find the X11 headers. I then
> installed gcc-core, etc., and the build succeeded.
>
> I'm not a programmer, and I have no idea what causes headers to be
> found,
What causes headers to be found is the relevant -devel package having been
installed by setup.exe; and what causes /that/ to happen is either your
explicit selection of the package in setup.exe's chooser, or it's being a
dependency of some other package you've chosen to install. Dependencies for
all packages are listed in the "requires:" line of their setup.hint files on
the mirrors, and in setup.ini which is generated from them.
> but this strikes me as a possible problem with the gcc4
> package(s). Or is it intended that users of gcc4 should also have gcc
> installed?
They're certainly intended to be orthogonal. And I don't know what exactly
happened to you, but there's no way on earth that installing Gcc-3 should
cause any X-related headers to be pulled in. Both setup.hints for gcc-core
and gcc4-core pull in w32api, and that's it by the way of headers.
Is it perhaps possible that your initial install failed to completely run
and the second time round setup.exe got the missing bits anyway - only
coincidentally at the same time as you installed gcc-core?
cheers,
DaveK
--
Can't think of a witty .sigline today....
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html
Documentation: http://cygwin.com/docs.html
FAQ: http://cygwin.com/faq/
