Hi,
this patch fixes an cygwin ld issue (GNU ld version 2.11.92 20011001) I've
encountered while analysing the runtime linking performance for kde.
Background:
The ld-auto-import stuff introduces additional symbols (_nm_...) in the import
library which are only needed for data exports.
Unfortuna
--- Ralf Habacker <[EMAIL PROTECTED]> wrote: > Hi,
> this patch fixes an cygwin ld issue (GNU ld version 2.11.92 20011001) I've
> encountered while analysing the runtime linking performance for kde.
>
> Background:
>
> The ld-auto-import stuff introduces additional symbols (_nm_...) in the
> im
Hi Danny,
> Yes, this looks very nice, but does it works against current CVS?
This patch is a minor change, which could be reviewed easy, but I have got
trouble using the current cvs head (binutils 2-12.xx) release from
sources.redhat.com.
It produces undefined symbols compiling dll/apps and tha
On Wed, Apr 24, 2002 at 02:09:19PM -0400, Gerald S. Williams wrote:
> I have a Cygwin SWIG package ready for review and/or upload.
> (Sorry, this is my first package. Is ITP the right keyword
> to use?)
>
> The package files can be retrieved from:
>
> http://www.users.fast.net/~gwilliams/cygwin
> Hi Danny,
>
> > Yes, this looks very nice, but does it works against current CVS?
> This patch is a minor change, which could be reviewed easy, but I have got
> trouble using the current cvs head (binutils 2-12.xx) release from
> sources.redhat.com.>
> It produces undefined symbols compiling dll
Hi all,
currently I'm working on an ordinal linking option for ld (performance benefits
for the kde-port) and have analysed the auto-import internals. While doing this
I got the knowledge to fix the bug
described in http://sources.redhat.com/ml/binutils/2002-01/msg00093.html.
$ diff -ubBp bfd/p
> -Original Message-
> From: Ralf Habacker [mailto:[EMAIL PROTECTED]]
> Sent: Friday, April 26, 2002 12:09 AM
>
> Any comments ?
Looks reasonable to me (on first glances). I'll try and have a closer
look this weekend if no-one else does.
Rob
Chris,
sometime ago in a conversation about cinstall and the all-in-one
setup the topic of cinstall's location was rasied. At that point I
didn't see any need to move cinstall but I'd actually like to see it
moved to the cygwin-apps repository now.
Why?
So that we can add a build de
On Thu, Apr 25, 2002 at 01:32:47PM +0200, Ralf Habacker wrote:
>> Hi Danny,
>>
>> > Yes, this looks very nice, but does it works against current CVS?
>> This patch is a minor change, which could be reviewed easy, but I have got
>> trouble using the current cvs head (binutils 2-12.xx) release from
On Fri, Apr 26, 2002 at 01:32:08AM +1000, Robert Collins wrote:
> sometime ago in a conversation about cinstall and the all-in-one
>setup the topic of cinstall's location was rasied. At that point I
>didn't see any need to move cinstall but I'd actually like to see it
>moved to the cygwi
> + // RH: prevent generating reimported functions
Do not use C++ style comments in C code. It is non-portable.
>
> > + // RH: prevent generating reimported functions
>
> Do not use C++ style comments in C code. It is non-portable.
Don't you mean C99 style comments?
Would be portable if the world adopted a standard now 2 years old...
> -Original Message-
> > From: Ralf Habacker [mailto:[EMAIL PROTECTED]]
> > Sent: Friday, April 26, 2002 12:09 AM
> >
> > Any comments ?
>
> Looks reasonable to me (on first glances). I'll try and have a closer
> look this weekend if no-one else does.
Perhaps it helps, if I tell some deta
> Don't you mean C99 style comments?
If I had meant C99, I would have said C99.
> Would be portable if the world adopted a standard now 2 years old...
You may dream all you like, but "portable" means "works on all the
systems we support". We cannot control the systems. We can control
our sou
Hi all,
I have applied the patch to the latest cvs release:
bfd/ChangeLog---
2002-04-25 Ralf Habacker <[EMAIL PROTECTED]>
* peXXigen.c (pe_print_idata): bugfix for segfault in
displaying auto-import image-import-descriptors
bfd/peXXige
Obviously, more than just the FTP server was messed up. While
fixing a problem with their web-based HTML editing system, my
ISP somehow managed to delete all of my files AND change my
FTP password. >:o
Perhaps it's a blessing in disguise. Since you hadn't gotten
it yet, I took this opportunity to
> Do not use C++ style comments in C code. It is non-portable.
>
This is an updated patch against the current cvs release and without c++
comments and a (I hope) propper changeLog entry.
2002-04-25 Ralf Habacker <[EMAIL PROTECTED]>
* pe-dll.cc (autofilter_symbolprefixlist): don't ex
In theory, it looks good. However, have you tested the following:
a) build a dll using an unmodified ld.
b) build an app that uses that dll, and which accesses both a function
export and a data export from the dll.
c) rebuild the dll using your modified ld.
d) does the app still work, without re
> On Thu, Apr 25, 2002 at 01:32:47PM +0200, Ralf Habacker wrote:
> >> Hi Danny,
> >>
> >> > Yes, this looks very nice, but does it works against current CVS?
> >> This patch is a minor change, which could be reviewed easy, but I have got
> >> trouble using the current cvs head (binutils 2-12.xx) r
> Can anybody tell me which cvs version is the last stable ? I have tried to
> checkout binutils with date 2001/12/31, but got compiling errors.
Compiling errors are fixed (was an overseen cvs conflict, but the problem still
remains).
So it seems to me, that the last official binutils release wa
--- Ralf Habacker <[EMAIL PROTECTED]> wrote: >
> > Can anybody tell me which cvs version is the last stable ? I have tried to
> > checkout binutils with date 2001/12/31, but got compiling errors.
>
> Compiling errors are fixed (was an overseen cvs conflict, but the problem
> still
> remains).
>
> ld was broken between 16 Dec (works) and 17 Dec (doesn't). The breakage was
> reported to binutils list in January. I think, the problem is with merging of
> sections in pe-dll.c in make_head() when making implib.
2001-12-17 Alan Modra <[EMAIL PROTECTED]>
* emultempl/elf32.em (gld${
>
> * emultempl/pe.em (gld_${EMULATION_NAME}_place_orphan): Likewise.
>
> Then this file could only be affected
>
When you take a look at the following changelog entry I assume, that this isn't
the problem, because there are only 4 changed lines, much more change
The GCC version 2.95.3-5 come with cygwin version 1.3.10 as a package cancompile C source file with DOS end-of-line character. However, the GCC built by myself can not compile DOS C file correctly.Here is the C source file:1 #define ABC 1,\2 2,\3
last official release ?
> >
> > Ralf
> >
>
> ld was broken between 16 Dec (works) and 17 Dec (doesn't). The breakage was
> reported to binutils list in January. I think, the problem is with merging of
> sections in pe-dll.c in make_head() when making implib.
>
I hav
> -Original Message-
> From: Christopher Faylor [mailto:[EMAIL PROTECTED]]
> Sent: Friday, April 26, 2002 1:42 AM
> To: [EMAIL PROTECTED]
> Subject: Re: cinstall location
>
>
> On Fri, Apr 26, 2002 at 01:32:08AM +1000, Robert Collins wrote:
> > sometime ago in a conversation about
> ld was broken between 16 Dec (works) and 17 Dec (doesn't). The breakage was
> reported to binutils list in January. I think, the problem is with merging of
> sections in pe-dll.c in make_head() when making implib.
>
Another question: Does bfd have a debug mode or something else ?
Ralf
On Fri, Apr 26, 2002 at 08:01:46AM +1000, Robert Collins wrote:
>
>
>> -Original Message-
>> From: Christopher Faylor [mailto:[EMAIL PROTECTED]]
>> Sent: Friday, April 26, 2002 1:42 AM
>> To: [EMAIL PROTECTED]
>> Subject: Re: cinstall location
>>
>>
>> On Fri, Apr 26, 2002 at 01:32:08AM
old - undefined reference error
> 4 new new - undefined reference error
>
> auto-imported data
> linking dll app
>
> 5 old old - no problems
> 6 old new - BFD 2.12.90 20020425 internal error,
> 7 new old - undefined reference error
> 8 new new - undefined reference error
>
This is an email for the archives...
The location of the cygwin 'setup.exe' aka cinstall sources, has moved.
The old location was /cvs/src/winsup/cinstall, the new location is
/cvs/cygwin-apps/setup.
The HEAD branch will be fixed shortly to compile outside the winsup
tree. The setup200202 and o
>
> You may dream all you like, but "portable" means "works on all the
> systems we support". We cannot control the systems. We can control
> our sources. Portability precludes //-style comments in binutils.
Well - personally I thought you had gcc to support all your platforms, which
for ages
On Thu, Apr 25, 2002 at 01:59:57PM -0700, Bernard Chow wrote:
>The GCC version 2.95.3-5 come with cygwin version 1.3.10 as a package can
>compile C source file with DOS end-of-line character. However, the GCC
>built by myself can not compile DOS C file correctly.
Please read the description fo
To build setup we need:
a mingw bz2lib
a mingw zlib
w32api
in the future (soon I hope):
a mingw libstdc++ (and any dependencies it has).
So,
I've made a copy of bz2lib from src/winsup/bz2lib to set/bz2lib, and
adjusted accordingly.
A second issue is that I cannot get configure to play nice in th
> Well - personally I thought you had gcc to support all your
> platforms, which for ages has supported either style of
> comment... there's only a few relics I've run across which were
> barely even functional as compilers that didn't support it :)
gcc and binutils are the two packages that are
On Fri, Apr 26, 2002 at 01:03:05PM +1000, Robert Collins wrote:
>To build setup we need:
>a mingw bz2lib
>a mingw zlib
>w32api
>in the future (soon I hope):
>a mingw libstdc++ (and any dependencies it has).
>
>So,
>I've made a copy of bz2lib from src/winsup/bz2lib to set/bz2lib, and
>adjusted acco
> -Original Message-
> From: Christopher Faylor [mailto:[EMAIL PROTECTED]]
> Sent: Friday, April 26, 2002 1:19 PM
> >So,
> >I've made a copy of bz2lib from src/winsup/bz2lib to set/bz2lib, and
> >adjusted accordingly.
>
> Ack. Duplication. Duplication bad.
Yup.
> Here was a good
On Fri, Apr 26, 2002 at 01:44:32PM +1000, Robert Collins wrote:
>> 2) The above won't work in a cross build environment. You could say
>>CC='i686-pc-cygwin-gcc -mno-cygwin'..., I guess.
>
>for cross compiles:
>../setup/configure --host=i686-pc-mingw32 --build-i686-pc-linux
>should do it (ass
Robert Collins wrote:
> Yes. I even documented all this some time back on
> http://www.cygwin.com/ml/cygwin-apps/2001-11/msg00634.html, but
> predicatably enough, no patches where forthcoming. Probably due to the
> complete lack of a prebuilt bz2lib for mingw (that my cursory searches
> have look
> A second issue is that I cannot get configure to play nice in the new
> location without updating to 2.5x. That doesn't concern me, does it
> concern anyone else?
Not me.
> On a separate but related topic, I'd like to automakeise (is that a
> word) setup - if there are no objections from the o
> -Original Message-
> From: Christopher Faylor [mailto:[EMAIL PROTECTED]]
> Sent: Friday, April 26, 2002 2:07 PM
> To: [EMAIL PROTECTED]
> Subject: Re: setup changes to build standalone
>
>
> On Fri, Apr 26, 2002 at 01:44:32PM +1000, Robert Collins wrote:
> >> 2) The above won't work
> -Original Message-
> From: Charles Wilson [mailto:[EMAIL PROTECTED]]
> Sent: Friday, April 26, 2002 2:12 PM
> https://sourceforge.net/projects/mingwrep/
Thanks.
> >>I wonder if we need a "mingw-libs" package.
> >>
> >
> > Yes, please, please, yes. I would really really love
> -Original Message-
> From: Robert Collins
> Sent: Friday, April 26, 2002 1:03 PM
> To: Cygwin-Apps
> Subject: setup changes to build standalone
>
>
> To build setup we need:
> a mingw bz2lib
> a mingw zlib
and a mingw getopt. For now I'm putting this in the setup directory, but
I'll
> -Original Message-
> From: Robert Collins
> Sent: Friday, April 26, 2002 3:28 PM
> To: Robert Collins; Cygwin-Apps
> Subject: RE: setup changes to build standalone
>
>
>
>
> > -Original Message-
> > From: Robert Collins
> > Sent: Friday, April 26, 2002 1:03 PM
> > To: Cygw
Ok, the first build of the new location setup.exe is available at:
http://www.cygwin.com/setup-snapshots/setup-newlocation.exe.
Please report any aberrant behaviour ASAP.
"Works for me" :}.
Rob
44 matches
Mail list logo
