Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com Reply-To: Cygwin List Message-Id: <6.1.0.6.0.20040611160844.03215af0@pop.prospeed.net> X-Sender: Date: Fri, 11 Jun 2004 16:12:33 -0400 To: geneSmith , cygwin AT cygwin DOT com From: Larry Hall Subject: Re: __getreent undefined on linux app build In-Reply-To: References: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" At 02:58 PM 6/11/2004, you wrote: >I have tried to build a linux app (actually a app and a shared library) that was made for linux and works there under cygwin. Was hoping for minimal changes. First off, it seemed that I had to tell the linker the c library name with -lc. That got rid of a ton of undefined references. However, it still has undefined reference to __getreent is every file when linking the shared library. > > From reading this list, I see that __getreent comes from the cygwin1.dll at run time. I had more than cywwin1.dll on my system from misc apps and renamed them and rebooted. Still get the link error. > >I assume you can build a shared library (the docs. only seem to talk about dll's) and that a shared library can call a function in the cywin dll. > >Someone also suggested using the latest snapshot to fix this type of problem. The other day when I tried to get a new app with setup.exe it automatically loaded the "latest" gcc. > >Here is my uname -a. If cygcheck -srv is needed, let me know. Yes, it's needed. If upgrading via setup didn't solve the problem, you're missing something or still have a local conflict. The cygcheck will give at least some basic diagnostics. Output from what you're doing would also be helpful. -- Larry Hall http://www.rfk.com RFK Partners, Inc. (508) 893-9779 - RFK Office 838 Washington Street (508) 893-9889 - FAX Holliston, MA 01746 -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/