On 2/18/2012 12:59, Whitequill Riclo wrote:
> xunxun, I'm not bootstrapping because the directions I'm following tell me
> not to boot strap.
> LFS book
> http://www.linuxfromscratch.org/lfs/view/stable/chapter05/gcc-pass2.html.
> You'll note one of the commands is, --disable-bootstrap.
>
Please
On 2/18/2012 14:37, Vincent Torri wrote:
> On Sat, Feb 18, 2012 at 7:08 AM, Vincent Torri
> wrote:
>> On Sat, Feb 18, 2012 at 1:40 AM, JonY wrote:
>>> On 2/18/2012 07:45, Vincent Torri wrote:
hey
i have that code in a header file :
static __forceinline __m128i mul_256_ss
On Sat, Feb 18, 2012 at 7:08 AM, Vincent Torri wrote:
> On Sat, Feb 18, 2012 at 1:40 AM, JonY wrote:
>> On 2/18/2012 07:45, Vincent Torri wrote:
>>> hey
>>>
>>> i have that code in a header file :
>>>
>>> static __forceinline __m128i mul_256_sse3(__m128i a, __m128i c) { *** }
>>>
>>> and gcc (4.7
On Sat, Feb 18, 2012 at 1:40 AM, JonY wrote:
> On 2/18/2012 07:45, Vincent Torri wrote:
>> hey
>>
>> i have that code in a header file :
>>
>> static __forceinline __m128i mul_256_sse3(__m128i a, __m128i c) { *** }
>>
>> and gcc (4.7) complains with the error "error: multiple storage
>> classes in
xunxun, I'm not bootstrapping because the directions I'm following tell me
not to boot strap.
LFS book
http://www.linuxfromscratch.org/lfs/view/stable/chapter05/gcc-pass2.html.
You'll note one of the commands is, --disable-bootstrap.
On Mon, Feb 13, 2012 at 8:02 AM, Whitequill Riclo
wrote:
> I'm
On Sat, Feb 18, 2012 at 8:36 AM, JonY wrote:
> On 2/18/2012 04:52, Kai Tietz wrote:
> > 2012/2/17 KC :
> >>
> >>
> >> On Sat, Feb 18, 2012 at 4:37 AM, Kai Tietz
> wrote:
> >>>
> >>> 2012/2/17 KC :
> Hi,
>
> I install mingw-w64-1.0-bin_x86_64-linux_20110822.tar.bz2 at CentOS
> 6.x.
On 2/18/2012 07:45, Vincent Torri wrote:
> hey
>
> i have that code in a header file :
>
> static __forceinline __m128i mul_256_sse3(__m128i a, __m128i c) { *** }
>
> and gcc (4.7) complains with the error "error: multiple storage
> classes in declaration specifiers"
>
> does someone know why ?
On 2/18/2012 04:52, Kai Tietz wrote:
> 2012/2/17 KC :
>>
>>
>> On Sat, Feb 18, 2012 at 4:37 AM, Kai Tietz wrote:
>>>
>>> 2012/2/17 KC :
Hi,
I install mingw-w64-1.0-bin_x86_64-linux_20110822.tar.bz2 at CentOS 6.x.
I extract the tar file into /xmingw-w64/*
and set /xmingw-w6
hey
i have that code in a header file :
static __forceinline __m128i mul_256_sse3(__m128i a, __m128i c) { *** }
and gcc (4.7) complains with the error "error: multiple storage
classes in declaration specifiers"
does someone know why ?
thank you
Vincent Torri
-
2012/2/17 KC :
>
>
> On Sat, Feb 18, 2012 at 4:37 AM, Kai Tietz wrote:
>>
>> 2012/2/17 KC :
>> > Hi,
>> >
>> > I install mingw-w64-1.0-bin_x86_64-linux_20110822.tar.bz2 at CentOS 6.x.
>> > I extract the tar file into /xmingw-w64/*
>> > and set /xmingw-w64/bin as the first search path of $PATH.
>>
On Sat, Feb 18, 2012 at 4:37 AM, Kai Tietz wrote:
> 2012/2/17 KC :
> > Hi,
> >
> > I install mingw-w64-1.0-bin_x86_64-linux_20110822.tar.bz2 at CentOS 6.x.
> > I extract the tar file into /xmingw-w64/*
> > and set /xmingw-w64/bin as the first search path of $PATH.
> >
> > Now when I compile a sim
2012/2/17 KC :
> Hi,
>
> I install mingw-w64-1.0-bin_x86_64-linux_20110822.tar.bz2 at CentOS 6.x.
> I extract the tar file into /xmingw-w64/*
> and set /xmingw-w64/bin as the first search path of $PATH.
>
> Now when I compile a simple hello.c as below:
>
> $ x86_64-w64-mingw32-gcc hello.c -o hello.
Thanks,
Kai
--
Virtualization & Cloud Management Using Capacity Planning
Cloud computing makes use of virtualization - but cloud computing
also focuses on allowing computing to be delivered as a service.
http://www.accel
Hi,
I install mingw-w64-1.0-bin_x86_64-linux_20110822.tar.bz2 at CentOS 6.x.
I extract the tar file into /xmingw-w64/*
and set /xmingw-w64/bin as the first search path of $PATH.
Now when I compile a simple hello.c as below:
$ x86_64-w64-mingw32-gcc hello.c -o hello.exe
I got error message:
cc1:
2012/2/17 Ruben Van Boxem :
> 2012/2/17 niXman
>>
>> 2012/2/17 niXman :
>> > Hi Ruben!
>> > Thanks for your work.
>> >
>> > For dynamically linking C++11 std::thread, replace this line:
>> >> #if SUPPORTS_WEAK && GTHREAD_USE_WEAK
>> > with this one:
>> >> #if SUPPORTS_WEAK && GTHREAD_USE_WEAK && !
2012/2/17 Kai Tietz :
> 2012/2/17 Ruben Van Boxem :
>> 2012/2/17 niXman
>>>
>>> 2012/2/17 niXman :
>>> > Hi Ruben!
>>> > Thanks for your work.
>>> >
>>> > For dynamically linking C++11 std::thread, replace this line:
>>> >> #if SUPPORTS_WEAK && GTHREAD_USE_WEAK
>>> > with this one:
>>> >> #if SUPP
2012/2/17 niXman :
> 2012/2/17 Ruben Van Boxem :
>> 2012/2/17 niXman
>>>
>>> 2012/2/17 niXman :
>>> > Hi Ruben!
>>> > Thanks for your work.
>>> >
>>> > For dynamically linking C++11 std::thread, replace this line:
>>> >> #if SUPPORTS_WEAK && GTHREAD_USE_WEAK
>>> > with this one:
>>> >> #if SUPPORT
2012/2/17 Ruben Van Boxem :
> 2012/2/17 niXman
>>
>> 2012/2/17 niXman :
>> > Hi Ruben!
>> > Thanks for your work.
>> >
>> > For dynamically linking C++11 std::thread, replace this line:
>> >> #if SUPPORTS_WEAK && GTHREAD_USE_WEAK
>> > with this one:
>> >> #if SUPPORTS_WEAK && GTHREAD_USE_WEAK && !
于 2012/2/18 3:20, Kai Tietz 写道:
> Hmm, interesting. What kind of issue happens here on cygwin. As my
> recent builds of binutils on cygwin were working fine. But well, I
> didn't built native cygwin ones.
>
I didn't try it on cygwin and it seems that I missed the small testcase.
But about weak
2012/2/17 Kai Tietz :
> 2012/2/17 Ruben Van Boxem :
>> 2012/2/17 niXman
>>>
>>> 2012/2/17 niXman :
>>> > Hi Ruben!
>>> > Thanks for your work.
>>> >
>>> > For dynamically linking C++11 std::thread, replace this line:
>>> >> #if SUPPORTS_WEAK && GTHREAD_USE_WEAK
>>> > with this one:
>>> >> #if SUPP
2012/2/17 Ruben Van Boxem :
> 2012/2/17 niXman
>>
>> 2012/2/17 niXman :
>> > Hi Ruben!
>> > Thanks for your work.
>> >
>> > For dynamically linking C++11 std::thread, replace this line:
>> >> #if SUPPORTS_WEAK && GTHREAD_USE_WEAK
>> > with this one:
>> >> #if SUPPORTS_WEAK && GTHREAD_USE_WEAK && !
2012/2/17 niXman
> 2012/2/17 niXman :
> > Hi Ruben!
> > Thanks for your work.
> >
> > For dynamically linking C++11 std::thread, replace this line:
> >> #if SUPPORTS_WEAK && GTHREAD_USE_WEAK
> > with this one:
> >> #if SUPPORTS_WEAK && GTHREAD_USE_WEAK && !defined(__MINGW32__)
>
> in gthr-posix.h
2012/2/17 xunxun :
> 于 2012/2/18 3:08, niXman 写道:
>> Hi Ruben!
>> Thanks for your work.
>>
>> For dynamically linking C++11 std::thread, replace this line:
>>> #if SUPPORTS_WEAK&& GTHREAD_USE_WEAK
>> with this one:
>>> #if SUPPORTS_WEAK&& GTHREAD_USE_WEAK&& !defined(__MINGW32__)
>> In my builds
于 2012/2/18 3:08, niXman 写道:
> Hi Ruben!
> Thanks for your work.
>
> For dynamically linking C++11 std::thread, replace this line:
>> #if SUPPORTS_WEAK&& GTHREAD_USE_WEAK
> with this one:
>> #if SUPPORTS_WEAK&& GTHREAD_USE_WEAK&& !defined(__MINGW32__)
> In my builds dynamic linking is used for a
2012/2/17 niXman :
> Hi Ruben!
> Thanks for your work.
>
> For dynamically linking C++11 std::thread, replace this line:
>> #if SUPPORTS_WEAK && GTHREAD_USE_WEAK
> with this one:
>> #if SUPPORTS_WEAK && GTHREAD_USE_WEAK && !defined(__MINGW32__)
in gthr-posix.h
>
> In my builds dynamic linking is
Hi Ruben!
Thanks for your work.
For dynamically linking C++11 std::thread, replace this line:
> #if SUPPORTS_WEAK && GTHREAD_USE_WEAK
with this one:
> #if SUPPORTS_WEAK && GTHREAD_USE_WEAK && !defined(__MINGW32__)
In my builds dynamic linking is used for a long time.
Possibly, anyone could tell
Hi all,
On request of Kai, I built a new MinGW-w64 toolchain including the latest
trunk 4.7 GCC, and mingw-w64 trunk. A lot of work has gone into both since
last time I sent one of these irritating mails no one reads about toolchain
builds no one ever uses ;-)
Nothing really fresh, except that Cl
On 14.02.12 13:17, Ruben Van Boxem wrote:
> Just FYI, my buildall.sh first builds the linux to Windows
> cross-compilers, which are then used to build the native compilers. As
> an extra, I use the Fedora Mac and Cygwin cross-compilers to build cross
> toolchains from those platforms too.
>
> Your
28 matches
Mail list logo
