Re: port lang/gnustep-base - make configure fails on ia64

Gerald Pfeifer <[email protected]>
Newsgroups gmane.os.freebsd.devel.ia64
Message-ID <[email protected]>
While looking for something different, I noticed this one and one or
two ideas I wanted to share:

Can you check where, if at all, these symbols may be defined? ONe
theory I have is that it's using on older version of libgcc_so instead
of the one necessary for this compiler.

Can you give a newer version of GCC a try, or does that fail on ia64
or does GNUstep fail to build, then?

If it actually works and you can submit test results to 
  [email protected]
I'd be open to adding ia64 to the list of supported platforms for
lang/gcc45.

Gerald

On Wed, 10 Mar 2010, Anton Shterenlikht wrote:
>> Hallo Anton Shterenlikht,
>> 
>> > On FreeBSD 9.0-CURRENT #0 r203484M
>> > port lang/gnustep-base fails "make configure".
>> > 
>> > Please see the log here:
>> > http://seis.bris.ac.uk/~mexas/gnustep-base-ia64.log
>> 
>> /usr/local/lib/gcc42/gcc/ia64-portbld-freebsd9.0/4.2.5/../../../libobjc.so: undefined reference to `__ia64_restore_stack_nonlocal@GCC_3.0'
>> /usr/local/lib/gcc42/gcc/ia64-portbld-freebsd9.0/4.2.5/../../../libobjc.so: undefined reference to `__ia64_save_stack_nonlocal@GCC_3.0'
>> collect2: ld returned 1 exit status
>> 
>> Please rebuild your gcc port.
> 
> I've rebuilt gcc42:
> 
> > pkg_info -xo gcc-
> Information for gcc-4.2.5.20090325_2:
> 
> > gcc42 --version
> gcc42 (GCC) 4.2.5 20090325 (prerelease)
> 
> and still get the same error.
> 
> I must say that gcc42 is marked "NOT_FOR_ARCHS=  ia64 powerpc",
> which I've overwritten manually.
> Perhaps the fact that gcc42 now builds on ia64 doesn't
> mean that is works correctly..
> 
> many thanks
> anton
_______________________________________________
[email protected] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ia64
To unsubscribe, send any mail to "[email protected]"
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.