Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com
Message-ID: <1262.201.252.23.241.1101992954.squirrel@www.activesec.biz>
Date: Thu, 2 Dec 2004 10:09:14 -0300 (ART)
Subject: RE: Problem with cygwin & xerces-2.6
From: <mchojrin AT activesec DOT biz>
To: <cygwin AT cygwin DOT com>
MIME-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: 8bit

Hi:

  I'm new to the list, so I don't really know how to post in order to
follow a conversation. I'm reading these emails through the digest, if
anyone can help me here, that would be great too.

  Anyway, I finally solved my problem by looking at the makefiles for the
xerces examples and eventually got to the same conclusion Dave points
out in his reply. But now the question I have is this: is this ld
limitation (putting the -l option after all the .o files) only for the
cygwin implementation? Because when I run the same command on a Linux,
it doesn't matter the options order, and by the way in the man pages for
ld there's nothing about placing the -l option at the end of the line...

  Well, thanks anyway.



--
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/