public inbox for crossgcc@sourceware.org
 help / color / mirror / Atom feed
From: "Cliff Tsai" <clifftsai@minecard.com.tw>
To: "crossgcc" <crossgcc@sources.redhat.com>
Subject: Fw:  Cerate shared library problem on Cygwin!
Date: Wed, 31 Jan 2001 18:35:00 -0000	[thread overview]
Message-ID: <004b01c08bf7$348fdbc0$b200a8c0@minecard.com.tw> (raw)

 
Hi:
    
    I wanna create a simple shared library.I 
used following two method.
 
    1. use libtool:
        $libtool gcc -c 
hello.c  ->no any warning or error message
        $libtool gcc -rpath 
/usr/local/lib -o libhello.la hello.lo
        libtool: link: warning: 
undefined symbols not allowed in 
        i586-pc-cygwin 
shared library  -> is this OK?
 
     2. another method
        $gcc -fPIC -c 
hello.c
        cc1.exe: warning: -fPIC 
ignored for target(all code is position independent)
            
                
->Is this OK?
 
        $gcc -shared -o 
hello.so hello.o
        cannot export 
_bss_end__:symbol not defined.
         cannot 
export _bss_start__:symbol not defined.
        cannot export 
_data_end__:symbol not defined.
        cannot 
export _data_start__:symbol not defined.
        collect2: ld 
returned 1 exit status
        
                
    ->what do these mean,and how to solve the 
problem?
 
         I've reference the doc-"AUTOBOOK" in 
redhat website,but don't get any 
        answer,do 
any one know where to get more information about shared 
library
        and dynamic 
linker and loader?thanks!
 

    
    
 

WARNING: multiple messages have this Message-ID
From: "Cliff Tsai" <clifftsai@minecard.com.tw>
To: "crossgcc" <crossgcc@sources.redhat.com>
Subject: Fw:  Cerate shared library problem on Cygwin!
Date: Sun, 01 Apr 2001 00:00:00 -0000	[thread overview]
Message-ID: <004b01c08bf7$348fdbc0$b200a8c0@minecard.com.tw> (raw)
Message-ID: <20010401000000.3OxHrPnSr44APOwC8du8OU-ZNcfE8tCl1YT2vaHQ2Dk@z> (raw)

 
Hi:
    
    I wanna create a simple shared library.I 
used following two method.
 
    1. use libtool:
        $libtool gcc -c 
hello.c  ->no any warning or error message
        $libtool gcc -rpath 
/usr/local/lib -o libhello.la hello.lo
        libtool: link: warning: 
undefined symbols not allowed in 
        i586-pc-cygwin 
shared library  -> is this OK?
 
     2. another method
        $gcc -fPIC -c 
hello.c
        cc1.exe: warning: -fPIC 
ignored for target(all code is position independent)
            
                
->Is this OK?
 
        $gcc -shared -o 
hello.so hello.o
        cannot export 
_bss_end__:symbol not defined.
         cannot 
export _bss_start__:symbol not defined.
        cannot export 
_data_end__:symbol not defined.
        cannot 
export _data_start__:symbol not defined.
        collect2: ld 
returned 1 exit status
        
                
    ->what do these mean,and how to solve the 
problem?
 
         I've reference the doc-"AUTOBOOK" in 
redhat website,but don't get any 
        answer,do 
any one know where to get more information about shared 
library
        and dynamic 
linker and loader?thanks!
 

    
    
 

             reply	other threads:[~2001-01-31 18:35 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-01-31 18:35 Cliff Tsai [this message]
2001-02-01 13:19 ` Alexandre Oliva
2001-04-01  0:00   ` Alexandre Oliva
2001-04-01  0:00 ` Cliff Tsai

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='004b01c08bf7$348fdbc0$b200a8c0@minecard.com.tw' \
    --to=clifftsai@minecard.com.tw \
    --cc=crossgcc@sources.redhat.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).