GPL tools and proprietary software

Top Page
Attachments:
Message as email
+ (text/plain)
Delete this message
Reply to this message
Author: Smith, Stephen P (AZ75)
Date:  
Subject: GPL tools and proprietary software
Is there a position paper anywhere on the use of GPL tool (ex: gcc) and
proprietary code. For instance, can I use gcc to compile a proprietary c++
file and have the output be proprietary or is the output GPL'ed

Stephen



From Don Harrop <> Sat Dec 9 00:21:15 2000
From: Don Harrop <> (Don Harrop)
Date: Fri, 8 Dec 2000 17:21:15 -0700 (MST)
Subject: HPUX and Net::SSLeay
In-Reply-To: <>
Message-ID: <>

I changed it in the SSLeay makefile. I keep assuming that my problem is
with SSLeay because i compiled OpenSSH just fine. It uses the openssl
libraries to link against too doesn't it? It installed just fine.. No
linker errors at all. I've made a couple of changes and it still bombs
out in the same place but with a different error.

ld: Invalid loader fixup in text space needed in output file for symbol
"$005C0032" in input file "/use/local/ssl/lib/libssl.a(ssl_lib.o)"

I'm not sure what the difference is beteen that and the position
independant error I was getting earlier. Oh well.. I'm gonna go take a
weekend off and maybe I'll have a fresh perspective when I get back.

On Fri, 8 Dec 2000, Kevin Buettner wrote:

> In which package's Makefile did you change this parameter? Was it in
> Net:SSLeay or was it in the library (that Net:SSLeay needs to link
> against) that you were fighting with the other day?
>
> The question I asked above is important because Perl needs to be
> able to dynamically load (via dlopen() or the like) the extension
> modules.
>
> In my opinion, you should probably have left the LINKTYPE as dynamic.
> The library that you mentioned the other day needs to be a shared
> object compiled to be PIC to work.
>
> (Of course, I could be entirely wrong. It's been a while since I've
> done any substantial amount of work on an HP system.)
>
> Kevin