Re: locales in buildd environment (http://lists.debian.org/debian-gcc/2003/debian-gcc-200301/msg00060.html)

2003-01-15 Thread Matthias Klose
Junichi Uekawa writes:
> > > To ensure some locales are available, I think you can use LOCPATH,
> > > and create locales locally, so that the following are available:
> > >   de_DE ISO-8859-1
> > >   en_US ISO-8859-1
> > >   fr_FR ISO-8859-1
> > > 
> > > 
> > > see /usr/sbin/locale-gen on how to generate these locale data.
> > 
> > ok, it's no problem to generate the data, but I cannot find any
> > reference to LOCPATH. Any hints?
> 
> I couldn't find any reference to LOCPATH either, but 
> setlocale seems to look at directories specified by LOCPATH
> in addition to (or instead of) the standard location (/usr/lib/locale)

ok, next question is how to write the new definitions to the new
LOCPATH. the outputdir in localedef seems to be hardcoded.




Re: locales in buildd environment (http://lists.debian.org/debian-gcc/2003/debian-gcc-200301/msg00060.html)

2003-01-15 Thread Junichi Uekawa

> > I couldn't find any reference to LOCPATH either, but 
> > setlocale seems to look at directories specified by LOCPATH
> > in addition to (or instead of) the standard location (/usr/lib/locale)
> 
> ok, next question is how to write the new definitions to the new
> LOCPATH. the outputdir in localedef seems to be hardcoded.

The manual page documents:
I18NPATH

In boot-floppies build-process, itseems to be:

mkdir -p $T/usr/lib/locale
localedef -i "utilities/bogl/C-at-utf-8.in" -f "UTF-8" \
"$T/usr/lib/locale/[EMAIL PROTECTED]"


so full-path to output file is the final command-line argument to localedef.


regards,
junichi




Bug#176797: libstdc++5: GDB looks in the wrong place for libstdc++ headers

2003-01-15 Thread Daniel E Baumann
Package: libstdc++5
Version: 1:3.2.2-0pre5
Severity: important

When running my c++ program from inside gdb I get the following:

[EMAIL PROTECTED]:~/software/src/cvs/gsim/src/examples/mm1$ gdb .libs/mm1
GNU gdb 5.3-debian
Copyright 2002 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and you
are
welcome to change it and/or distribute copies of it under certain
conditions.
Type "show copying" to see the conditions.
There is absolutely no warranty for GDB.  Type "show warranty" for
details.
This GDB was configured as "i386-linux"...
(gdb) run
Starting program:
/home/danielb/software/src/cvs/gsim/src/examples/mm1/.libs/mm1
[New Thread 16384 (LWP 20311)]
 
 Program received signal SIGSEGV, Segmentation fault.
 [Switching to Thread 16384 (LWP 20311)]
 0x400313b6 in bool std::has_facet >(std::locale
 const&) ([EMAIL PROTECTED])
 at /usr/include/g++-v3/bits/locale_facets.tcc:87
 87  /usr/include/g++-v3/bits/locale_facets.tcc: No such file or
 directory.
 in /usr/include/g++-v3/bits/locale_facets.tcc


Even making a symlink here does not fix things.

(gdb) run
Starting program:
/home/danielb/software/src/cvs/gsim/src/examples/mm1/.libs/mm1
[New Thread 16384 (LWP 20366)]

Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 16384 (LWP 20366)]
0x400313b6 in bool std::has_facet >(std::locale const&)
([EMAIL PROTECTED])
at /usr/include/g++-v3/bits/locale_facets.tcc:87
warning: Source file is more recent than executable.

87  }

So then I just said the heck with it and did an apt-get install
libstdc++3 and libstdc++3-dev (because the headers for that version are
located in the above include path that it complains about) and tried to
run it. Note: this is the wrong version of libstdc++ my program is linked
with.

