From linuxhippy at gmail.com Mon Jan 12 13:53:38 2009 From: linuxhippy at gmail.com (Clemens Eisserer) Date: Mon, 12 Jan 2009 22:53:38 +0100 Subject: AWT toolkit for Mac OS X Aqua In-Reply-To: <921BE2F9-BB59-4E31-B2BE-3435BF696B38@eteks.com> References: <929825AD-4A66-42D0-A0A2-FD705C07DE3A@eteks.com> <921BE2F9-BB59-4E31-B2BE-3435BF696B38@eteks.com> Message-ID: <194f62550901121353u4b7f21do23fc33a78db216d0@mail.gmail.com> You could try to submit it as Google Summer of Code project. - Clemens 2008/9/22 Emmanuel Puybaret : > Thank you Jeremy for your suggestion. > I know SourceForge.net quite well because Sweet Home 3D, one of my Open > Source project is hosted there at http://sweethome3d.sourceforge.net . ;-) > But I don't earn money on this project through SourceForge.net, and really > wonder if some projects got enough donations for their living. > > Best regards > -- > Emmanuel Puybaret > > Le 22 sept. 08 ? 18:18, Jeremy Denton a ?crit : > >> The mechanism for setting up a project with financial support is built >> into sourceforge. You could start a project there. >> >> Jeremy >> >> >> On Sep 17, 2008, at 11:08 AM, Emmanuel Puybaret wrote: >> >>> Hi everybody, >>> >>> Time passed, and we still didn't develop anything about Aqua AWT Toolkit. >>> >>> As I said back in November 2007 >>> http://mail.openjdk.java.net/pipermail/porters-dev/2007-November/000001.html , >>> I wanted to spend some time on this, but finally I didn't have the time. >>> One good thing : I worked with JNI during 5 months this year, and this >>> will help to develop such a toolkit (but I still have a small knowledge >>> about Cocoa). >>> An other good thing for self motivation : month after month, it looks >>> like Apple won't support old architecture in JDK, and their support for Java >>> in general is worse and worse. It seems we really need OpenJDK to run on Mac >>> OS X. >>> >>> I write you today to get ideas about how to get some financial support to >>> help me contribute to this toolkit port. Any idea will be welcome. :-) >>> >>> Best regards >>> -- >>> Emmanuel PUYBARET >>> Email : puybaret at eteks.com >>> Web : http://www.eteks.com > From Kelly.Ohair at Sun.COM Wed Jan 28 11:57:25 2009 From: Kelly.Ohair at Sun.COM (Kelly O'Hair) Date: Wed, 28 Jan 2009 11:57:25 -0800 Subject: Questions about RedHat/Fedora - ld dynamic linker hash style Message-ID: <4980B8A5.8090701@sun.com> I need some advice or information, figured this alias might be the right place to ask, probably lots of gcc/ld experts listing in here. ;^) Fedora (RedHat?) seems to have a different default dynamic linker hash style, I think basically it is: ld --hash-style=gnu .. So without using one of: --hash-style=both or --hash-style=sysv The bits created won't run on systems that don't support this new hash style, like SuSE 10. We had planned on changing our formal JDK7 builds to Fedora 9 but ran into this problem, making our built bits less portable than we would like. We need to resolve this, or change our build system choice. I'd like to just add one of the options to the link lines in the OpenJDK Makefiles, but I suspect I need to be careful to only add the option when the Linux system doing the build needs it. Anybody have any ideas on how to deal with this? I suppose if we had a './configure' step it could be figured out there, but alas, we don't. Or, can you configure gcc/ld on a system to have a different default hash style? -kto From aph at redhat.com Wed Jan 28 12:34:28 2009 From: aph at redhat.com (Andrew Haley) Date: Wed, 28 Jan 2009 20:34:28 +0000 Subject: Questions about RedHat/Fedora - ld dynamic linker hash style In-Reply-To: <4980B8A5.8090701@sun.com> References: <4980B8A5.8090701@sun.com> Message-ID: <4980C154.4030403@redhat.com> Kelly O'Hair wrote: > I need some advice or information, figured this alias might be the > right place to ask, probably lots of gcc/ld experts listing in here. ;^) > > Fedora (RedHat?) seems to have a different default dynamic linker hash > style, > I think basically it is: > ld --hash-style=gnu .. > > So without using one of: > --hash-style=both or --hash-style=sysv > > The bits created won't run on systems that don't support this new hash > style, like SuSE 10. > > We had planned on changing our formal JDK7 builds to Fedora 9 but > ran into this problem, making our built bits less portable than we > would like. We need to resolve this, or change our build system > choice. > > I'd like to just add one of the options to the link lines in the > OpenJDK Makefiles, but I suspect I need to be careful to only add > the option when the Linux system doing the build needs it. > > Anybody have any ideas on how to deal with this? > I suppose if we had a './configure' step it could be figured out > there, but alas, we don't. > > Or, can you configure gcc/ld on a system to have a different default > hash style? You can do that. $ gcc -dumpspecs > specfile $ sed -i 's/hash-style=gnu/hash-style=both/' specfile $ gcc -specs=specfile hello.c This will work regardless of whether the gcc you have defaults to hash-style=gnu. Andrew. From aph at redhat.com Wed Jan 28 12:52:56 2009 From: aph at redhat.com (Andrew Haley) Date: Wed, 28 Jan 2009 20:52:56 +0000 Subject: Questions about RedHat/Fedora - ld dynamic linker hash style In-Reply-To: <4980C154.4030403@redhat.com> References: <4980B8A5.8090701@sun.com> <4980C154.4030403@redhat.com> Message-ID: <4980C5A8.5030901@redhat.com> Andrew Haley wrote: > Kelly O'Hair wrote: > >> I need some advice or information, figured this alias might be the >> right place to ask, probably lots of gcc/ld experts listing in here. ;^) >> >> Fedora (RedHat?) seems to have a different default dynamic linker hash >> style, >> I think basically it is: >> ld --hash-style=gnu .. >> >> So without using one of: >> --hash-style=both or --hash-style=sysv >> >> The bits created won't run on systems that don't support this new hash >> style, like SuSE 10. >> >> We had planned on changing our formal JDK7 builds to Fedora 9 but >> ran into this problem, making our built bits less portable than we >> would like. We need to resolve this, or change our build system >> choice. >> >> I'd like to just add one of the options to the link lines in the >> OpenJDK Makefiles, but I suspect I need to be careful to only add >> the option when the Linux system doing the build needs it. >> >> Anybody have any ideas on how to deal with this? >> I suppose if we had a './configure' step it could be figured out >> there, but alas, we don't. >> >> Or, can you configure gcc/ld on a system to have a different default >> hash style? > > You can do that. > > $ gcc -dumpspecs > specfile > $ sed -i 's/hash-style=gnu/hash-style=both/' specfile > $ gcc -specs=specfile hello.c > > This will work regardless of whether the gcc you have defaults to > hash-style=gnu. Ahh, no. That will work but it's unnecessarily nasty. Try something like this instead: if ( gcc -dumpspecs | grep hash-style=gnu > /dev/null ) then CC="gcc -Wl,-hash-style=both" else CC=gcc fi Andrew. From Kelly.Ohair at Sun.COM Wed Jan 28 14:45:16 2009 From: Kelly.Ohair at Sun.COM (Kelly O'Hair) Date: Wed, 28 Jan 2009 14:45:16 -0800 Subject: Questions about RedHat/Fedora - ld dynamic linker hash style In-Reply-To: <4980C5A8.5030901@redhat.com> References: <4980B8A5.8090701@sun.com> <4980C154.4030403@redhat.com> <4980C5A8.5030901@redhat.com> Message-ID: <4980DFFC.7030905@sun.com> Thanks Andrew, that helps. -kto Andrew Haley wrote: > Andrew Haley wrote: >> Kelly O'Hair wrote: >> >>> I need some advice or information, figured this alias might be the >>> right place to ask, probably lots of gcc/ld experts listing in here. ;^) >>> >>> Fedora (RedHat?) seems to have a different default dynamic linker hash >>> style, >>> I think basically it is: >>> ld --hash-style=gnu .. >>> >>> So without using one of: >>> --hash-style=both or --hash-style=sysv >>> >>> The bits created won't run on systems that don't support this new hash >>> style, like SuSE 10. >>> >>> We had planned on changing our formal JDK7 builds to Fedora 9 but >>> ran into this problem, making our built bits less portable than we >>> would like. We need to resolve this, or change our build system >>> choice. >>> >>> I'd like to just add one of the options to the link lines in the >>> OpenJDK Makefiles, but I suspect I need to be careful to only add >>> the option when the Linux system doing the build needs it. >>> >>> Anybody have any ideas on how to deal with this? >>> I suppose if we had a './configure' step it could be figured out >>> there, but alas, we don't. >>> >>> Or, can you configure gcc/ld on a system to have a different default >>> hash style? >> You can do that. >> >> $ gcc -dumpspecs > specfile >> $ sed -i 's/hash-style=gnu/hash-style=both/' specfile >> $ gcc -specs=specfile hello.c >> >> This will work regardless of whether the gcc you have defaults to >> hash-style=gnu. > > Ahh, no. That will work but it's unnecessarily nasty. > > Try something like this instead: > > if ( gcc -dumpspecs | grep hash-style=gnu > /dev/null ) > then > CC="gcc -Wl,-hash-style=both" > else > CC=gcc > fi > > Andrew. > >