how to port stdc++ ?

[Frank Mehnert]

On Wednesday 09 March 2005 11:03, Andrushka wrote:
> I'm trying to port by self libstdc++.
> Please say me what is necessary steps compleat to build libstdc++.a ?
>
> I'm explored next:
> 1. Download stdc++ from GNU archives.
> 2. Modify config.sub (add drops target)
> 3. Modify configure add
>     *-*-drops*)
>     os_include_dir="os/generic"
>     ;;
> 4. run ./configure --target=drops --host=i486-pc-linux
> 5. run make make all-target-libiberty all-target-libstdc++-v3
>
> Please!  Write in steps what are you doing to succesful build
> libstdc++ for L4Env!!!
> What changes and additions you made to raw libstdc++ sources?
> Maybe there are any guide ?

Porting the libstdc++ to L4env is a bit complicated. To determine
all additions we made you can try

  cd l4/pkg/libstdc++/contrib/libstdc++-v3
  cvs -q diff -r1.1.1.1 -rHEAD

(use the libstdc++ package from our remote cvs)

libstdc++-v3 should work with gcc-3.2 and gcc-3.3. libstdc++-6 was the
first try to get libstdc++ work with gcc-3.4, but it is currently broken.

Have a look at drops-gcc, it must be able to build valid L4env binaries
when passing no further parameters, (e.g. drops-gcc main.c _must_ work).

Frank
-- 
## Dept. of Computer Science, Dresden University of Technology, Germany ##
## http://os.inf.tu-dresden.de/~fm3                                     ##
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
URL: <http://os.inf.tu-dresden.de/pipermail/l4-hackers/attachments/20050309/7f3d84dd/attachment-0001.sig>