++6-4.3-doc/libstdc++/html/_form0.ps not
found.
but is nonetheless created by the package when it is installed, which is
a bug in itself.
So could you please rid us of the unwanted file ?
--
Laurent Bonnaud.
http://www.lis.inpg.fr/pages_perso/bonnaud/
--
To UNSUBSCRIBE, email to debian-gcc
linked to /bin/bash
Versions of packages libstdc++6-4.3-doc depends on:
ii gcc-4.3-base 4.3.0-3The GNU Compiler Collection (base
libstdc++6-4.3-doc recommends no packages.
-- no debconf information
--
Laurent Bonnaud.
http://www.lis.inpg.fr/pages_perso/bonnaud/
--
To U
Package: java-gcj-compat
Version: 1.0.44-1
Severity: normal
Hi,
here is the problem:
$ symlinks -r /usr/lib/jvm/java-1.4.2-gcj-4.0-1.4.2.0/
dangling: /usr/lib/jvm/java-1.4.2-gcj-4.0-1.4.2.0/bin/jar ->
../../../../bin/fastjar-4.0
I installed fastjar 4.1 from experimental and therefore my syste
Package: libstdc++6-4.1-doc
Version: 4.1-0exp0
Severity: normal
Tags: experimental
Hi,
thanks for packaging pre-release versions of gcc 4.1 !
Here is the problem:
Setting up libstdc++6-4.1-doc (4.1-0exp0) ...
cannot create dhelp file
'/usr/share/doc/libstdc++6-4.0-doc/libstdc++/html_user/.dhe
Package: java-gcj-compat-dev
Version: 1.0.30-4
Severity: normal
Hi,
here is the problem:
$ symlinks -r /usr/lib/jvm/java-1.4.2-gcj-4.0-1.4.2.0/
dangling: /usr/lib/jvm/java-1.4.2-gcj-4.0-1.4.2.0/man/man1/javac.1.gz ->
../../../../../share/man/man1/ecj.1.gz
dangling: /usr/lib/jvm/java-1.4.2-gcj-
n/ experimental main contrib
but gcc-4.0 is not available. I'm wondering which packages Andreas
Jochens is using to report all the build failures in Debian packages
with gcc-4.0.
Thanks again,
--
Laurent Bonnaud.
http://www.lis.inpg.fr/pages_perso/bonnaud/
--
To UNSUBSCRIBE, email to
fortunately my edits are undone by the build process. I don't know
how to split the build so that my edit remains.
BTW, the file I have on my system contains:
MULTILIB_OSDIRNAMES = ../lib64 ../lib32
(gcc-4.0_4.0.0-6 source package)
--
Laurent Bonnaud.
http://www.lis.inpg.fr/pages_perso/
> Which version of ia32-libs-dev was installed during the build?
The latest version available in sid:
ii ia32-libs-dev 1.4 ia32 development libraries and
headers for use on ia32/ia6
--
Laurent Bonnaud.
http://www.lis.inpg.fr/pages_perso/bonnaud/
--
On sam, 2005-05-07 at 10:18 +0200, Matthias Klose wrote:
> strange, because it's already found in the build dependency list
> (without any typo).
Indeed. This is in fact a problem in dpkg-buildpackage that fails to
check build dependencies even if I explicitly add the -D option.
Package: gcc-4.0
Version: 4.0.0-2
Severity: serious
Tags: experimental
Justification: package must BFS
Hi,
here is the problem:
$ fakeroot apt-get -b source gcc-4.0
[...]
./xgcc -B./ -B/usr/x86_64-linux/bin/ -isystem /usr/x86_64-linux/include
-isystem /usr/x86_64-linux/sys-include
-L/home/bon
Package: gcc-4.0
Version: 4.0.0-2
Severity: serious
Tags: experimental
Justification: build-dependencies must be listed exhaustively
Hi,
here is the problem:
$ fakeroot apt-get -b source gcc-4.0
[...]
mkdir /home/bonnaud/gcc-4.0-4.0.0/build
: # configure
cd /home/bonnaud/gcc-4.0-4.0.0/build \
Package: libstdc++6-4.0-dbg
Version: 4.0-0pre5
Severity: important
Tags: experimental
Hi,
here is the problem:
# apt-get -t experimental install libstdc++6-4.0-dbg
Reading Package Lists... Done
Building Dependency Tree... Done
Some packages could not be installed. This may mean that you have
re
l_'
> > before installing another version: File name too long
> > dpkg-deb: subprocess paste killed by signal (Broken pipe)
>
> are you able to reproduce the failure with the current version in
> experimental?
No, it is fixed. Thank you !
I'm not closing the bug s
Package: libstdc++6-4.0-doc
Version: 4.0-0pre4
Severity: grave
Justification: renders package unusable
Hi,
here is the problem:
# apt-get install libstdc++6-4.0-doc
[...]
Unpacking libstdc++6-4.0-doc (from .../libstdc++6-4.0-doc_4.0-0pre4_all.deb) ...
dpkg: error processing
/var/cache/apt/arch
Package: gij-4.0
Version: 4.0-0pre2
Severity: grave
Justification: renders package unusable
Hi,
here is the problem:
$ /usr/bin/gij-4.0
/usr/bin/gij-4.0: error while loading shared libraries: libgij.so.0: cannot
open shared object file: No such file or directory
$ ldd -r /usr/bin/gij-4.0
Hi,
let me add the following problem to my initial bug report:
# /etc/cron.daily/man-db
mandb: can't open /usr/share/man/man3/std::basic_stringbuf.3: No such file or
directory
mandb: warning: /usr/share/man/man3/std::stringbuf.3.gz: bad symlink or ROFF
`.so' request
Package: libstdc++6-4.0-doc
Version: 4.0-0pre0
Severity: normal
Tags: experimental
Hi,
here is the problem:
mandb: warning: /usr/share/man/man3/std::ofstream.3.gz: bad symlink or ROFF
`.so' request
mandb: can't open /usr/share/man/man3/std::basic_ofstream.3: No such file or
directory
mandb: w
Package: gfortran-4.0
Version: 4.0-0pre0
Severity: normal
Tags: experimental
Hi,
here are the 2 dangling symlinks:
mandb: warning: /usr/share/man/man1/i386-linux-g95-4.0.1 is a dangling symlink
mandb: warning: /usr/share/man/man1/i486-linux-g95-4.0.1 is a dangling symlink
They point to "g95-4.
bin/prelink.bin: Could not find virtual address slot for
/usr/lib/libluminate.so.5.0.0
--
Laurent Bonnaud.
http://www.lis.inpg.fr/pages_perso/bonnaud/
Package: libstdc++6-doc
Version: 3.5-0pre1
Severity: normal
Tags: experimental
Hi,
here is the problem:
# mandb -c
[...]
mandb: can't open /usr/share/man/man3/std::basic_streambuf.3: No such file or
directory
mandb: warning: /usr/share/man/man3/std::wstreambuf.3.gz: bad symlink or ROFF
`.so'
Package: libstdc++6-doc
Version: 3.5-0pre1
Severity: normal
Tags: experimental
Hi,
here is the problem:
$ man -k std:: |grep unknow
std::allocator (3) - (unknown subject)
std::allocator - (3) [std::allocator] - (unknown subject)
std::back_insert_iterator (3) - (unknown subject)
std::back_inse
Package: gnat-3.4-doc
Version: 3.4.1-5
Severity: normal
Hi,
the following doc-base files:
/usr/share/doc-base/gnat-style-3.4
/usr/share/doc-base/gnat_rm-3.4
/usr/share/doc-base/gnat_ugn_unw-3.4
refer to HTML files in the /usr/share/doc/gcc-3.4-base/ directory
whereas they are in /usr/sha
Package: libstdc++6-doc
Version: 3.4-0pre4
Severity: normal
Tags: experimental
Hi,
here is the problem:
$ zcat /usr/share/man/man3/Allocators.3.gz | wc
0 0 0
-- System Information:
Debian Release: testing/unstable
APT prefers unstable
APT policy: (500, 'unstable'), (1, '
Package: gcc-snapshot
Version: 20040215-1
Severity: normal
Hi,
I suppose that gcc-snapshot is currently superseded by gcc-3.4-pre in
experimental, but this report may be useful once you package gcc 3.5 in
gcc-snapshot (hint!, hint! :>).
Anyway here is what prelink complains about:
/usr/sbin/pr
Package: libstdc++6-dbg
Version: 3.4-0pre1
Severity: important
Tags: experimental
Hi,
here is the problem:
Unpacking libstdc++6-dbg (from .../libstdc++6-dbg_3.4-0pre1_i386.deb) ...
dpkg - warning, overriding problem because --force enabled:
trying to overwrite `/usr/lib/debug/libstdc++.a', whi
Package: libstdc++5-3.3-doc
Version: 1:3.3.3-0pre2
Severity: normal
Hi,
here is the problem:
$ man -k std:: | grep unknown
std::__debug_alloc (3) - (unknown subject)
std::__debug_alloc - (3) [std::__debug_alloc] - (unknown subject)
std::__default_alloc_template (3) - (unknown subject)
std::__de
Package: g++-3.3
Version: 1:3.3-0pre9
Severity: normal
Hi,
I saw Mark Mitchell's announcement about a final call for tests before
the g++ 3.3 release. So I did some tests and found that this program
generates warnings whereas it did not with g++ 3.2:
// Compile with: g++-3.3 -O -Winline essai.
Package: gpc
Version: 1:2.95.4-15
Severity: normal
Hi,
this symlink is dangling:
/usr/bin/gpc-run -> gpc-run-2.95
package gpc-2.95 contains /usr/bin/gpc-2.95 but not
/usr/bin/gpc-run-2.95
-- System Information:
Debian Release: testing/unstable
Architecture: i386
Kernel: Linux jophur 2.4.2
> try
>
> dpkg-buildpackage "-rfakeroot --" ...
It would probably work.
Unfortunately, I used dpkg-buildpackage only because my first build
attempt failed. I generally use:
fakeroot apt-get -b source gcc-3.2
which would have the same problem with LD_LIBRARY_PATH.
Therefore I think th
Package: gcc-3.2
Version: 1:3.2-0pre4
Severity: normal
Hi,
I tried to build gcc 3.2 packages on a woody system. I used this command:
"fakeroot dpkg-buildpackage -b" and the build ended up with this error:
[...]
make[5]: Leaving directory `/tmp/LB/gcc-3.2-3.2ds0/build/i386-linux/libjava'
make[4]
>> Is this bug been reported to the Gnats GCC BTS (I don't see any
>> reference in bug #147864) ? If yes under which bug number ?
> It's ada/5679.
Thank you for the info. I'm cc'ing the Debian BTS for the record.
--
Laurent.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of
Matthias> Yes, can be done by moving the libstdc++ headers to
Matthias> /usr/include/g++-v3-3.1 or something like this. Do we want to
Matthias> do this?
You are the final judge, but I think this would be a very nice Debian
feature.
--
Laurent.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
wi
Package: gcc-3.0
Version: 1:3.0.2-0pre010922
Severity: normal
Hi,
here is the bug (seen while compiling ALSA modules):
$ gcc -v -O2 -march=k6 -c ainstr_gf1.i
Reading specs from /usr/lib/gcc-lib/i386-linux/3.0.2/specs
Configured with: ../src/configure -v
--enable-languages=c,c++,java,f77,proto,
Hi,
I tested again with
ii g++-3.0 3.0.1-0pre010811The GNU C++ compiler.
and the bug is fixed.
Thanks !
--- Begin Message ---
Synopsis: internal error at compiling a c++ source file
State-Changed-From-To: open->closed
State-Changed-By: rodrigc
State-Changed-When: Sun Aug 12
> "Jaakko" == Jaakko Niemi <[EMAIL PROTECTED]> writes:
Jaakko>
Jaakko> The compile time is not a problem here, but failure building is.
Jaakko>
Jaakko> You move aiosout (const aiosout &o) ... under public:, which
Jaakko> effectively hides the problem. Please take look at:
Jaakko>
Jaakko>
Hi,
you write that "apparently", g++ 3.0 tries a longer conversion chain
than 2.95. Indeed, the compiler message let us think so. But to
verify this, I added traces into your testcase. The result is that
both g++ versions use the same conversion chain (and indeed g++ 3.0
takes much longer to c
Package: g++-3.0
Version: 1:3.0-1
Severity: normal
Hi,
according to http://gcc.gnu.org/bugs.html#known, it would seem to be a good
idea to compile g++-3.0 with the --use-cxa-atexit switch:
>Global destructors are not run in the correct order
>Global destructors should be run in the reverse ord
> "Matthias" == Matthias Klose <[EMAIL PROTECTED]> writes:
Matthias>
Matthias> ok, please attach the GCC GNATS number to the Debian report.
Here it is :
Thank you very much for your problem report.
It has the internal identification `optimization/3315'.
The individual assigned to look at yo
Hi again,
shortly after sending this bugreport I received a mail with the cause
of the failure. It is this header line:
To: [EMAIL PROTECTED] debian-gcc@lists.debian.org
And here is the mailer daemon explanation:
A message that you sent contained one or more recipient addresses that were
in
Hi again,
after some trouble, I sent a bugreport upstreams. I did not send a
copy to the Debian list because it is a little too big (600 KB).
--
Laurent.
Package: gcc-3.0
Version: 1:3.0-1
Severity: normal
Hi,
I tried to use gccbug to report a gcc bug, but failed:
$ gccbug-3.0
a)bort, e)dit or s)end? s
gccbug-3.0: mysterious mail failure.
gccbug-3.0: the problem report remains in /tmp/pbaddUwzq0 and is not sent.
Perhaps I did something wrong wh
Package: g++-3.0
Version: 1:3.0-1
Severity: important
Hi,
here is the bug:
$ fakeroot apt-get -b source mozilla
[building mozilla_0.9.1-3...]
nsFormControlHelper.cpp: In static member function `static void
nsFormControlHelper::PaintFixedSizeCheckMark(nsIRenderingContext&, float)':
nsFormCon
Hi,
now that g++-3.0 is offcially out, we have 2 C++ compilers with 2
incompatible C++ ABI. Currently all C++ libraries have been compiled
with g++-2.95.x. Is there a plan for the C++ libraries transition ?
More precisely :
- Will each library switch independently ?
- Will there be 2 devel
Hi,
this version of g++-3.0 does not crash anymore on this code:
ii g++-3.0 3.0-0pre010526 The GNU C++ compiler.
However the code does not link because it is somewhat incorrect.
Therefore, this bug should probably be reassigned to g++-2.95.
--
Laurent.
Hi,
the program as is does not generate any warning, indeed. This is
probably because the Foo::Bar method is inline and gcc does not
generate code for it unless it is used.
However, if you add some code to force the method to be used, then g++
warns you. For instance with this code :
#include
Hi,
sorry I made a mistake in my original report because I found another
bug while writing the report. The missing -r option is in
/var/lib/dpkg/info/gpc-2.95.preinst :
# dpkg cannot handle transistions from symlinks to directories
rm -f /usr/share/doc/gpc-2.95 || true
The prerm script still l
Package: gpc-2.95
Version: 1:2.95.4-0.010424
Severity: normal
Hi,
here is the error :
# apt-get install --reinstall gpc-2.95
Reading Package Lists... Done
Building Dependency Tree... Done
0 packages upgraded, 0 newly installed, 1 reinstalled, 0 to remove and 8 not
upgraded.
2 packages not full
47 matches
Mail list logo
