headers
David McPaul | 1 Jun 2005 05:12
Picon

compilation problem with Haiku

Hello,

	I am trying to get haiku to compile but I am having a problem with 
the gensyscall tool.

	The error generated is:

Link objects/x86.R1/tools/gensyscalls/gensyscallinfos
objects/x86.R1/tools/gensyscalls/
gensyscallinfos.o(.gnu.linkonce.t.__ls__H3ZcZt18string_char_traits1ZcZt
24__default_alloc_template2b0i0_R7ostreamRCt12basic_string3ZX01ZX11ZX21
_R7ostream+0x3f): In function `ostream & operator<<<char, 
string_char_traits<char>, __default_alloc_template<false, 0> >(ostream 
&, basic_string<char, string_char_traits<char>, 
__default_alloc_template<false, 0> > const &)':
: undefined reference to `ostream::write(char const *, long)'
collect2: ld returned 1 exit status

Looking at our version of stdc++.r4 the ostream::write is defined with 
streamsize as the type which resolves to unsigned long so the error is 
to be expected for the basic function.

So I would expect a converter function in iostream.h to handle this 
type.

I am using the following gcc version on R5 Pro
Reading specs from /boot/develop/tools/gnupro/lib/gcc-lib/i586-pc-beos/
2.95.3-beos-041202/specs
gcc version 2.95.3-beos-041202
(Continue reading)

Permalink | Reply | 0 comments |
headers
Daniel Robson | 1 Jun 2005 06:34
Picon
Picon

Google Summer Of Code

Hi all,

Just read on slashdot about the google summer of code 
(http://code.google.com/summerofcode.html) and thought it might be an 
interesting opportunity for Haiku. Possibly Michael, or someone else 
high up, could contact the google team responsible and get Haiku listed?

Just a thought.
Danny
Permalink | Reply | 2 comments |
headers
Stefano Ceccherini | 1 Jun 2005 08:40
Picon

Re: compilation problem with Haiku


Hi,

>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 ?

Stefano Ceccherini aka Jack Burton
---------------------------------------------------------------
Scegli il tuo dominio preferito e attiva la tua email! Da oggi
l'eMail di superEva e' ancora piu' veloce e ricca di funzioni!
http://webmail.supereva.it/new/
---------------------------------------------------------------
Permalink | Reply | 503 comments |
headers
David McPaul | 1 Jun 2005 10:47
Picon

Re: compilation problem with Haiku

On 1 Jun 2005 06:40:41 -0000 Stefano Ceccherini <burton666@...>
 said
> 
> Hi,
> 
> >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.

Cheers
David

--
Everyone can be taught to sculpt: Michelangelo would have had to be
taught how ___not to.  So it is with the great programmers.
Permalink | Reply | 503 comments |
headers
Ingo Weinhold | 1 Jun 2005 11:43
Picon

Re: compilation problem with Haiku

On Wed, 1 Jun 2005, David McPaul wrote:

> On 1 Jun 2005 06:40:41 -0000 Stefano Ceccherini <burton666@...>
> 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.

CU, Ingo
Permalink | Reply | 9 comments |
headers
David McPaul | 1 Jun 2005 11:56
Picon

Re: compilation problem with Haiku

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

Yes configure has been re-run.  Same error

Link objects/x86.R1/tools/gensyscalls/gensyscallinfos
objects/x86.R1/tools/gensyscalls/
(Continue reading)

Permalink | Reply | 0 comments |
headers
David McPaul | 1 Jun 2005 12:00
Picon

Re: compilation problem with Haiku

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

Hmm, I just reread this.

So the line:
(Continue reading)

Permalink | Reply | 7 comments |
headers
Ingo Weinhold | 1 Jun 2005 12:33
Picon

Re: compilation problem with Haiku

On Wed, 1 Jun 2005, David McPaul wrote:

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

Permalink | Reply | 6 comments |
headers
David McPaul | 1 Jun 2005 13:45
Picon

Re: compilation problem with Haiku

On Wed, 1 Jun 2005 12:33:14 +0200 (MEST) Ingo Weinhold <bonefish@...
berlin.de> said
> On Wed, 1 Jun 2005, David McPaul wrote:
> 
> > On Wed, 1 Jun 2005 11:43:32 +0200 (MEST) Ingo Weinhold <
> > bonefish@...
> > berlin.de> said
> >> On Wed, 1 Jun 2005, David McPaul wrote:
> >>> On 1 Jun 2005 06:40:41 -0000 Stefano Ceccherini <
> >>> burton666@...>
> >>> 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
(Continue reading)

Permalink | Reply | 5 comments |
headers
Axel Dörfler | 1 Jun 2005 14:41
Picon

Re: compilation problem with Haiku

"David McPaul" <dmcpaul@...> wrote:
> I still have a number of errors when running makehdimage, some 
> missing 
> object files and some files with compile errors.
> but I am finding that if I run jam manually against the missing bits 
> they compile and link ok and that gets me past the error.
> So far I have had to manually do kernel.so and strace

I have the same problem over here on all machines I am building under. 
This looks to me like a Jam problem, although I haven't investigated 
it; I've briefly scanned the Jam sources, but I saw no artificial limit 
that could cause this.
It happens no matter if the StatCacheServer is running in the 
background or not.

Bye,
   Axel.
Permalink | Reply | 4 comments |

Gmane