Learn how easy it is to sync an existing GitHub or Google Code repo to a SourceForge project! See Demo

Close

#24156 CF usage issue: Solaris C compiler

closed
Chad Schwartz
5
2002-02-27
2002-01-30
Allen Barnett
No

First, let me say that the compile farm is fantastic!
I was able to clean up a few portability issues in
libEMF in less than 10 minutes on all of the Linux
and FreeBSD boxes.

However, I ran into a few problems on the Solaris
machine. First, "config.guess" from the latest
version of automake (1.5c) uses the "cc" command to
glean information about the platform. On the Solaris
machine, /usr/ucb/cc (and /opt/SUNWspro/bin/cc) seems
to hang forever. Perhaps it is waiting for a license?
Are Sun's compilers officially supported on the
compile farm system? (Anyway, I removed /usr/ucb from
my PATH and got by this problem.)

Next, I got this message from my configure script
(from autoconf 2.52):

checking whether the linker (/usr/ccs/bin/ld)
supports shared libraries...
Releases of GCC earlier than version 3.0 cannot
reliably
create self contained shared libraries on Solaris
systems, without
introducing a dependency on libgcc.a. Therefore,
libtool is disabling
-no-undefined support, which will at least allow you
to build shared
libraries. However, you may find that when you link
such libraries
into an application without using GCC, you have to
manually add
`gcc --print-libgcc-file-name` to the link command.
We urge you to
upgrade to a newer version of GCC. Another option is
to rebuild your
current GCC to use the GNU linker from GNU binutils
2.9.1 or newer.

While I didn't see this exact problem, when I
compiled libEMF as a shared object, my test codes
behaved incorrectly: namely, the constructors for
global variables in the shared library were not
invoked when the library was loaded. Do you have any
plans to upgrade the GNU compiler system on the
Solaris machine? (or maybe you can tell what I did
wrong? I'm trusting libtool to do the right thing: It
does include libgcc as mentioned in the configure
message.)

Thanks,
Allen

Discussion

  • Trae McCombs
    Trae McCombs
    2002-01-30

    • milestone: --> Second Level Support
    • summary: Compilation on Solaris --> compilation on Solaris
    • assigned_to: nobody --> moorman
     
  • Jacob Moorman
    Jacob Moorman
    2002-02-22

    • summary: compilation on Solaris --> CF usage issue: Solaris C compiler
    • assigned_to: moorman --> coax
     
  • Chad Schwartz
    Chad Schwartz
    2002-02-25

    Logged In: YES
    user_id=192470

    bash-2.03$ cat test.c
    #include <stdio.h>

    int main(void) {
    printf("Hi\n");
    return(0);
    }
    bash-2.03$
    bash-2.03$ /usr/ucb/cc test.c -o test
    bash-2.03$ ./test
    Hi

    Hrmmmm. seems to be working okay for me. ;)

    And, in regards to your gcc 3.0 stuff, sorry. I cant install a newer compiler than what comes with the distribution in question.

    If you absolutely _NEED_ gcc 3.0, you can compile it in your homedir... if you need more disk space for that allocated to you, let me know.. I'll take care of it for ya...

    go ahead and set this case to 'open' when you reply. i'm setting it to 'pending' to get it out of my queue.

     
  • Chad Schwartz
    Chad Schwartz
    2002-02-25

    • status: open --> pending
     
  • Allen Barnett
    Allen Barnett
    2002-02-26

    Logged In: YES
    user_id=9845

    Well, cc works today.

    I'll take a stab at building GCC 3.0 sometime; but
    it's not urgent.

    I think you can close this request.

    Thanks,
    Allen

     
  • Allen Barnett
    Allen Barnett
    2002-02-26

    • status: pending --> open
     
  • Chad Schwartz
    Chad Schwartz
    2002-02-27

    Logged In: YES
    user_id=192470

    Hrm. must've been something with usf-cf-sparc-solaris-1 at the time. (that server does in fact host licenses...)

    I havent fixed anything, so i'm leary.

    Anyway, reopen this if you have further issues.

     
  • Chad Schwartz
    Chad Schwartz
    2002-02-27

    • status: open --> closed