ncurses tic

ncurses tic

[Trevor Woerner]

- crosstool 1.6.1
- sample configuration i686-nptl-linux-gnu

When crosstool configures ncurses tic it does so as follows:

==> Executing: '/home/trevor/devel/crosstool/1.6.1/build/x86/targets/src/ncurses-5.7/configure
--build=x86_64-suse-linux --host=x86_64-build_suse-linux-gnu
--prefix=/usr --without-shared --enable-symlinks
--with-build-cc=x86_64-suse-linux-gcc
--with-build-cpp=x86_64-suse-linux-gcc --with-build-cflags= -pipe
--without-ada'

But I think it should instead be:

--with-build-cc=x86_64-build_suse-linux-gnu-gcc
--with-build-cpp=x86_64-build_suse-linux-gnu-gcc

I can work around this one by creating a symlink in the buildtools
directory shortly after the build starts.

I'm guessing there's a problem with:

<install>/lib/ct-ng-1.6.1/scripts/build/debug/300-gdb.sh

But I'm not sure how it needs to be changed.

Am I doing something unexpected?

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

Re: ncurses tic

[Yann E. MORIN]

Trevor, All,

On Monday 15 March 2010 22:07:00 Trevor Woerner wrote:
> When crosstool configures ncurses tic it does so as follows:
> ==> Executing: '/home/trevor/devel/crosstool/1.6.1/build/x86/targets/src/ncurses-5.7/configure
> --build=x86_64-suse-linux --host=x86_64-build_suse-linux-gnu

In fact, it's doing:
    [...]
    --build=${CT_REAL_BUILD}
    --host=${CT_BUILD}
    [...]

> --prefix=/usr --without-shared --enable-symlinks
> --with-build-cc=x86_64-suse-linux-gcc
> --with-build-cpp=x86_64-suse-linux-gcc --with-build-cflags= -pipe
> --without-ada'

I already have seen some weirdness on the openSuSE machine of a friend of
mine. He was not interested in a native gdb for his target, and I had no
time to investigate. Now is a good time, as someone seems interested in
fixing this! :-)

> But I think it should instead be:
> --with-build-cc=x86_64-build_suse-linux-gnu-gcc
> --with-build-cpp=x86_64-build_suse-linux-gnu-gcc

Not quite sure... build.log, please.

> Am I doing something unexpected?

That sample is just bulding fine for me. I did not want to reproduce the
1.6.0 error, where not all samples were tested, so for 1.6.1 I tested all
samples on my machine (Debian lenny 5.0.4). So if you just recalled that
sample, you did nothing wrong, but there seems to be some issue with how
openSuSe (and SuSE?) configured their tuple... We'll have to fix that,
if you have a little time to investigate. But first, I'd need your
build.log, please.

Regards,
Yann E. MORIN.


-- 
.-----------------.--------------------.------------------.--------------------.
|  Yann E. MORIN  | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +33 662 376 056 | Software  Designer | \ / CAMPAIGN     |  ___               |
| +33 223 225 172 `------------.-------:  X  AGAINST      |  \e/  There is no  |
| http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL    |   v   conspiracy.  |
'------------------------------^-------^------------------^--------------------'



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

Re: ncurses tic

[Yann E. MORIN]

[-- Attachment #1: Type: text/plain, Size: 1568 bytes --]

Trevor, All,

[Sorry, forgot to CC the list...]

On Tuesday 16 March 2010 02:44:20 Trevor Woerner wrote:
> Thank you for being interested in looking into this for me. I've
> attached my build log compressed with xz and would be happy to try out
> whatever you suggest. I would CC the list but I don't think they'd
> want a 500K build log in their inboxes.

Yes, nice! :-)

> On Mon, Mar 15, 2010 at 5:30 PM, Yann E. MORIN
> <yann.morin.1998@anciens.enib.fr> wrote:
> > So if you just recalled that
> > sample, you did nothing wrong, but there seems to be some issue with how
> > openSuSe (and SuSE?) configured their tuple... We'll have to fix that,
> > if you have a little time to investigate. But first, I'd need your
> > build.log, please.
> Well, I did tweak them a *little* bit, but only on the "Paths and misc
> options" page to change some of the locations and increase the log
> verbosity.

Care to test the attached fix, please ?

It may not be the final fix, but I need to know if it works on your system
so I can come up with a proper fix.

Regards,
Yann E. MORIN.

-- 
.-----------------.--------------------.------------------.--------------------.
|  Yann E. MORIN  | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +33 662 376 056 | Software  Designer | \ / CAMPAIGN     |  ___               |
| +33 223 225 172 `------------.-------:  X  AGAINST      |  \e/  There is no  |
| http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL    |   v   conspiracy.  |
'------------------------------^-------^------------------^--------------------'

