-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Alan Lord wrote:
> You have to remove the :: to! See the first link to this problem I
> posted a dayor two back for aspell.
>
> Al
>
Al,
Thanks, that got me moving again but I quickly ran into another
problem. I did some googling and found a
Al,
OK, I tried removing what was before :: and got a different error on
that line. Let me get a before and after snapshot. I took what you said
to mean remove X from an X::Y construct. Did I understand incorrectly?
Arnie
Error from the last build:
/usr/src/secondary/jdk-build/hotspot/src/cpu/am
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Alan Lord wrote:
> Dan Nicholson wrote:
> >> /usr/src/secondary/jdk-build/hotspot/src/share/vm/runtime/os.hpp:325:
>>> error: extra qualification 'os::' on member 'exception_name'
>>
>> These "extra qualification" issues are because of gcc-4.1. There'
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Alan Lord wrote:
> Dan Nicholson wrote:
> >> /usr/src/secondary/jdk-build/hotspot/src/share/vm/runtime/os.hpp:325:
>>> error: extra qualification 'os::' on member 'exception_name'
>>
>> These "extra qualification" issues are because of gcc-4.1. There'
Dan Nicholson wrote:
>> /usr/src/secondary/jdk-build/hotspot/src/share/vm/runtime/os.hpp:325:
error: extra qualification 'os::' on member 'exception_name'
These "extra qualification" issues are because of gcc-4.1. There's a
patch in the repo, it just hasn't gotten into the book yet.
http://ww
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Dan Nicholson wrote:
> On 10/31/06, Arnie Stender <[EMAIL PROTECTED]> wrote:
>>
>> After the recent thread on JDK I decided I would make an attempt at
>> getting it running. The BLFS page looks like it is mainly aimed at i386.
>
> This is definitely t
On 10/31/06, Arnie Stender <[EMAIL PROTECTED]> wrote:
After the recent thread on JDK I decided I would make an attempt at
getting it running. The BLFS page looks like it is mainly aimed at i386.
This is definitely true. I have no idea if there are 64 bit only
patches needed, but I wouldn't be