Your message dated Tue, 12 Jul 2005 20:39:00 +0200
with message-id <[EMAIL PROTECTED]>
and subject line Bug#317268: g++-4.0: Assembler problem with g++-3.4
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is n
fixed with binutils-2.16.1
Yannick Beynet writes:
> Package: g++-4.0
> Version: 4.0.0-12
> Severity: important
>
> When I Try to compile with g++-4.0 I have some assembler messages like
> this :
> tmp/cceXLCbg.s: Assembler messages:
> /tmp/cceXLCbg.s:615: Warning: ignoring changed section attribu
Processing commands for [EMAIL PROTECTED]:
> # Automatically generated email from bts, devscripts version 2.8.14
> retitle 317268 g++-4.0: Assembler problem with g++-4.0
Bug#317268: g++-4.0: Assembler problem with g++-3.4
Changed Bug title.
>
End of message, stopping processing here
Package: g++-4.0
Version: 4.0.0-12
Severity: important
When I Try to compile with g++-4.0 I have some assembler messages like
this :
tmp/cceXLCbg.s: Assembler messages:
/tmp/cceXLCbg.s:615: Warning: ignoring changed section attributes for
.gnu.linkonce.t._ZNSt12_Vector_baseISsSaISsEED2Ev
/tmp/cceX
"Kapil Khosla" <[EMAIL PROTECTED]> writes:
> I guess by reading the man page I have understood that g++ is just
> a script which calls gcc compiler with options to recognize C++.
That is not true (anymore); it is now a proper binary.
Regards,
Martin
--
To UNSUBSCRIBE, email to [EMAIL PROTEC
"Kapil Khosla" <[EMAIL PROTECTED]> writes:
> I thought g++ was the C++ compiler , why do I have to upgrade gcc to
> make it work. What really is g++ ?
It is the C++ compiler driver (just like gcc is the C compiler
driver). The C++ compiler proper is cc1plus (like cc1 for C).
Regards,
Martin
--
I guess by reading the man page I have understood that g++ is just a script
which calls gcc compiler with options to recognize C++.
Thanks for your help.
Kapil
--
On Wed, 12 Jun 2002 10:33:07
Kapil Khosla wrote:
> Thanks again
>I just solved the problem using your mail . I saw that my gcc ver
Thanks again
I just solved the problem using your mail . I saw that my gcc version was 2.95.3
I upgraded to 2.95.4 and now g++ works fine.
I thought g++ was the C++ compiler , why do I have to upgrade gcc to make it
work. What really is g++ ?
Thanks a lot,
Kapil
--
On Wed, 12 Jun 2002 16:23:0
On Wed, Jun 12, 2002 at 09:28:15 -0400, Kapil Khosla wrote:
> dpkg -l g++-2.95
>
> ii g++-2.95 2.95.4-7 The GNU C++ compiler.
>
> dpkg -l binutils
> ii binutils 2.12.90.0.1-4 The GNU assembler, linker and binary
> utilitils
OK, those are the current versions for woody. (Ass
On Tue, Jun 11, 2002 at 21:53:15 -0400, Kapil Khosla wrote:
> I did an apt-get install g++-2.95 and am having problems using my C++
> compiler.
Are you running testing or unstable? What is the version number of the
g++-2.95 you installed ("dpkg -l g++-2.95")?
> I get the error message
> as: unre
Hi,
I did an apt-get install g++-2.95 and am having problems using my C++ compiler.
I get the error message
as: unrecognized option `-Qy'
I am able to generate the assembly file by doing g++ -S test.c but not able to
generate the executable.
I have also tried g++-3.0 and get the same error,
Plea
in my c++ program i write:
XtAddCallback(entry, XtNcallback, print_string, "one");
g++ 2.9 complains:
xzip.cpp: In function `int main(int, char **)':
xzip.cpp:35: passing `const char *' as argument 4 of
`XtAddCallback(_WidgetRec *, const char *,
void (*)(_WidgetRec *, void *, void *), void *)' d
Zoltan Nagy wrote:
> When I use the g++-3.0 ( gcc version 3.0.2 20010922 (Debian prerelease)
> ) the compiler doesn't link the libstdc++. It might be a bug.
Firstly, the compiler does not link at all. It is linker's task.
Secondly, the linker links it [libstdc++] fine for me (g++ is the same vers
Hi,
When I use the g++-3.0 ( gcc version 3.0.2 20010922 (Debian prerelease)
) the compiler doesn't link the libstdc++. It might be a bug.
Zoltan
14 matches
Mail list logo
