This is the mail archive of the gcc@gcc.gnu.org mailing list for the GCC project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]

Re: Does anyone have 2.95.2 running on NetBSD for PowerPC?


In article <B4DFCB7CDE2DD4118F690008C78694167B3644@tahoe.allegronetworks.com> you write:
>
>The pain of the port is beginning to seem fairly endless.
>I suppose that is why the port is not readily available?
>In my efforts so far, I do not seem to be able to prevent
>the config code from inserting "CLIB=-lld" into the make
>files.  That breaks everything, so I strip it by hand.
>(The `t-netbsd' explicitly sets it empty, so I don't know
>where it is getting this assignment...)  Also, since BSD
>has a rather unusual way of setting up the __va_list struct,
>I wind up getting conflicts because sometimes this is
>included before the va-ppc.h gets included and sometimes
>after.  I finally did this in /usr/include/powerpc/ansi.h:
>
>   #if  !defined( __GNUC_VA_LIST)
>   typedef struct {
>        char __gpr, __fpr, __pad[2];
>        char *__stack, *__base;
>   } __va_list;
>   #define _BSD_VA_LIST_           __va_list       /* va_list */
>   #define __GNUC_VA_LIST __va_list
>   #define __gnuc_va_list __va_list
>
>   #else
>   #define _BSD_VA_LIST_ __gnuc_va_list
>   #endif
>
>Icky.  (The native gcc does not have fixed headers and won't
>have until I get the blasted 2.95.2 installed.)
>
>Now I have this:
>
>/usr/src/tools/gcc/=build/gcc/xgcc -B/usr/src/tools/gcc/=build/gcc/ \
>  -B/usr/local/powerpc-apple-netbsdelf1.4Z/bin/ -c -DHAVE_CONFIG_H -g -O2\
>  -msoft-float -I. -I../../../../libiberty/../include  \
>  ../../../../libiberty/concat.c
>../../../../libiberty/concat.c: In function `concat':
>../../../../libiberty/concat.c:96: incompatible type for \
>  argument 1 of `__builtin_memcpy'
>../../../../libiberty/concat.c:107: invalid type argument of `->'
>../../../../.....
>
>because the var args are mutilated.  What's next?
>Are there any shortcuts to this plodding?  Thanks! - Bruce
>

We do have a working OpenBSD 2.95.x config in our repository.
Time constraints meant it was not included in the FSF 2.95.x version (it came
out after 2.95, and the 2.95 freeze explicitly meant `no new ports').

(And I need to grab all my port patches since 2.95 and try to make sure they
ARE in 3.0)

You might wish to browse the openbsd repository (see www.openbsd.org for
mirror addresses) to grab the port.

And gcc 3.0 is way simpler to deal with from that side, apart from the fact
that it doesn't exist yet.


Half-joke, would be funnier if it weren't that close to reality.
FSF version syndromitis:
User A: - I have bug such and such in version x of soft foo.
FSF dev: - Ah ! that bug has been fixed for ages. Grab version y of soft foo.

Never mind that there never was a newer actual release of foo since version x,
which was n years ago...

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]