Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com Date: Sat, 4 Oct 2003 20:26:04 -0400 From: Christopher Faylor To: cygwin AT cygwin DOT com Subject: Re: missing java headers Message-ID: <20031005002604.GC10341@redhat.com> Reply-To: cygwin AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com References: <20030921000411 DOT 86E4632A822 AT redhat DOT com> <3F7E2B7A DOT 2030804 AT kleckner DOT net> <10-1465508400 DOT 20031004190846 AT familiehaase DOT de> <20031004175052 DOT GE31073 AT redhat DOT com> <93-1461217329 DOT 20031004202017 AT familiehaase DOT de> <20031004230521 DOT GA9651 AT redhat DOT com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.1i On Sat, Oct 04, 2003 at 09:16:58PM -0300, Fr?d?ric L. W. Meunier wrote: >On Sat, 4 Oct 2003, Christopher Faylor wrote: > >> On Sat, Oct 04, 2003 at 06:09:15PM -0300, Fr?d?ric L. W. Meunier wrote: >> >On Sat, 4 Oct 2003, Gerrit P. Haase wrote: >> >>>I've repeatedly asked for someone to take over maintainership of gcc. >> >>>If you are producing packages on your web site can I ask you go to all >> >>>of the way and maintain gcc for cygwin? >> >> >> >>I'm thinking about it for a while now. Ok. I'll release a first >> >>tarball the next week, including all frontends and Pascal as previously >> >>advertised. >> > >> >While you're at it, I'd (again) suggest splitting it in various parts. >> >Most people only install C and C++. The rest takes a lot of space, >> >mainly Java and Ada. >> >> Yes, I was going to suggest that, too. > >> This is clearly the right way to do this but it is a lot more >> work. > >Yes, but once you get it set up in the script... > >I don't know how Cygwin handles it (maybe I should download >some source packages - I'll), but the Linux distributions seem >to just split it without recompiling the whole thing various >times with --enable-languages=c++ (you don't need to specify >c), then --enable-languages=c++,java etc. Oh, yes. I wouldn't recompile multiple times. That would take forever. It is already pretty frustrating to make a change to the source tree, recompile, and then find twenty minutes later that something is broken in libjava (one of the last things to compile). If I was doing this, I'd probably write a filter which detected what was being installed by java, libstdc++, etc. and then build tar files based on that. It would be nice to break out the libstdc++ package as well. >An example which works and may help Gerrit (I use the resulting >C and C++ packages) is the 3.3.1 script from Slackware - >http://distro.ibiblio.org/pub/Linux/distributions/slackware/slackware-current/testing/source/gcc-3.3.1/gcc.SlackBuild > >I guess Cygwin doesn't need a separate C++ package. I think it does, really. But, this will probably cause massive confusion for people who'd previously installed. cgf -- 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/