Well, how about we don't support *upgrade* to 3.3? For panther this
will be no problem (because nobody's got a GM panther to upgrade yet..
;-)) and neither for Jag because the only people who would have/use 3.3
would be developers who installed the update. For them we could just
require gcc_sel
I'm actually a little confused as to why each *package* needs the gcc:
3.1 | 3.3 flags. Its only important to which version of gcc3 we compile
with, not which code we compile.
Shouldn't fink just keep track of which gcc3 a given package was
compiled with instead of making a duplicate info file f
Hi. After the discussion last week, I agree with you, and don't plan to have
fink invoke gcc_select. In fact, I've put code into fink on CVS which
checks that version of gcc you are running (when it matters, as indicated
by the GCC directive), and if the version is incorrect, advises you to
run g
John Davidorff Pell <[EMAIL PROTECTED]> wrote:
> I'm actually a little confused as to why each *package* needs the gcc:
> 3.1 | 3.3 flags. Its only important to which version of gcc3 we compile
> with, not which code we compile.
> Shouldn't fink just keep track of which gcc3 a given package was
I am very opposed to calling gcc_select ever from within fink, because
it overwrites symlinks in /usr/bin. fink has always had the policy to
not mess w/ anything outside of /sw with notable exceptions (X11R6).
One of the features of gcc is that you can have multiple versions
installed simultane
On Sunday, August 17, 2003, at 06:38 PM, David R. Morrison wrote:
One thing I forgot to say. Even with my new strategy, we need to have
fink
verify that the correct version of gcc has been selected when
compiling is
being done.
The overwhelming opinion on IRC last night was that fink should N
One thing I forgot to say. Even with my new strategy, we need to have fink
verify that the correct version of gcc has been selected when compiling is
being done.
The overwhelming opinion on IRC last night was that fink should NOT reset
your gcc selection. Instead, fink should query the gcc selec
After a discussion on IRC last night, I have a completely different proposal
to make about the gcc 3.3 upgrade.
In the new proposal we make a new distribution, perhaps called 10.2a, which
is for packages running under 10.2 but compiled with gcc 3.3. Peter O'Gorman
and others believe that version
when compiling against then, we will have to guarentee that /sw/lib3.3
is before /sw/lib on the link line or it'll link to the older version.
BTW i'd prefer /sw/lib/3.3 or GCC3.3 in the lib dir.
On Saturday, August 16, 2003, at 10:13 AM, David R. Morrison wrote:
However, let me point out that t
Dear fink developers,
As many of you know, the upgrades from gcc 2.95 to gcc 3.1 and from gcc 3.1
to gcc 3.3 cause trouble for Fink due to the change in ABI for C++ code.
For the gcc 3.1 upgrade, we made a clean break when 10.2 was released and
started using gcc 3.1 at that point. This worked re
10 matches
Mail list logo