[-- Attachment #2: ct-ng-1.6.1-fix-building-tic.patch --]
[-- Type: text/x-diff, Size: 786 bytes --]

diff --git a/scripts/build/debug/300-gdb.sh b/scripts/build/debug/300-gdb.sh
--- a/scripts/build/debug/300-gdb.sh
+++ b/scripts/build/debug/300-gdb.sh
@@ -161,7 +161,7 @@
         # tools instead of searching for the native ones...
         CT_DoExecLog ALL                                                    \
         "${CT_SRC_DIR}/ncurses-${CT_DEBUG_GDB_NCURSES_VERSION}/configure"   \
-            --build=${CT_REAL_BUILD}                                        \
+            --build=${CT_BUILD}                                             \
             --host=${CT_BUILD}                                              \
             --prefix=/usr                                                   \
             --without-shared                                                \


[-- Attachment #3: Type: text/plain, Size: 71 bytes --]

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

Re: ncurses tic

[Trevor Woerner]

Thanks Yann,

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.

In the mean time I thought you might be interested in the gcc -v
output on my openSuSE machine:

$ gcc -v
Using built-in specs.
Target: x86_64-suse-linux
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?

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

Re: *** SPAM ***Re: ncurses tic

[Yann E. MORIN]

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...

Regards,
Yann E. MORIN.

-- 
.-----------------.--------------------.------------------.--------------------.
|  Yann E. MORIN  | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +33 662 376 056 | Software  Designer | \ / CAMPAIGN     |  ___               |
| +33 223 225 172 `------------.-------:  X  AGAINST      |  \e/  There is no  |
| http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL    |   v   conspiracy.  |
'------------------------------^-------^------------------^--------------------'



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

Re: ncurses tic

[Trevor Woerner]

On Tue, Mar 16, 2010 at 2:46 PM, Trevor Woerner <twoerner@gmail.com> 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.

That succeeded.

> I've applied your patch and will let you know how that goes.

Your patch on my openSuSE box also worked.

If the tuple is the problem, then building and using my own native gcc
(with a standard tuple) should also fix the problem. I'll try that one
next.

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

Re: ncurses tic

[Trevor Woerner]

On Tue, Mar 16, 2010 at 4:28 PM, Trevor Woerner <twoerner@gmail.com> wrote:
> Your patch on my openSuSE box also worked.

[DEBUG]        ==> Executing:
'/home/trevor/devel/crosstool/1.6.1/build/x86/targets/src/ncurses-5.7/configure
--build=x86_64-build_suse-linux-gnu --host=x86_64-build_suse-linux-gnu
--prefix=/usr --without-shared --enable-symlinks
--with-build-cc=x86_64-suse-linux-gcc
--with-build-cpp=x86_64-suse-linux-gcc --with-build-cflags= -pipe
--without-ada'

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

Re: ncurses tic

[Yann E. MORIN]

Trevor, All,

On Tuesday 16 March 2010 21:28:13 Trevor Woerner wrote:
> On Tue, Mar 16, 2010 at 2:46 PM, Trevor Woerner <twoerner@gmail.com> 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.
> That succeeded.

Hopefully it did! That's the machine I'm using! :-)

> > I've applied your patch and will let you know how that goes.
> Your patch on my openSuSE box also worked.

OK, thank you for the test. I'll devise an evil plan to fix this.
And my evil plan is... (Tada!)... Keep the patch!

> If the tuple is the problem, then building and using my own native gcc
> (with a standard tuple) should also fix the problem.

Yes, that's what should be done. I was too conservative when I did
differentiate --build and --host. tic will _always_ be run on the
build machine, so no need to handle canadian/native/...

Thanks for the reporting and the tests! :-)

Regards,
Yann E. MORIN.

-- 
.-----------------.--------------------.------------------.--------------------.
|  Yann E. MORIN  | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +33 662 376 056 | Software  Designer | \ / CAMPAIGN     |  ___               |
| +33 223 225 172 `------------.-------:  X  AGAINST      |  \e/  There is no  |
| http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL    |   v   conspiracy.  |
'------------------------------^-------^------------------^--------------------'



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

Re: ncurses tic

[Trevor Woerner]

On Tue, Mar 16, 2010 at 6:06 PM, Yann E. MORIN
<yann.morin.1998@anciens.enib.fr> wrote:
> On Tuesday 16 March 2010 21:28:13 Trevor Woerner wrote:
>> If the tuple is the problem, then building and using my own native gcc
>> (with a standard tuple) should also fix the problem.
>
> Yes, that's what should be done.

Just for the sake of completeness, using my own native gcc compiler
(configured with mostly defaults) built the target just fine without
the patch.

Thanks!

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

Re: *** SPAM ***Re: ncurses tic

[Trevor Woerner]

On Fri, Mar 19, 2010 at 9:52 AM, Harold Grovesteen
<h.grovsteen@tx.rr.com> wrote:
> As a user of openSUSE, is this an issue for just i486 targets or all
> targets?

I'm guessing it would be an issue for any target for which you want to
compile gdb.

> What version of openSUSEis using this non-standard tuple?

openSUSE 11.2, x86_64

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

Re: *** SPAM ***Re: ncurses tic

[Harold Grovesteen]

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

Re: *** SPAM ***Re: ncurses tic

[David Dyck]

On Fri, 19 Mar 2010 at 07:09 -0700, twoerner@... wrote:

> 
> On Fri, Mar 19, 2010 at 9:52 AM, Harold Grovesteen
> <h.grovsteen@tx.rr.com> wrote:
>> As a user of openSUSE, is this an issue for just i486 targets or all
>> targets?
>
> I'm guessing it would be an issue for any target for which you want to
> compile gdb.
>
>> What version of openSUSEis using this non-standard tuple?
>
> openSUSE 11.2, x86_64

Also:

# x86_64-suse-linux

  cat /etc/SuSE-release
openSUSE 11.0 (X86-64)
VERSION = 11.0

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