[EMAIL PROTECTED]:~/software/src/cvs/gsim/src/examples/mm1$ gdb .libs/mm1
GNU gdb 5.3-debian
Copyright 2002 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and you
are
welcome to change it and/or distribute copies of it under certain
conditions.
Type "show copying" to see the conditions.
There is absolutely no warranty for GDB.  Type "show warranty" for
details.
This GDB was configured as "i386-linux"...
(gdb) run
Starting program:
/home/danielb/software/src/cvs/gsim/src/examples/mm1/.libs/mm1
[New Thread 16384 (LWP 20439)]

Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 16384 (LWP 20439)]
0x400313b6 in bool std::has_facet >(std::locale const&)
([EMAIL PROTECTED])
at /usr/include/g++-v3/bits/locale_facets.tcc:87
87__vec_facet* __facet = __loc._M_impl->_M_facets;
(gdb)


I think something funky may be going on with libstdc++. At any rate it makes 
debugging some c++ programs impossible. It wold be nice to be able to
use the latest libstdc++ when developing c++ apps and be able to run
them inside gdb. 

Also, this may be hard to reproduce as it seems perhaps you need to make
a call into the locale templates, but I am not 100% sure of this.

Dan
<[EMAIL PROTECTED]>
-- System Information:
Debian Release: testing/unstable
Architecture: i386
Kernel: Linux frodo 2.4.20-xfs #4 Thu Jan 9 11:54:54 CST 2003 i686
Locale: LANG=C, LC_CTYPE=C

