This is my self follow.
In article <[EMAIL PROTECTED]>
[EMAIL PROTECTED] writes:
>>I just committed Binutils 2.11.2. Please let me know if this helps or
>>not.
> Thank you! But there remain a problem about gas+ld. Linking bug.C
>(Message-Id: <[EMAIL PROTECTED]>) results error
It was "asm()"
In article <[EMAIL PROTECTED]>
[EMAIL PROTECTED] writes:
>I just committed Binutils 2.11.2. Please let me know if this helps or
>not.
Thank you! But there remain a problem about gas+ld. Linking bug.C
(Message-Id: <[EMAIL PROTECTED]>) results error
as below:
% c++ bug.C
/tmp/ccN393OH.o: In fun
On 26 Jun, David O'Brien wrote:
> I just committed Binutils 2.11.2. Please let me know if this helps or
> not.
Yes, it fixes the problem at least with lame-3.89.
Thanks,
Alexander.
--
Yes, I've heard of "decaf." What's your point?
http://www.Leidinger.net A
David O'Brien wrote:
> On Wed, Jun 27, 2001 at 02:16:48AM +0900, NAKAMURA Kazushi wrote:
> > Not only nasm, but also gas has same problem. In case of
> > ports/audio/gogo and ports/audio/lame, nasm outputs object which
> > make ld dumps core. While gcc+gas outputs object which can't link
> > by l
On Wed, Jun 27, 2001 at 02:16:48AM +0900, NAKAMURA Kazushi wrote:
> Not only nasm, but also gas has same problem. In case of
> ports/audio/gogo and ports/audio/lame, nasm outputs object which
> make ld dumps core. While gcc+gas outputs object which can't link
> by ld. I think the problem occures
In article <[EMAIL PROTECTED]>
[EMAIL PROTECTED] writes:
>> Oops. I wanted to say: Every software which has a problem with ld
>> dumping core uses nasm (so far). The core dump is a bug in ld, but I
>> didn't know if the condition which triggers the core dump is a problem
>> with nasm, the input of
Nevermind -- let's try binutils-2.11.2. :-)
Thanks David!
--
FUJISHIMA Satsuki
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
At Tue, 26 Jun 2001 07:23:57 -0700,
David O'Brien wrote:
> If someone could provide me with the minal input to nasm which then fed
> to `ld' dumps core, it would really speed up a fix. :-)
I'm not sure when but this problem seems to be fixed in CVS at
sources.redhat.com. I built binutils from sou
On Tue, Jun 26, 2001 at 01:15:17PM +0200, Alexander Leidinger wrote:
> Oops. I wanted to say: Every software which has a problem with ld
> dumping core uses nasm (so far). The core dump is a bug in ld, but I
> didn't know if the condition which triggers the core dump is a problem
> with nasm, the
On 25 Jun, An: [EMAIL PROTECTED] wrote:
>> It seems that there is a bug in the GNU ld(1) in -CURRENT. Currently it can't
>> link SDL library from ports/devel/sdl12 port (confirmed by bento). When I'm
>> replacing /usr/libexec/elf/ld with the corresponding file from my 4.3-STABLE
>> system the pro
On 25 Jun, Maxim Sobolev wrote:
> It seems that there is a bug in the GNU ld(1) in -CURRENT. Currently it can't
> link SDL library from ports/devel/sdl12 port (confirmed by bento). When I'm
> replacing /usr/libexec/elf/ld with the corresponding file from my 4.3-STABLE
> system the problem disappe
I have noticed the same problem when compiling ports/audio/gogo.
It worked fine in 4.3-STABLE
- David
- Original Message -
From: "Maxim Sobolev" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Cc: <[EMAIL PROTECTED]>
Sent: Monday, June 25, 2001 11:26 AM
Subject:
Hi,
It seems that there is a bug in the GNU ld(1) in -CURRENT. Currently it can't
link SDL library from ports/devel/sdl12 port (confirmed by bento). When I'm
replacing /usr/libexec/elf/ld with the corresponding file from my 4.3-STABLE
system the problem disappears. Please check what's wrong or pa
13 matches
Mail list logo
