Opened 12 years ago

Closed 12 years ago

#1333 closed bug (invalid)

_G_config.h issue

Reported by: kaliber Owned by: bonefish
Priority: low Milestone: R1
Component: Build System Version: R1/pre-alpha1
Keywords: Cc:
Blocked By: Blocking:
Has a Patch: no Platform: All

Description

File _G_config.h is included by some other headers (cmath, stl_config.h), but it is placed in glibc directory which isn't in gcc's search path.

Proposed solutions: a) svn mv glibc/_G_config.h posix/ b) add search path in buildtools/legacy/gcc/gcc/config/i386/beos-elf.h to the /boot/develop/headers/glibc c) ?

Change History (5)

comment:1 by axeld, 12 years ago

Component: - GeneralBuild System
Owner: changed from axeld to bonefish

It would be nice if we could keep this header private.

comment:2 by bonefish, 12 years ago

Priority: normallow

GCC 2.95.3 has not been ported to Haiku yet, so it obviously can't contain Haiku specifics. It has also not yet been decided, where the headers are to be placed in a Haiku installation -- _G_config.h might end up in posix/ as under BeOS.

comment:3 by kaliber, 12 years ago

What does it mean GCC is not ported to Haiku? As I understand we need compiler compatible with BeOS, so there is nothing to do specific for Haiku IMHO. Are we going to create i586-pc-haiku instead of i586-pc-beos?

I think it's time to decide about GCC on Haiku. GCC on Haiku is quite stable, so I'm testing it and reporting such bugs.

in reply to:  3 comment:4 by bonefish, 12 years ago

Replying to kaliber:

What does it mean GCC is not ported to Haiku? As I understand we need compiler compatible with BeOS, so there is nothing to do specific for Haiku IMHO.

You're mistaken here. The plan for Haiku is to be mostly binary and source compatible with BeOS R5. This doesn't imply compatibility in the other direction, nor does it mean that we have to use the same compiler.

Are we going to create i586-pc-haiku instead of i586-pc-beos?

I've already done that for gcc 4. I'm not quite sure yet, if it's worth the work to also to do that for gcc 2.95.3 or if we just stick to the status quo and start migrating to gcc 4 soon. It would be consequent though. Although mostly compatible with BeOS, we've created a new platform and it makes neither sense to live with BeOS work-arounds not necessary for Haiku, nor to hack special cases into *-beos ports for Haiku specifics. It would be the natural strategy to re-port the whole tool chain (perl, autoconf/-make, gcc, binutils,...) to Haiku -- they probably won't build from the sources as they are anyway, since our uname returns "Haiku" instead of "BeOS".

I think it's time to decide about GCC on Haiku. GCC on Haiku is quite stable, so I'm testing it and reporting such bugs.

Your reports are much appreciated. We have a lot of tasks to do before the gcc question really becomes urgent, though.

comment:5 by bonefish, 12 years ago

Resolution: invalid
Status: newclosed

Closing this one. a) is mostly a question of correct installation, i.e. _G_config.h has to be copied to /boot/develop/headers/posix. b) is a non-issue -- if you want to use the gcc built for BeOS, you'll have to replace at least the compiler system headers. I recently wrote a mail about this on the developer list.

Note: See TracTickets for help on using tickets.