On Fri, Dec 12, 2008 at 12:01:07PM -0800, Mike Stump wrote:
> On Dec 10, 2008, at 3:24 PM, IainS wrote:
>> if one did -lgcc_s.10.x -lgcc_s.1 would that break it?
>> ... should it not pick up only the unresolved symbols from s.1
>
> I think this is the best long term solution. Things that can be
On Dec 10, 2008, at 3:24 PM, IainS wrote:
if one did -lgcc_s.10.x -lgcc_s.1 would that break it?
... should it not pick up only the unresolved symbols from s.1
I think this is the best long term solution. Things that can be found
from the system are, those that aren't, come from the newly
Iain,
In a perfect world, the real solution to this would be for
Apple to create a new libgcc_s.10.6.dylib which contained the
missing symbols for the newer FSF gcc releases. However since
Apple won't touch GPLv3, this is impossible since it would
require their adopting the libgcc from gcc 4.3 o
On 11 Dec 2008, at 13:51, Jack Howarth wrote:
On Thu, Dec 11, 2008 at 12:38:11PM +, IainS wrote:
...
I have a hunch that this is, at least partially, the origin of
sporadic
failures in crayptr2 (which has been one of the very few tests
using tls
so far - because all the rest have been
On Thu, Dec 11, 2008 at 12:38:11PM +, IainS wrote:
...
>
> I have a hunch that this is, at least partially, the origin of sporadic
> failures in crayptr2 (which has been one of the very few tests using tls
> so far - because all the rest have been UNSUPPORTED by the fails in dg
> target supp
Gents,
thanks for taking the time to explain stuff - hopefully, in the end,
we'll resolve this.
---
Firstly, issues with my choice of configure options might be
important - but they are not relevant to the underlying problem.
The basic problem is entirely repeatable with default options
On Dec 10, 2008, at 7:03 PM, Jack Howarth wrote:
I am confused. Assuming one builds FSF gcc configured with
--enable-threads, shouldn't that create a libgcc.a for FSF gcc
containing the ___emutls_get_address and ___emutls_get_address
symbols?
No, the people that wrote ___emutls_get_address de
On Wed, Dec 10, 2008 at 11:24:28PM +, IainS wrote:
> Thanks Geoff,
> that's v. useful doc.
>
> On 10 Dec 2008, at 22:36, Geoff Keating wrote:
>
>>
>> On Dec 10, 2008, at 7:32 AM, Jack Howarth wrote:
>>
>>> On Wed, Dec 10, 2008 at 02:55:11PM +, IainS wrote:
>
>
>
>> To use the 'unversioned
On Wed, Dec 10, 2008 at 04:13:45PM -0800, Geoff Keating wrote:
>
> On Dec 10, 2008, at 3:24 PM, IainS wrote:
>
>> Thanks Geoff,
>> that's v. useful doc.
>>
>> On 10 Dec 2008, at 22:36, Geoff Keating wrote:
>>
>>>
>>> On Dec 10, 2008, at 7:32 AM, Jack Howarth wrote:
>>>
On Wed, Dec 10, 2008 at
On Dec 10, 2008, at 3:24 PM, IainS wrote:
Thanks Geoff,
that's v. useful doc.
On 10 Dec 2008, at 22:36, Geoff Keating wrote:
On Dec 10, 2008, at 7:32 AM, Jack Howarth wrote:
On Wed, Dec 10, 2008 at 02:55:11PM +, IainS wrote:
To use the 'unversioned set' implies that you're compili
On Wed, Dec 10, 2008 at 02:36:22PM -0800, Geoff Keating wrote:
>
> On Dec 10, 2008, at 7:32 AM, Jack Howarth wrote:
>
>> On Wed, Dec 10, 2008 at 02:55:11PM +, IainS wrote:
>>>
>>> On 10 Dec 2008, at 14:43, Jack Howarth wrote:
>>>
shipped by Apple with its OS releases. I think what you want
Thanks Geoff,
that's v. useful doc.
On 10 Dec 2008, at 22:36, Geoff Keating wrote:
On Dec 10, 2008, at 7:32 AM, Jack Howarth wrote:
On Wed, Dec 10, 2008 at 02:55:11PM +, IainS wrote:
To use the 'unversioned set' implies that you're compiling for a
version of Mac OS that Apple has n
On Dec 10, 2008, at 7:32 AM, Jack Howarth wrote:
On Wed, Dec 10, 2008 at 02:55:11PM +, IainS wrote:
On 10 Dec 2008, at 14:43, Jack Howarth wrote:
shipped by Apple with its OS releases. I think what you want to do
make sure you are using the FSF libgcc's and not the system ones
while hav
FWIW
clearly, this *can* be done .. the open question is whether it
*should* be done :-)
On 10 Dec 2008, at 19:59, IainS wrote:
perhaps it would be more productive to see
if the testsuite in libgomp can be reworked to handle darwin when
gcc is uninstalled.
the patch below gives the same r
On 10 Dec 2008, at 19:58, Mike Stump wrote:
emulation package, which has nothing to do with eh, right?)
that thought had crossed my mind a few times ;-)
can be found. Another possibility, would be to split out the tls
emulation package from gcc_eh. We avoid gcc_eh, so as to not pull
i
On 10 Dec 2008, at 19:46, Jack Howarth wrote:
Since your objections are entirely related to the testsuite when
FSF has not been installed,
hm. I'm not entirely sure that's the whole case... although that was
the trigger for this chain of investigation.
I'm also wondering what instru
On Dec 10, 2008, at 10:23 AM, IainS wrote:
I wonder what a good long-term solution would be?
You can try something like:
#define
REAL_LIBGCC_SPEC \
"%{static-libgcc|static: -lgcc_eh -
lgcc;\
shared-l
On Wed, Dec 10, 2008 at 07:39:35PM +, IainS wrote:
>
> On 10 Dec 2008, at 19:05, Jack Howarth wrote:
>
>> On Wed, Dec 10, 2008 at 06:23:18PM +, IainS wrote:
>>>
>>> On 10 Dec 2008, at 18:10, Mike Stump wrote:
>>>
On Dec 10, 2008, at 9:43 AM, Jack Howarth wrote:
>> If I now understa
On 10 Dec 2008, at 19:05, Jack Howarth wrote:
On Wed, Dec 10, 2008 at 06:23:18PM +, IainS wrote:
On 10 Dec 2008, at 18:10, Mike Stump wrote:
On Dec 10, 2008, at 9:43 AM, Jack Howarth wrote:
If I now understand correctly, the symbols present in updated
versions of
libgcc that are not in
On Wed, Dec 10, 2008 at 06:23:18PM +, IainS wrote:
>
> On 10 Dec 2008, at 18:10, Mike Stump wrote:
>
>> On Dec 10, 2008, at 9:43 AM, Jack Howarth wrote:
If I now understand correctly, the symbols present in updated
versions of
libgcc that are not in the "stock" system libgcc on
On 10 Dec 2008, at 18:10, Mike Stump wrote:
On Dec 10, 2008, at 9:43 AM, Jack Howarth wrote:
If I now understand correctly, the symbols present in updated
versions of
libgcc that are not in the "stock" system libgcc on darwin - need
to be
mentioned in the stub libraries (ligcc_s.10.{4,5,...
On Dec 10, 2008, at 9:43 AM, Jack Howarth wrote:
If I now understand correctly, the symbols present in updated
versions of
libgcc that are not in the "stock" system libgcc on darwin - need
to be
mentioned in the stub libraries (ligcc_s.10.{4,5,...} ). The
emutls ones
were not present causin
On Wed, Dec 10, 2008 at 02:55:11PM +, IainS wrote:
>
> On 10 Dec 2008, at 14:43, Jack Howarth wrote:
>
>> shipped by Apple with its OS releases. I think what you want to do
>> make sure you are using the FSF libgcc's and not the system ones
>> while having environmental MACOSX_DEPLOYMENT_TARGET
On 10 Dec 2008, at 14:43, Jack Howarth wrote:
shipped by Apple with its OS releases. I think what you want to do
make sure you are using the FSF libgcc's and not the system ones
while having environmental MACOSX_DEPLOYMENT_TARGET unset. The latter
step will cause the unversioned libgcc to be us
On Wed, Dec 10, 2008 at 08:27:50AM +, IainS wrote:
> Hi all,
>
> ref: http://gcc.gnu.org/ml/gcc/2008-12/msg00107.html, PR32765 and
> http://gcc.gnu.org/ml/fortran/2008-12/ msg00118.html
>
> NOTE to gurus: the whole libgcc_eh, libgcc_s.{10.x, 1} thing is quite
> hard to understand.
> I sear
Hi all,
ref: http://gcc.gnu.org/ml/gcc/2008-12/msg00107.html, PR32765 and
http://gcc.gnu.org/ml/fortran/2008-12/ msg00118.html
NOTE to gurus: the whole libgcc_eh, libgcc_s.{10.x, 1} thing is
quite hard to understand.
I searched gcc.pdf, gccint.pdf (0 hits) and the list (not much) ...
a
26 matches
Mail list logo
