Herminia, http://es.geocities.com/numb8877 Shauna Carlton
After announcing they cleaned $1,000,000.00 worth of debt off their books, investors start rally !! **INVESTOR WATCH ISSUED FOR TUESDAY 17th, BIG MOVE COULD HAPPEN** SYMBOL: MWIS.OB Friday Close: $0.165 Friday Volume: 120,000 Short Term: $0.50 - $0.75 Long Term: $1.50 - $1.75 With Volume up and the forward movement of this great company, we believe we will see HUGE increase in price tuesday. Get your buy in first thing and get what you can before it climbs. Be sure you read the release below and comments from the Diector of Syntek Capital, then, get on MWIS first thing Tuesday Morning! Past Venture Capital Investor Agreed to Waive Old Debt in Exchange for Restricted Shares Jan 9, 2006 8:14:00 AM m-Wise, Inc. (OTCBB:MWIS), a leading technology provider of mobile content solutions for operators, ASPs and content providers, today announced that venture capital firm Syntek Capital, A.G. has entered into a termination and release agreement converting $1 million of debt to m-Wise common stock. Under the terms of the agreement, m-Wise will issue a minimum of 5,561,994 shares of common stock in exchange for terminating m-Wise's 3.5 year-old debt to Syntek Capital. The conversion of this debt was for restricted shares at market value with no discount relative to the 30 days average trading price of the common stock. Furthermore, m-Wise will issue Syntek a warrant of 5,263,158 shares of common stock at an exercise price of $0.19 per share, which can be exercised for up to a period of three years. Shay Ben-Asulin, chairman of m-Wise said, "We are very happy that a strategic investor like Syntek Capital saw the opportunity in our current stock price and took a long-term position in m-Wise. The management of m-Wise believes that increasing our shareholder's equity, coupled with completing several business transactions shortly, will result in excellent return to Syntek and all our shareholders." Ronni Benatoff, director of Syntek Capital said, "We are pleased to begin the New Year confirming our support to m-Wise. Syntek Capital has a strategy to investing only in companies with solid core and sustainable businesses. We have long recognized the potential of m-Wise's technology and believe in its future growth potential." ..Whatever you do WATCH MWIS...
[-- Attachment #1: Type: text/plain, Size: 511 bytes --] Dear Homeowner, You have been pre-approved for a $402,000 Home Loan at a Record Low Fixed Rate. This offer is being extended to you unconditionally and your credit is in no way a factor. To take Advantage of this Limited Time opportunity all we ask is that you visit our Website and complete the 1 minute post Approval Form. Enter Here <http://www.mrg-now-yes.com/sp.asp> Sincerely, Esteban Tanner Regional CEO NoThanks <http://www.mrg-now-yes.com/gone.asp> [-- Attachment #2: Type: text/html, Size: 4487 bytes --]
Hello, I haven't received much traffic on this list, but I was wondering if it was still active? I am trying to compile an SWT application to run on linux using gcj. The application runs on SWT 3.0.1. Here is the command line I am using: gcj -O2 -fjni --main=com.octetstring.jdbc.ldap.browser.JdbcLdapBrowserApp dist/osgi.jar dist/swt-pi-linux.jar dist/swt-mozilla.jar dist/swt-linux.jar dist/runtime.jar dist/boot.jar dist/jface.jar dist/ldap.jar dist/runtime.jar dist/ldap.jar dist/jdbcLdap.jar dist/jdbcLdapBrowser.jar -o ldapBrowser After playing around with the ordering, I figured it was best to put osgi first, but when I try this I get the error: org/osgi/service/url/AbstractURLStreamHandlerService.java: In class `org.osgi.service.url.AbstractURLStreamHandlerService': org/osgi/service/url/AbstractURLStreamHandlerService.java: In method `org.osgi.service.url.AbstractURLStreamHandlerService.equals(java.net.UR L,java.net.URL)': org/osgi/service/url/AbstractURLStreamHandlerService.java:83: class 'java.net.URLStreamHandler' has no method named 'equals' matching signature '(Ljava/net/URL;Ljava/net/URL;)Z' org/osgi/service/url/AbstractURLStreamHandlerService.java:93: confused by earlier errors, bailing out Is there something else I need to do? I tried including rt.jar in the classpath, but gcj didn't like that very much. I know you gotten eclipse 2.1 working with gcj, I was wondering if there had been any luck with 3.0 and the 3.0 libraries. Any help would be greatly appreciated. ------------------------------------------------------------------------ -------------------------- Marc Boorshtein Sr. Software Engineer, Octet String marc.boorshtein@octetstring.com On May 10, 2004, at 6:16 PM, Anthony Green wrote:
I am very pleased to announce the new Eclipse-RPM and Eclipse-OProfile projects on Eclipse.org! Eclipse-RPM is an Eclipse-based front-end to the RPM Package Management system and provides an easy way for users to package C/C++ applications. Eclipse-OProfile is an Eclipse-based front-end to the powerful, Linux-based OProfile profiling tool. Eclipse-OProfile provides an easy way for users to profile C/C++ applications system-wide. Red Hat has donated Eclipse-RPM and Eclipse-OProfile to the Eclipse Foundation's C/C++ Development Tools (CDT) project to expand the Eclipse IDE's offerings in the C/C++ arena. Eclipse-RPM and Eclipse-OProfile will operate as contributions to the existing CDT project. For more information, downloads, documentation, and how to get involved in Eclipse-RPM and Eclipse-OProfile, please visit the respective web sites: http://dev.eclipse.org/viewcvs/index.cgi/~checkout~/org.eclipse.cdt-contrib/org.eclipse.cdt.rpm-home/index.html?cvsroot=Tools_Project http://dev.eclipse.org/viewcvs/index.cgi/~checkout~/org.eclipse.cdt-contrib/org.eclipse.cdt.oprofile-home/index.html?cvsroot=Tools_Project As you'll see on the web sites, we've created a new mailing list for developer discussion relating to these contributions: cdt-contrib-dev@eclipse.org. Please feel free to follow up with any questions about Eclipse-RPM and Eclipse-OProfile. We will be actively encouraging others to participate in Eclipse-RPM and Eclipse-OProfile development. We are committed to being extremely open, receptive, and responsive to all questions, proposals, and patches. I'm looking forward to working with all of you and I hope to see you out on the mailing list! Jeremy
well the compiler issues are pretty interesting. the best way to fix
them going forward may be to get things working on gcc 3.4, since that's
what fedora 3 will ship.
the eclipse that ships with red hat enterprise used a "3.5-ssa" snapshot
from the tree-ssa branch, but the issues surrounding this are murky: it
corresponds to a snapshot from the tree-ssa branch from before 3.4 was
released, and thus I'm not even certain that its C++/java abi
corresponds exactly to any FSF compiler that will ever be released.
Whether binaries compiled against its shared libraries will continue to
be supported by redhat is anyone's guess. Even if a recent stabilized
3.5-mainline snapshot were to be incorporated into rawhide for Eclipse
purposes, there are still questions about giving nonstandard sonames to
its shared libraries.
if you're not a gcc hacker you'll probably have more success with gcc3.4
or the older gcc-ssa snapshots that are currently in red hat enterprise.
gcc3.4 may have more issues but the ones i've found so far appear to be
more "peripheral" than what you are describing: there are problems with
the verifier, but bytecode verification can probably be trivially turned
off, for example.
3.5-ssa from RH enterprise is known to work, but it uses some hacks that
aren't good enough for the main FSF respository - presumably, it just
comments out bytecode verification entirely. Would a patch that
implements a command line switch / environment variable equivalent in
functionality to Sun Java's -Xverify:{none,all,remote} option have a
chance of making it into the main FSF gcj/libgcj repository?
Jakob Praher wrote:
>hi all,
>
>out of curiosity I was trying to build eclipse from source.
>I am using debian/unstable and did a fresh cvs co and build of gcc head,
>which is using the tree-ssa stuff and I think the otable/atable gcj
>engine already.
>
>I was able to compile the first bunch of jars successfully, but at least
>after org.apache.coyote plugin gcj segfaults with:
>
>internal compiler error: segmentation fault
>...
>
>Is there a version of gcc/gcj which is stable enough to work?
>
>Why is the compiler reporting a segfault in .java files, when the
>command line tells to build from a binary jar file?
>
>Is there any trick?
>
>thanks
>-- Jakob
>
>
>
>
hi all, out of curiosity I was trying to build eclipse from source. I am using debian/unstable and did a fresh cvs co and build of gcc head, which is using the tree-ssa stuff and I think the otable/atable gcj engine already. I was able to compile the first bunch of jars successfully, but at least after org.apache.coyote plugin gcj segfaults with: internal compiler error: segmentation fault ... Is there a version of gcc/gcj which is stable enough to work? Why is the compiler reporting a segfault in .java files, when the command line tells to build from a binary jar file? Is there any trick? thanks -- Jakob
i've been playing with building eclipse in a hybrid environment, fedora 1 with a few rpm's from fedora 2, notably: newer binutils newer libgcc gcc34-* ant and various rhug bits. et cetera. this does mean that i'm building against an older gtk2 that doesn't require patches, it seems. The sources I'm working on are eclipse-2.1.2-6 with a few patches that have already been discussed here. Where I'm falling afoul is crashes on startup in the bytecode verifier... anyone seen this? java.lang.LinkageError: unexpected exception during linking: org.eclipse.update.internal.core.Policy at java.lang.VMClassLoader.resolveClass(java.lang.Class) (/usr/lib/libgcj.so.5.0.0) at java.lang.Class.initializeClass() (/usr/lib/libgcj.so.5.0.0) at _Jv_ResolvePoolEntry(java.lang.Class, int) (/usr/lib/libgcj.so.5.0.0) at org.eclipse.update.internal.core.UpdateCore.startup() (Unknown Source) at org.eclipse.core.internal.plugins.PluginDescriptor$1.run() (/usr/lib/eclipse/plugins/org.eclipse.core.runtime_2.1.1/libruntime.so) [snip] Caused by: java.lang.NullPointerException at _Jv_BytecodeVerifier.verify_instructions_0() (/usr/lib/libgcj.so.5.0.0) at _Jv_VerifyMethod(_Jv_InterpMethod) (/usr/lib/libgcj.so.5.0.0) at _Jv_PrepareClass(java.lang.Class) (/usr/lib/libgcj.so.5.0.0) at _Jv_WaitForState(java.lang.Class, int) (/usr/lib/libgcj.so.5.0.0) at java.lang.VMClassLoader.linkClass0(java.lang.Class) (/usr/lib/libgcj.so.5.0.0) at java.lang.VMClassLoader.resolveClass(java.lang.Class) (/usr/lib/libgcj.so.5.0.0) ...29 more
On Fri, 2004-05-14 at 10:22, Keith Seitz wrote:
> So, I'm trying to do the minimal Eclipse3 migration thing. (Largely just
> let the PDE "migrate" to 3.0.) Well, I cannot seem to import any CDT
> plugins into eclipse.
Grrr. Never mind that (sorta). As everyone can tell, I'm attempting to
fix some of the oprofile problems that are now plaguing us, and Eclipse
is just making a *wee* bit difficult for me...
Of course, if anyone does have any suggestions on how to fix this, I'd
appreciate a note! :-)
Keith
Hi, I am admitting defeat on the marker thing. [After mucking with it for three days, I finally remembered why I haven't attempted this earlier.] So, I'm trying to do the minimal Eclipse3 migration thing. (Largely just let the PDE "migrate" to 3.0.) Well, I cannot seem to import any CDT plugins into eclipse. I've downloaded and unzipped the 3.0M8 build from eclipse.org. I've added the CDT 2.0M8 update site and installed that. Yet when I go to either "Import..." or Project->Preferences->PDE->Target Platform, I see none of the CDT plugins. As a result, none of my plugins can resolve any of their CDT plugin dependencies. Anyone else see this? Hints? Keith [bang, bang]
On Mon, 2004-05-10 at 15:12, Tom Tromey wrote:
> I got it building by basically s/solib/gcjlib/ in the eclipse patches.
> You need a small patch to SWT to make it build with the newer Gtk.
> Once this stuff is done, it seems to crash if you do anything real
> with it; Anthony Green claimed better success but I'm not sure under
> what conditions.
I was just running Eclipse 2 on RHEL with GCC 3.4's gij.
The only trick I had to do was to set the GCJ_PROPERTIES environment to
"gnu.gcj.runtime.VMClassLoader.library_control=never". This prevents
gij from loading .so files that were built with previous versions of
gcj. The binary compatibility ABI should fix this in the future.
Unfortunately, Eclipse would crash eventually. I think everybody is
seeing the same crash. mjw's mew line-number-in-interpreted-stack-trace
patch should help us debug this.
AG
--
Anthony Green <green@redhat.com>
Red Hat, Inc.
On Mon, May 10, 2004 at 04:12:47PM -0600, Tom Tromey wrote: > Paul> I had Eclipse building with gcc-ssa and gcc34 mostly - ISTR the > Paul> RHEL binaries were working for someone out of the box. The > Paul> issues I hit are in the archives - solib/gcjlib, various link > Paul> problems, etc. > > I got it building by basically s/solib/gcjlib/ in the eclipse patches. Yup - I've posted my patch to list before and you cast an eye on it and it seemed sane. > You need a small patch to SWT to make it build with the newer Gtk. Hmm, pretty sure got that far too. > Once this stuff is done, it seems to crash if you do anything real > with it; Anthony Green claimed better success but I'm not sure under > what conditions. IIRC I got splash and stuff working correctly then barfing on various runtime linking issues. This could be me, and I'm not overly familiar with how gcj/eclipse deals with hybrid .so/java stuff. It strikes me that it should be at least something that should go into Fedora Extras for FC2 eventually. I'll rebuild and log and try and poke people here - I've had a lot of out of channel intrest from people via jpackage and other forums for native eclipse so I would personally like to see it in fedora once all the pain is gone. Paul
Paul> I had Eclipse building with gcc-ssa and gcc34 mostly - ISTR the Paul> RHEL binaries were working for someone out of the box. The Paul> issues I hit are in the archives - solib/gcjlib, various link Paul> problems, etc. I got it building by basically s/solib/gcjlib/ in the eclipse patches. You need a small patch to SWT to make it build with the newer Gtk. Once this stuff is done, it seems to crash if you do anything real with it; Anthony Green claimed better success but I'm not sure under what conditions. Tom
On Mon, May 10, 2004 at 05:02:32PM -0300, Ricardo Gorosito wrote:
> Any news/progress about RH's Eclipse & Fedora 2? AFAIK oprifile is the
> 'stopper'.
The oprofile plugin is not really a stopper it is possible to build without as
it's an additional plugin.
I had Eclipse building with gcc-ssa and gcc34 mostly - ISTR the RHEL binaries
were working for someone out of the box. The issues I hit are in the archives
- solib/gcjlib, various link problems, etc.
I'll have another play this week sometime.
Paul
Any news/progress about RH's Eclipse & Fedora 2? AFAIK oprifile is the 'stopper'. Thanks, Ricardo.-
Phil Muldoon writes:
> Mr Cole,
>
> I just reread your original email, and it looks as though you are using
> 2.1.1-4 version of Eclipse with the Red Hat Enterprise Product. This
> list is for the community released version at sources.redhat.com/eclipse.
>
> As far as the release notes - that might be a PR; please file a PR in
> bugzilla at http://bugzilla.redhat.com. From there we can track it, and
> resolves those issues with the Release Notes.
Bugzilla bug #119504. Thanks!
Mr Cole, I just reread your original email, and it looks as though you are using 2.1.1-4 version of Eclipse with the Red Hat Enterprise Product. This list is for the community released version at sources.redhat.com/eclipse. As far as the release notes - that might be a PR; please file a PR in bugzilla at http://bugzilla.redhat.com. From there we can track it, and resolves those issues with the Release Notes. Best Regards Phil Muldoon Ronald Cole wrote: >Phil Muldoon writes: > > >>I replicated what you did. Did you do this? >> >>Windows->Preferences->Java >> >>Click on Installed JREs >> >>If there is not a JRE there called "Standard VM", click Add >> >>then inside the following fields: >> >>JRE Name type "Standard VM" without the quotes >> >>in JRE Home Directory, click the browse button and navigate to the home >>of the JRE. For example. with the SUN JRE it would be something like: >> >>/usr/java/j2sdk1.4.2_04 >> >>or whatever path to the JRE choice you have installed. >> >>Click OK on the browse window, and it should populate JRE libraries box >> >>When you click OK to close the Installed JREs window, and click OK again >>to close the preferences window. After that it (Eclipse) should want to >>rebuild your project, and it should take care of the classpath issues >> >>Did this help at all? >> >> > >Actually, it did. I downloaded and installed Sun's latest JDK and it >worked as expected. But it just won't work with IBM's JDK on the >Extras disc as Red Hat's Eclipse Release Notes indicates it should. >Has this been bugzilla bug #114354 biting me in the butt the whole >time? > >If so, then until such time as IBM fixes their JVM to work with Red >Hat's Enterprise product AND Red Hat pushes out an Extras errata, I >*STRONGLY* recommend that you change the release notes to remove IBM's >1.4.1 JRE from the list of compatible JREs! It's wasted a *LOT* of my >time incorrectly figuring that I was doing something wrong or missing >some critical step along the way! > > >
Phil Muldoon writes:
> I replicated what you did. Did you do this?
>
> Windows->Preferences->Java
>
> Click on Installed JREs
>
> If there is not a JRE there called "Standard VM", click Add
>
> then inside the following fields:
>
> JRE Name type "Standard VM" without the quotes
>
> in JRE Home Directory, click the browse button and navigate to the home
> of the JRE. For example. with the SUN JRE it would be something like:
>
> /usr/java/j2sdk1.4.2_04
>
> or whatever path to the JRE choice you have installed.
>
> Click OK on the browse window, and it should populate JRE libraries box
>
> When you click OK to close the Installed JREs window, and click OK again
> to close the preferences window. After that it (Eclipse) should want to
> rebuild your project, and it should take care of the classpath issues
>
> Did this help at all?
Actually, it did. I downloaded and installed Sun's latest JDK and it
worked as expected. But it just won't work with IBM's JDK on the
Extras disc as Red Hat's Eclipse Release Notes indicates it should.
Has this been bugzilla bug #114354 biting me in the butt the whole
time?
If so, then until such time as IBM fixes their JVM to work with Red
Hat's Enterprise product AND Red Hat pushes out an Extras errata, I
*STRONGLY* recommend that you change the release notes to remove IBM's
1.4.1 JRE from the list of compatible JREs! It's wasted a *LOT* of my
time incorrectly figuring that I was doing something wrong or missing
some critical step along the way!
I replicated what you did. Did you do this?
Windows->Preferences->Java
Click on Installed JREs
If there is not a JRE there called "Standard VM", click Add
then inside the following fields:
JRE Name type "Standard VM" without the quotes
in JRE Home Directory, click the browse button and navigate to the home
of the JRE. For example. with the SUN JRE it would be something like:
/usr/java/j2sdk1.4.2_04
or whatever path to the JRE choice you have installed.
Click OK on the browse window, and it should populate JRE libraries box
When you click OK to close the Installed JREs window, and click OK again
to close the preferences window. After that it (Eclipse) should want to
rebuild your project, and it should take care of the classpath issues
Did this help at all?
regards
phil
Ronald Cole wrote:
>I've spent the last few months looking through the supplied user
>documentation and used "The Java Developer's Guide to Eclipse" book,
>and recently upgraded to your 2.1.1-4 release.
>
>I am unable to get a simple Hello World java problem to compile and
>run.
>
>Following the instructions in Chapter 29, Exercise 2, Section 1, here
>is what I did after an absolutely clean re-install:
>
> 1. Window > Open Perspective > Java
> 2. [New Java Product] toolbar button
> 3. Entered the Project Name: com.ibm.lab.usingjdt.helloworld
> 4. [Finish] button
> 5. [New Java Class] toolbar button > Class
> 6. Entered the Class Name: HelloWorld
> 7. Selected the main method stub creation.
> 8. Unselected the inherited abstract methods creation
> 9. [Finish] button
>
>I immediately get two task errors:
>
>* The project was not built due to classpath errors (incomplete or
> involved in cycle).
>* Unbound classpath container: 'Default System Library'.
>
>10. Expand HelloWorld.java in the Package Explorer view.
>11. Select the class HelloWorld
>12. Run > Run As > Java Application
>
>I am then greeted with the error:
>
> Exception occurred during launch
> Reason:
> The specified JRE installation does not exist.
>
>Ok, so then I install both the IBMJava2 rpms from the "Extras" disc
>and follow the instructions from the "Java Development User Guide,
>Basic tutorial, Preparing the workbench" to step six to the letter!
>
>I am able to detect /opt/IBMJava2-141/jre as the Installed JRE.
>
>However, I now have a two new task errors:
>
>* The project was not built since its classpath is incomplete. Cannot
> find the class file for java.lang.Object. Fix the classpath and
> then try rebuilding this project.
>* This compilation unit indirectly references the missing type
> java.lang.Object (typically some required class file is referencing
> a type outside the classpath)
>
>So, now that I've tried reading the release notes and following the
>instructions in the documentation, I am still unable to use Eclipse to
>compile and run a simple HelloWorld java program.
>
>What am I missing or not doing?
>
>
I've spent the last few months looking through the supplied user documentation and used "The Java Developer's Guide to Eclipse" book, and recently upgraded to your 2.1.1-4 release. I am unable to get a simple Hello World java problem to compile and run. Following the instructions in Chapter 29, Exercise 2, Section 1, here is what I did after an absolutely clean re-install: 1. Window > Open Perspective > Java 2. [New Java Product] toolbar button 3. Entered the Project Name: com.ibm.lab.usingjdt.helloworld 4. [Finish] button 5. [New Java Class] toolbar button > Class 6. Entered the Class Name: HelloWorld 7. Selected the main method stub creation. 8. Unselected the inherited abstract methods creation 9. [Finish] button I immediately get two task errors: * The project was not built due to classpath errors (incomplete or involved in cycle). * Unbound classpath container: 'Default System Library'. 10. Expand HelloWorld.java in the Package Explorer view. 11. Select the class HelloWorld 12. Run > Run As > Java Application I am then greeted with the error: Exception occurred during launch Reason: The specified JRE installation does not exist. Ok, so then I install both the IBMJava2 rpms from the "Extras" disc and follow the instructions from the "Java Development User Guide, Basic tutorial, Preparing the workbench" to step six to the letter! I am able to detect /opt/IBMJava2-141/jre as the Installed JRE. However, I now have a two new task errors: * The project was not built since its classpath is incomplete. Cannot find the class file for java.lang.Object. Fix the classpath and then try rebuilding this project. * This compilation unit indirectly references the missing type java.lang.Object (typically some required class file is referencing a type outside the classpath) So, now that I've tried reading the release notes and following the instructions in the documentation, I am still unable to use Eclipse to compile and run a simple HelloWorld java program. What am I missing or not doing?
On Sat, 2004-02-28 at 14:52, Tom Tromey wrote: > Hmm, was the rawhide at built with gcj-ssa? I was under the > impression it was built with gcj34. This matters due to how > compilations are done when building eclipse -- first the eclipse java > compiler is compiled to a .so, then this is loaded into ant. If ant > and the .so aren't built with the same compiler, problems will occur. Thanks for the response, I actually went back to the older versions of ant, gcj-ssa, et. al. and it worked. Seems like that was the problem. > We'll be putting out a newer build for FC in the hopefully > not-too-distant future. Great, I'm looking forward to it. Scott
>>>>> "Scott" == J Scott Amort <jsamort@shaw.ca> writes:
Scott> I came across the SRPM for eclipse-2.1.1-4, and have been trying to get
Scott> it to compile on my FC2 test 1 system. I have the latest rawhide
Scott> versions (as of today) of the dependent gcj-ssa, ant, etc., but am
Scott> running into a problem. The build fails with:
Hmm, was the rawhide at built with gcj-ssa? I was under the
impression it was built with gcj34. This matters due to how
compilations are done when building eclipse -- first the eclipse java
compiler is compiled to a .so, then this is loaded into ant. If ant
and the .so aren't built with the same compiler, problems will occur.
We'll be putting out a newer build for FC in the hopefully
not-too-distant future.
Tom