gcl-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Gcl-devel] Re: PLT code and Mach-O


From: Vadim V. Zhytnikov
Subject: [Gcl-devel] Re: PLT code and Mach-O
Date: Tue, 09 Mar 2004 22:56:22 +0300
User-agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; ru-RU; rv:1.5) Gecko/20031006

Camm Maguire ?????:
Greetings!

"Vadim V. Zhytnikov" <address@hidden> writes:


Camm Maguire:

Greetings!

<snip>

The last possibility is that we put in some configure magic to skip
the plt stuff on windows and macosx.  I don't like this much, as I
fear that eventually the binutils change will catch up there too.

I was about to propose this as a temporary solution for 2.6.2 release.
The problem sounds too serious to make serious improvements in a hurry.
On the other hand I'd to see 2.6.2 released really soon.
Thank to Camm we now have a fix for Linux - at present the only
system where problem with new binutils shows up.
Further investigation and improvement could be moved to 2.7.X
and if more robust scheme will be found it the we can release
2.6.3.


This is possible, but before deciding, could we briefly pursue 2
questions:

1) Do we know what happens on mingw with binutils .8?  Can we find out
   if not?

Interesting question. It seems that mingw uses some other branch of
binutils.  Take a look at mingw download site.
"Current" binutils - 2.13.90-20030111 and ANSI GCL doesn't compile with it crashing at pcl (see a thread a while ago). But this is different issue since can be cured by (use-fast-links nil). "Candidate" binutils - 2.15.90-20040222(yes, yes, 2.15 not 2.14) - GCL builds well including pcl without (use-fast-links nil).

2) Could you or Mike try to compile that simple little test with 'cos'
   only, let me know if it works, and why not if not?

I don't want to spend a lot of time either, but these should be quick
I'm hoping.  I'd like to have the greatest possible chance of never
having to look back at the 2.6 series.

Take care,


--
     Vadim V. Zhytnikov

      <address@hidden>
     <address@hidden>





reply via email to

[Prev in Thread] Current Thread [Next in Thread]