Versions of packages libstdc++5 depends on:
ii  gcc-3.2-base   1:3.2.2-0pre5 The GNU Compiler Collection (base 
ii  libc6  2.3.1-9   GNU C Library: Shared libraries an
ii  libgcc11:3.2.2-0pre5 GCC support library

-- no debconf information





Bug#153965: c/8602: [3.2/3.3 regression] incorrect line numbers in warning messages when using inline functions

2003-01-15 Thread Janis Johnson
The regression was introduced with this patch:

--- gcc/ChangeLog ---
2000-10-05  Richard Henderson  <[EMAIL PROTECTED]>

  * c-decl.c (warn_missing_noreturn): Remove.
  (c_expand_body): Don't set or check can_reach_end.
  * c-tree.h (warn_missing_noreturn): Move ...
  * flags.h: ... here.
  (can_reach_end): Remove.
  * flow.c (check_function_return_warnings): New.
  (make_edges): No edge to exit for noreturn sibcalls.
  * function.c (expand_function_end): Save the return value
  clobber instruction.
  (mark_function_status): Mark it.
  * function.h (struct function): Add x_clobber_return_insn.
  * jump.c (can_reach_end): Remove.
  (calculate_can_reach_end): Remove.
  (jump_optimize_1): Don't call it.
  * output.h (check_function_return_warnings): Declare.
  * toplev.c (warn_missing_noreturn): Move from c-decl.c
  (rest_of_compilation): Call check_function_return_warnings.

http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=8602







Bug#176797: libstdc++5: GDB looks in the wrong place for libstdc++ headers

2003-01-15 Thread Daniel Jacobowitz
On Wed, Jan 15, 2003 at 02:15:04AM -0600, Daniel E Baumann wrote:
> Package: libstdc++5
> Version: 1:3.2.2-0pre5
> Severity: important
> 
> When running my c++ program from inside gdb I get the following:
> 
> [EMAIL PROTECTED]:~/software/src/cvs/gsim/src/examples/mm1$ gdb .libs/mm1
> GNU gdb 5.3-debian
> Copyright 2002 Free Software Foundation, Inc.
> GDB is free software, covered by the GNU General Public License, and you
> are
> welcome to change it and/or distribute copies of it under certain
> conditions.
> Type "show copying" to see the conditions.
> There is absolutely no warranty for GDB.  Type "show warranty" for
> details.
> This GDB was configured as "i386-linux"...
> (gdb) run
> Starting program:
> /home/danielb/software/src/cvs/gsim/src/examples/mm1/.libs/mm1
> [New Thread 16384 (LWP 20311)]
>  
>  Program received signal SIGSEGV, Segmentation fault.
>  [Switching to Thread 16384 (LWP 20311)]
>  0x400313b6 in bool std::has_facet >(std::locale
>  const&) ([EMAIL PROTECTED])
>  at /usr/include/g++-v3/bits/locale_facets.tcc:87
>  87  /usr/include/g++-v3/bits/locale_facets.tcc: No such file or
>  directory.
>  in /usr/include/g++-v3/bits/locale_facets.tcc

That's not enough information.  How was this built?  What libraries is
it really linked to?  What headers are really opened during build?

-- 
Daniel Jacobowitz
MontaVista Software Debian GNU/Linux Developer




Bug#176064: gcc-3.2: Provide a way to build cpu-specific versions

2003-01-15 Thread Matthias Klose
Daniel Schepler writes:
> Package: gcc-3.2
> Version: 1:3.2.2-0pre3
> Severity: wishlist
> 
> I've been rebuilding all my packages with Athlon optimization, using a
> combination of pbuilder and pentium-builder.  Unfortunately, because
> of the way this works, gcc-3.2 isn't compiled with Athlon
> optimization.  It would be nice to have a way to get this to happen.
> 
> Probably the easiest way (for me) would be to recognize the
> DEBIAN_BUILDARCH environment variable, which is also what
> pentium-builder uses.  If the variable were set, stage 2 and above,
> along with the libraries, would be built using
> "-O... -march=$DEBIAN_BUILDARCH -mcpu=$DEBIAN_BUILDARCH".

it would be easier to add an DEBIAN_EXTRA_BUILDFLAGS, as not every
architecture does have -mcpu/-march. s390 uses -mtune. I didn't check
all architectures ...




Bug#176797: libstdc++5: GDB looks in the wrong place for libstdc++ headers

2003-01-15 Thread Daniel E Baumann
On Wed, Jan 15, 2003 at 03:05:55PM -0500, Daniel Jacobowitz wrote:
> On Wed, Jan 15, 2003 at 02:15:04AM -0600, Daniel E Baumann wrote:
> > Package: libstdc++5
> > Version: 1:3.2.2-0pre5
> > Severity: important
> > 
> > When running my c++ program from inside gdb I get the following:
> > 
> > [EMAIL PROTECTED]:~/software/src/cvs/gsim/src/examples/mm1$ gdb .libs/mm1
> > GNU gdb 5.3-debian
> > Copyright 2002 Free Software Foundation, Inc.
> > GDB is free software, covered by the GNU General Public License, and you
> > are
> > welcome to change it and/or distribute copies of it under certain
> > conditions.
> > Type "show copying" to see the conditions.
> > There is absolutely no warranty for GDB.  Type "show warranty" for
> > details.
> > This GDB was configured as "i386-linux"...
> > (gdb) run
> > Starting program:
> > /home/danielb/software/src/cvs/gsim/src/examples/mm1/.libs/mm1
> > [New Thread 16384 (LWP 20311)]
> >  
> >  Program received signal SIGSEGV, Segmentation fault.
> >  [Switching to Thread 16384 (LWP 20311)]
> >  0x400313b6 in bool std::has_facet >(std::locale
> >  const&) ([EMAIL PROTECTED])
> >  at /usr/include/g++-v3/bits/locale_facets.tcc:87
> >  87  /usr/include/g++-v3/bits/locale_facets.tcc: No such file or
> >  directory.
> >  in /usr/include/g++-v3/bits/locale_facets.tcc
> 
> That's not enough information.  How was this built?  What libraries is
> it really linked to?  What headers are really opened during build?

It was built with g++-3.2 so it is linked to libstdc++5 (well, and my
lib gsim, gnu common c++ built from cvs and gnu scientific
library, etc.). It uses the headers in /usr/include/c++/3.2 which is where
they are for libstdc++5[-dev], AFAIK.

ldd -v gives me:

libgsim.so.0 => /usr/lib/libgsim.so.0 (0x40022000)
libgsl.so.0 => /usr/lib/libgsl.so.0 (0x4004b000)
libgslcblas.so.0 => /usr/lib/libgslcblas.so.0 (0x40194000)
libccext2-1.1.so.0 => /usr/lib/libccext2-1.1.so.0 (0x401be000)
libccgnu2-1.1.so.0 => /usr/lib/libccgnu2-1.1.so.0 (0x401fb000)
libxml2.so.2 => /usr/lib/libxml2.so.2 (0x4022f000)
libz.so.1 => /lib/libz.so.1 (0x402e8000)
libdl.so.2 => /lib/libdl.so.2 (0x402f7000)
libstdc++.so.5 => /usr/lib/libstdc++.so.5 (0x402fa000)
libm.so.6 => /lib/libm.so.6 (0x403a3000)
libgcc_s.so.1 => /lib/libgcc_s.so.1 (0x403c4000)
libpthread.so.0 => /lib/libpthread.so.0 (0x403cc000)
libc.so.6 => /lib/libc.so.6 (0x4041b000)
libccext2-0.99.so.0 => /usr/lib/libccext2-0.99.so.0 (0x4052c000)
libccgnu2-0.99.so.0 => /usr/lib/libccgnu2-0.99.so.0 (0x4055a000)
/lib/ld-linux.so.2 => /lib/ld-linux.so.2 (0x4000)

Version information:
.libs/mm1:
libgcc_s.so.1 (GCC_3.0) => /lib/libgcc_s.so.1
libc.so.6 (GLIBC_2.0) => /lib/libc.so.6
libc.so.6 (GLIBC_2.1.3) => /lib/libc.so.6
libstdc++.so.5 (CXXABI_1.2) => /usr/lib/libstdc++.so.5
libstdc++.so.5 (GLIBCPP_3.2) => /usr/lib/libstdc++.so.5
/usr/lib/libgsim.so.0:
libm.so.6 (GLIBC_2.0) => /lib/libm.so.6
libc.so.6 (GLIBC_2.1.3) => /lib/libc.so.6
libc.so.6 (GLIBC_2.0) => /lib/libc.so.6
/usr/lib/libgsl.so.0:
libc.so.6 (GLIBC_2.1.3) => /lib/libc.so.6
libc.so.6 (GLIBC_2.1) => /lib/libc.so.6
libc.so.6 (GLIBC_2.0) => /lib/libc.so.6
libm.so.6 (GLIBC_2.0) => /lib/libm.so.6
/usr/lib/libgslcblas.so.0:
libc.so.6 (GLIBC_2.1.3) => /lib/libc.so.6
libc.so.6 (GLIBC_2.0) => /lib/libc.so.6
/usr/lib/libccext2-1.1.so.0:
libc.so.6 (GLIBC_2.1.3) => /lib/libc.so.6
libc.so.6 (GLIBC_2.0) => /lib/libc.so.6
/usr/lib/libccgnu2-1.1.so.0:
libc.so.6 (GLIBC_2.1.2) => /lib/libc.so.6
libc.so.6 (GLIBC_2.1.3) => /lib/libc.so.6
libc.so.6 (GLIBC_2.0) => /lib/libc.so.6
libc.so.6 (GLIBC_2.1) => /lib/libc.so.6
/usr/lib/libxml2.so.2:
libm.so.6 (GLIBC_2.0) => /lib/libm.so.6
libc.so.6 (GLIBC_2.1.3) => /lib/libc.so.6
libc.so.6 (GLIBC_2.3) => /lib/libc.so.6
libc.so.6 (GLIBC_2.1) => /lib/libc.so.6
libc.so.6 (GLIBC_2.0) => /lib/libc.so.6
/lib/libz.so.1:
libc.so.6 (GLIBC_2.1.3) => /lib/libc.so.6
libc.so.6 (GLIBC_2.1) => /lib/libc.so.6
libc.so.6 (GLIBC_2.0) => /lib/libc.so.6
/lib/libdl.so.2:
libc.so.6 (GLIBC_2.3) => /lib/libc.so.6
libc.so.6 (GLIBC_2.1.3) => /lib/libc.so.6
libc.so.6 (GLIBC_2.1) => /lib/libc.so.6
libc.so.6 (GLIBC_PRIVATE) => /lib/libc.so.6
libc.so.6 (GLIBC_2.0) => /lib/libc.so.6
/usr/lib/libstdc++.so.5:
libgcc_s.so.1 (GCC_3.0)