[prev in list] [next in list] [prev in thread] [next in thread] 

List:       openpkg-dev
Subject:    [OpenPKG #237] [gcc] enabling additional languages
From:       "matt () cis ! ksu ! edu via RT" <openpkg-rt () openpkg ! org>
Date:       2003-08-23 3:44:25
[Download RAW message or body]

Request 237 was acted upon.
_________________________________________________________________________

         URL: https://rt.openpkg.org/id/237
      Ticket: [OpenPKG #237]
     Subject: [gcc] enabling additional languages
  Requestors: matt@cis.ksu.edu
       Queue: openpkg
       Owner: Nobody
      Status: open
 Transaction: Correspondence added by matt@cis.ksu.edu
        Time: Sat Aug 23 05:44:23 2003
________________________________________________________________________

Thanks, Ralf.

On Fri, 2003-08-22 at 04:22, Ralf S. Engelschall via RT wrote:
> Request 237 was acted upon.
> _________________________________________________________________________
> 
>          URL: https://rt.openpkg.org/id/237
>       Ticket: [OpenPKG #237]
>      Subject: [gcc] enabling additional languages
>   Requestors: matt@cis.ksu.edu
>        Queue: openpkg
>        Owner: Nobody
>       Status: open
>  Transaction: Correspondence added by rse
>         Time: Fri Aug 22 11:22:48 2003
> ________________________________________________________________________
> 
> On Mon, Aug 18, 2003, matt@cis.ksu.edu via RT wrote:
> 
> > > > The current gcc package provides a build-time option to selectively
> > > > enable the C++ language, via the following construct:
> > > >
> > > > %if "%{with_cxx}" == "yes"
> > > >     l_enable_languages="${l_enable_languages},c++"
> > > > %endif
> > > >
> > > > I would like to suggest adding a similar build-time option for Fortran
> > > > support. I know that this language is not the most fashionable any more,
> > > > but we at least have several users who would appreciate a Fortran
> > > > compiler.
> > > >
> > > > I imagine this would not affect the stability of the gcc package, since
> > > > the option could/would be disabled by default.
> > > >
> > > > Comments?
> > >
> > > Yes, this certainly can be done as an %option. The same should be done
> > > perhaps for the GCC Java frontend. The problem is just that additional
> > > frontends usually also need additional run-time libraries. The question
> > > is whether these also have to be included or whether we make separate
> > > packages out of them...
> 
> > I have done a trial run with g77 back when GCC 3.2 was the current
> > package. Because the GCC team has chosen to implement the Fortran
> > frontend as a thin wrapper around C library calls, there are not too
> > many extra libraries needed.
> >
> > If memory serves, there was an extra static library (.a) produced, the
> > g77 executable, and perhaps a few include files. All of these were
> > self-contained inside the gcc package.
> 
> Ok, seems to work fine. I've now added support for optional Objective-C,
> Java and Fortran-77 languages, starting with gcc-3.3.1-20030822.
> Details you can see here: http://cvs.openpkg.org/chngview?cn=11794
> Thanks for your feedback.
>                                        Ralf S. Engelschall
>                                        rse@engelschall.com
>                                        www.engelschall.com
> 
> 
> ______________________________________________________________________
> The OpenPKG Project                                    www.openpkg.org
> Bug Database Interface                           www.openpkg.org/bugdb
> Bug Database List                            openpkg-bugdb@openpkg.org
> 


______________________________________________________________________
The OpenPKG Project                                    www.openpkg.org
Developer Communication List                   openpkg-dev@openpkg.org
[prev in list] [next in list] [prev in thread] [next in thread]