Go to the FreeLists Home Page Home Signup Help Login
 



Browse haiku: This Month's ArchiveMain Archive PageRelated postsPrevious by DateNext by Date

[openbeos] Re: compilation problem with Haiku

  • From: Ingo Weinhold <bonefish@xxxxxxxxxxxxxxx>
  • To: openbeos@xxxxxxxxxxxxx
  • Date: Wed, 1 Jun 2005 12:33:14 +0200 (MEST)
On Wed, 1 Jun 2005, David McPaul wrote:

On Wed, 1 Jun 2005 11:43:32 +0200 (MEST) Ingo Weinhold <bonefish@xxxxxx
berlin.de> said
On Wed, 1 Jun 2005, David McPaul wrote:
On 1 Jun 2005 06:40:41 -0000 Stefano Ceccherini <
burton666@xxxxxxxxxxx>
said

So am I missing something in my build environment?

Did you install the compiler following the included instructions ? i.e: did you copy the new libstdc++.r4.so in the system directory ? did
you copy the new c++ headers in the right place ?

Yes.  I do note however that the hauku build process creates it's
own
stdc++ library to link against.

That's correct, but for building gensyscall[info]s the build platform environment is used, since those tools need to be executed as part of the build process. Have you re-run `configure' after installing the new gcc? If not, the old compiler will still be used.

I was wrong here, BTW. The compiler in the PATH is always used. There are only things like the libgcc.a path, which are determined by configure, but those don't play a role in this case.


Hmm, I just reread this.

So the line:

gcc  -o "objects/x86.R1/tools/gensyscalls/gensyscallinfos"  "objects/
x86.R1/tools/gensyscalls/gensyscallinfos.o"  -lstdc++.r4 ;

should really be

gcc  -o "objects/x86.R1/tools/gensyscalls/gensyscallinfos"  "objects/
x86.R1/tools/gensyscalls/gensyscallinfos.o"  -llibstdc++.r4 ;

So the Jamfile rule
LinkSharedOSLibs gensyscalls : $(BUILD_LIBSTDC++) ;

is wrong?

No, the link line is just fine. The linker expands -lstdc++.r4 to the first libstdc++.r4.{a/so} it finds in its search path. Which isn't the one built by the Haiku build system (as you suggest in your other mail), as it is apparently, and rightly so, not in the search path (according to the build line).


Please rebuild gensyscallinfos.o and check, if the compile line for it looks OK (jam -a -d2 gensyscallinfos). If it does, then there's definitely something wrong with your build environment (wrong STL headers or wrong libstdc++.r4).

CU, Ingo

Other related posts:

  • [openbeos] compilation problem with Haiku
  • [openbeos] Re: compilation problem with Haiku
  • [openbeos] Re: compilation problem with Haiku
  • [openbeos] Re: compilation problem with Haiku
  • [openbeos] Re: compilation problem with Haiku
  • [openbeos] Re: compilation problem with Haiku
  • [openbeos] Re: compilation problem with Haiku
  • [openbeos] Re: compilation problem with Haiku
  • [openbeos] Re: compilation problem with Haiku
  • [openbeos] Re: compilation problem with Haiku
  • [openbeos] Re: compilation problem with Haiku
  • [openbeos] Re: compilation problem with Haiku
  • [openbeos] Re: compilation problem with Haiku




  • [ Home | Signup | Help | Login | Archives | Lists ]

    All trademarks and copyrights within the FreeLists archives are owned by their respective owners.
    Everything else ©2008 Avenir Technologies, LLC.