This is the mail archive of the newlib@sourceware.org mailing list for the newlib project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: Patch to update libtool in GCC and Src trees


This is a copy of a message sent privately to Steve, only this version does not include the following attachments:
gcc-toplevel-changelog-fragment
src-toplevel-changelog-fragment
newlib-libtool-update.changelog.bz2
add-to-toplevel.tar.gz
newlib-libtool-update.patch.bz2
Mainly because newlib-libtool-update.patch.bz2, even compressed, is 360k. Hopefully Steve will be able to integrate these with his changes and post the whole thing.


Steve Ellcey wrote:
(4) Once these questions are answered: Steve, do you want to 'absorb' this patch into your update, so it can be committed atomically?
This would be best. Steve, please post your patch again in reply to this message (I've added back binutils, gdb, and gcc mailing lists) and I'll ok it.

I am not sure I followed everthing here. Do you want me to post my last patch without Chuck's additions or should I wait, get Chuck's changes and then post the entire patch. It sounds like we need to check in my changes and Chuck's changes together in one patch so I am assuming I should wait for those and then post the whole thing.

I think you should post the entire combined patch. My piece is attached, but there are a few things you need to do, in additional to your changes, and in addition to incorporating the patch:


in the gcc tree
(1) add 'compile' from automake-1.9 to toplevel (I've put a copy in the attached 'add-to-toplevel.tar.gz' file)


in the src tree
(1) add 'compile' from automake-1.9 to toplevel
(2) remove newlib/libtool.m4
(3) apply the attached patch at the newlib/ level.

And, of course, revise and extend your ChangeLog entries for gcc-toplevel, src-toplevel, and src-newlib. (See attached)

With the addition of a patch to fix a separate, recently-introduced problem: http://www.cygwin.com/ml/newlib/2007/msg00558.html , I obtained the following results:

On cygwin-native, I successfully built a new cygwin kernel with its internal newlib. The build process did NOT create any libtool scripts, nor did configure run any of the libtool-related tests (except for the SED one).

On linux-native, I successfully built a shared newlib library, and the build process did create and use several libtool scripts.

--
Chuck


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]