public inbox for crossgcc@sourceware.org
 help / color / mirror / Atom feed
From: Harold Grovesteen <h.grovsteen@tx.rr.com>
To: "Yann E. MORIN" <yann.morin.1998@anciens.enib.fr>
Cc: crossgcc@sourceware.org, Trevor Woerner <twoerner@gmail.com>
Subject: Re: *** SPAM ***Re: ncurses tic
Date: Fri, 19 Mar 2010 14:19:00 -0000	[thread overview]
Message-ID: <4BA38875.1080301@tx.rr.com> (raw)
In-Reply-To: <201003162007.31621.yann.morin.1998@anciens.enib.fr>



Yann E. MORIN wrote:

>On Tuesday 16 March 2010 19:46:31 Trevor Woerner wrote:
>  
>
>>I installed Debian 5 into a VirtualBox instance to see how that would
>>go so I'd have something to compare to. That build is still chugging
>>along.
>>I've applied your patch and will let you know how that goes.
>>    
>>
>
>OK, thank you!
>I don't have enough space on my HDD to afford a new VM, unfortunately,
>or I'd install an openSuSE one myself as well...
>
>  
>
>>In the mean time I thought you might be interested in the gcc -v
>>output on my openSuSE machine:
>>    
>>
>
>Haha, that's interesting, indeed!
>
>  
>
>>$ gcc -v
>>Using built-in specs.
>>Target: x86_64-suse-linux
>>    
>>
>          ^^^^^^^^^^^^^^^^^
>Hey, that's not a 'standard' tuple! :-(
>
>  
>
>>Configured with: ../configure --prefix=/usr --infodir=/usr/share/info
>>--mandir=/usr/share/man --libdir=/usr/lib64 --libexecdir=/usr/lib64
>>--enable-languages=c,c++,objc,fortran,obj-c++,java,ada
>>--enable-checking=release --with-gxx-include-dir=/usr/include/c++/4.4
>>--enable-ssp --disable-libssp --with-bugurl=http://bugs.opensuse.org/
>>--with-pkgversion='SUSE Linux' --disable-libgcj --disable-libmudflap
>>--with-slibdir=/lib64 --with-system-zlib --enable-__cxa_atexit
>>--enable-libstdcxx-allocator=new --disable-libstdcxx-pch
>>--enable-version-specific-runtime-libs --program-suffix=-4.4
>>--enable-linux-futex --without-system-libunwind --with-arch-32=i586
>>--with-tune=generic --build=x86_64-suse-linux
>>Thread model: posix
>>gcc version 4.4.1 [gcc-4_4-branch revision 150839] (SUSE Linux)
>>
>>Here's the Debian one, for comparison:
>>
>>Using built-in specs.
>>Target: i486-linux-gnu
>>Configured with: ../src/configure -v --with-pkgversion='Debian
>>4.3.2-1.1' --with-bugurl=file:///usr/share/doc/gcc-4.3/README.Bugs
>>--enable-languages=c,c++,fortran,objc,obj-c++ --prefix=/usr
>>--enable-shared --with-system-zlib --libexecdir=/usr/lib
>>--without-included-gettext --enable-threads=posix --enable-nls
>>--with-gxx-include-dir=/usr/include/c++/4.3 --program-suffix=-4.3
>>--enable-clocale=gnu --enable-libstdcxx-debug --enable-objc-gc
>>--enable-mpfr --enable-targets=all --enable-cld
>>--enable-checking=release --build=i486-linux-gnu --host=i486-linux-gnu
>>--target=i486-linux-gnu
>>Thread model: posix
>>gcc version 4.3.2 (Debian 4.3.2-1.1)
>>
>>Maybe openSuSE's non-standard triplet is causing the grief?
>>    
>>
>
>Well, I guess this is the root cause of all the issues.
>
>It seems we would also have to have 'buildtools' wrapper for that...
>Lemme see...
>
As a user of openSUSE, is this an issue for just i486 targets or all 
targets?
What version of openSUSEis using this non-standard tuple?

Harold Grovesteen

>Regards,
>Yann E. MORIN.
>
>  
>


--
For unsubscribe information see http://sourceware.org/lists.html#faq

  parent reply	other threads:[~2010-03-19 14:19 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-03-15 21:07 Trevor Woerner
2010-03-15 21:30 ` Yann E. MORIN
     [not found]   ` <f415e2731003151844u69efccb7rd737dfcb89491339@mail.gmail.com>
2010-03-16 18:31     ` Yann E. MORIN
2010-03-16 18:46       ` Trevor Woerner
2010-03-16 19:07         ` *** SPAM ***Re: " Yann E. MORIN
     [not found]           ` <4BA381A3.3070704@tx.rr.com>
2010-03-19 14:09             ` Trevor Woerner
2010-03-21  3:43               ` David Dyck
2010-03-19 14:19           ` Harold Grovesteen [this message]
2010-03-16 20:28         ` Trevor Woerner
2010-03-16 20:29           ` Trevor Woerner
2010-03-16 22:07           ` Yann E. MORIN
2010-03-17 19:31             ` Trevor Woerner

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4BA38875.1080301@tx.rr.com \
    --to=h.grovsteen@tx.rr.com \
    --cc=crossgcc@sourceware.org \
    --cc=twoerner@gmail.com \
    --cc=yann.morin.1998@anciens.enib.fr \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).