[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <CAOPXC2nSvSd3E8sbYuhtRKp7-1+db2iRL1rnUWzJKQkHXuLsNw@mail.gmail.com>
Date: Wed, 31 Jul 2013 10:48:49 +0200
From: Gregor Pintar <grpintar@...il.com>
To: musl@...ts.openwall.com
Subject: Re: musl 0.9.12 released
2013/7/30, idunham@...abit.com <idunham@...abit.com>:
> On Mon, Jul 29, 2013 at 10:14:34PM +0200, Gregor Pintar wrote:
>> 2013/7/29, Szabolcs Nagy <nsz@...t70.net>:
>> > * Gregor Pintar <grpintar@...il.com> [2013-07-29 19:37:19 +0200]:
>> >>
>> >> I have a problem. When I try to compile it, I get this:
>> >>
>> >
>> > are you sure the x86_64 arch is correct?
>> >
>> > seems gcc does not know about x86_64 registers in the asm
>> >
>> > i'd check the target in gcc -v
>>
>> Yes, x86_64 is correct arch. Target is also correct.
>> "as crt1.s" also works. It's probably something wrong with gcc.
>
> Maybe see what happens if you pass a flag that forces binutils to use
> 64-bit mode (--64 is documented in the as man page)?
>
> It looked to me like gcc generated 64-bit code, then invoked as
> in 32-bit mode.
>
> HTH,
> Isaac Dunham
>
I switched distribution yesterday.
I had similar problem when compiling kernel (it wanted gnu/stubs-32.h).
It was definitely something messed up with gcc.
Now it works.
Powered by blists - more mailing lists
Confused about mailing lists and their use?
Read about mailing lists on Wikipedia
and check out these
guidelines on proper formatting of your messages.
