Re: Cygport big oopsie
On 05/07/2009 20:28, Dave Korn wrote:
>> * bin/cygport.in: Export CC, CXX, and friends.
>> * lib/cmake.cygclass: Use CC, CXX, and LDFLAGS.
These were added, primarily, so that I could easily force gcc4 usage
(with -shared-libgcc and -Wl,--enable-auto-import) for _all_ types of
build systems. I had hoped that we could make gcc4 the default earlier,
but as that was rejected at the time, I maintain a local patch on top of
this which does this for now.
> If you declare CPP or any other such variable in the environment, it
> overrides any auto-detection that the package's configury might implement.
> That means that during a GCC bootstrap, it unconditionally uses "cpp" to
> invoke the preprocessor, when stages 2 and 3 very much want to use the
> previous stage's xgcc driver (along with assorted -nostdinc, -B, -isystem, and
> -E flags), and even stage 1 really needs to use "$(CC) -E".
Sounds like a bug in gcc machinery to me; if boostrapping, the supplied
CC,CPP,... should only be accepted for stage1. Does this affect CC as
well during stages 2/3, or just CPP?
> I don't think it's very safe to declare all this stuff in the environment
> when there are so many potential things that will behave one way or another
> based on a test for either existence or non-emptiness. I think this is
> possibly a case of trying to be too helpful. How about deleting the lot, or
> only declaring them for cmake builds, or ... any other ideas?
The best solution would be to have a stable, preferred-by-alternatives
gcc4 with -shared-libgcc on by default, in which case I can stop
overriding these. (--enable-auto-import is on by default now with the
(Continue reading)
I just checked into Ports SVN a snapshot of my .cygport's and patches for KDE 4.2.4, so now you can see what I've done: http://cygwin-ports.svn.sourceforge.net/viewvc/cygwin-ports/ports/trunk/kde/ As for packaging, I've almost got kdelibs figured out; the rest is nowhere near finished. > It is possible to give related tools a different name on the cygwin > platform. > > In the kde buildsystem the variable KDE4_KCFGC_EXECUTABLE (located in > kdelibs/cmake/modules/FindKDE4Internals.cmake) contains the name of the > config compiler. > > The executable name of the config compiler could be changed in > kdelibs\kdecore\kconfig_compiler\CMakeLists.txt by adding an OUTPUT_NAME > property. That much I was aware of, but it's more than just that: 1) kdelibs/CONFLICTS lists 4 more, and omitted one, which are marked "devel only, doesn't matter [if they collide]". * checkXML: a simple script for invoking `meinproc{,4} --check`. Is this used by either automated build system, or is this only invoked manually? Are meinproc 3 & 4 compatible?
RSS Feed