From: Jaap-Jan Boor <jjboor@aimsys.nl>
To: "Peter Gehirnforce" <Gehirnmann@gmx.de>
Cc: linuxppc-embedded@ozlabs.org
Subject: Re: ELDK/DENX: doesn't find iostream-lib when linking
Date: Thu, 12 May 2005 12:26:26 +0200 [thread overview]
Message-ID: <d2163c240d3070ac810975f1346a0d88@aimsys.nl> (raw)
In-Reply-To: <25101.1115889218@www45.gmx.net>
Peter,
you should use g++ as compiler front end when compiling C++ programs
> compiler =3D ${CROSS_COMPILE}g++
best regards,
Jaap-Jan
On 12-mei-05, at 11:13, Peter Gehirnforce wrote:
> I use a makefile with dependencies:
>
> --------------------------------------------------
> # Makefile for simple test program
> # The CROSS_COMPILE is set globally, as well as ELDK gcc-paths
>
> compiler =3D ${CROSS_COMPILE}gcc
> simple_server_objects =3D ServerSocket.o Socket.o simple_server_main.o
> simple_client_objects =3D ClientSocket.o Socket.o simple_client_main.o
>
>
> all : Socket ServerSocket simple_server_main simple_server =
ClientSocket
> simple_c
> lient_main simple_client
>
> simple_server: $(simple_server_objects)
> $(compiler) -o simple_server $(simple_server_objects)
>
>
> simple_client: $(simple_client_objects)
> $(compiler) -o simple_client $(simple_client_objects)
>
> #ppc_gcc dependencies, added for compiling with ppc only!!
> Socket:
> $(compiler) -o Socket.o -c Socket.cpp
>
> ServerSocket: Socket.o
> $(compiler) -o ServerSocket.o -c ServerSocket.cpp
>
> ClientSocket: Socket.o
> $(compiler) -o ClientSocket.o -c ClientSocket.cpp
>
> simple_server_main: ServerSocket.o
> $(compiler) -o simple_server_main.o -c simple_server_main.cpp
>
> simple_client_main: ClientSocket.o
> $(compiler) -o simple_client_main.o -c simple_client_main.cpp
>
> clean:
> rm -f *.o simple_server simple_client
> ------------------------------------------------
>
> The program itself is using <string> <iostream> and other STL libs =
with
> namespaces in use.
> It compiles for i686 on my host machine.
> BUT I had to change the Makefile!!! (that is why I posted it)
> The dependencies starting from "gcc-ppc" dependencies are added.
> Are they defined wrong?
>
> Peter
>
>> --- Urspr=FCngliche Nachricht ---
>> Von: Wolfgang Denk <wd@denx.de>
>> An: "Peter Gehirnforce" <Gehirnmann@gmx.de>
>> Kopie: etux@embeddedtux.org
>> Betreff: Re: ELDK/DENX: doesn't find iostream-lib when linking
>> Datum: Thu, 12 May 2005 09:46:10 +0200
>>
>> In message <28918.1115882747@www45.gmx.net> you wrote:
>>>
>>> when compiling for ppc_6xx architecture, the linker doesn't find the
>> lib's
>>> for iostream headers.
>>> Do I have to use other headers than the standard <iostream> ones, or=20=
>>> do
>> they
>>> simply not exist?
>>
>> I guess this is a usage error. Can you please provide a simple
>> example which shows the problem?
>>
>> Best regards,
>>
>> Wolfgang Denk
>>
>> --=20
>> Software Engineering: Embedded and Realtime Systems, Embedded Linux
>> Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd@denx.de
>> What is research but a blind date with knowledge? -- Will Harvey
>> _______________________________________________
>> etux mailing list
>> etux@embeddedtux.org
>> http://www.embeddedtux.org/mailman/listinfo/etux
>>
>
> --=20
> +++ Lassen Sie Ihren Gedanken freien Lauf... z.B. per FreeSMS +++
> GMX bietet bis zu 100 FreeSMS/Monat: http://www.gmx.net/de/go/mail
> _______________________________________________
> Linuxppc-embedded mailing list
> Linuxppc-embedded@ozlabs.org
> https://ozlabs.org/mailman/listinfo/linuxppc-embedded
prev parent reply other threads:[~2005-05-12 10:26 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20050512074615.30BE8C1512@atlas.denx.de>
2005-05-12 9:13 ` ELDK/DENX: doesn't find iostream-lib when linking Peter Gehirnforce
2005-05-12 9:12 ` Matej Kupljen
2005-05-12 9:47 ` Wolfgang Denk
2005-05-12 10:26 ` Jaap-Jan Boor [this message]
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=d2163c240d3070ac810975f1346a0d88@aimsys.nl \
--to=jjboor@aimsys.nl \
--cc=Gehirnmann@gmx.de \
--cc=linuxppc-embedded@ozlabs.org \
/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 NNTP newsgroup(s).