I resolved all of the errors in opal make module. I will write a guide
for other people in the near future.
Mahmood Naderan,
On 3/7/10, Mahmood Naderan <mahmood.nt@xxxxxxxxx> wrote:
> Yes I did compile the ruby with some changes but now stuck at this
> error. I will be thankfull if someone help me on this error.
>
> Mahmood Naderan,
>
> On 3/7/10, Abdullah Kayi <apokayi@xxxxxxxxxxxxxx> wrote:
>> Sorry for the confusion, I actually didn't try to compile Opal. I was
>> just trying to say that if you only need Ruby, that can be compiled
>> under gcc 4.4.1 with minor changes.
>>
>> ~AK
>>
>> Mahmood Naderan wrote:
>>> While making the Opal, I get these errors:
>>> system/pseq.h: In member function ‘cache_t* pseq_t::getDataCache()’:
>>> system/pseq.h:417: error: cannot convert
>>> ‘generic_cache_template<generic_cache_block_t>*’ to ‘cache_t*’ in
>>> return
>>> system/pseq.h: In member function ‘cache_t*
>>> pseq_t::getInstructionCache()’:
>>> system/pseq.h:421: error: cannot convert
>>> ‘generic_cache_template<generic_cache_block_t>*’ to ‘cache_t*’ in
>>> return
>>>
>>> The staements are:
>>> cache_t *getDataCache( void ) {
>>> return (l1_data_cache); // error line 417
>>> }
>>> /** get the l1 instruction cache interface */
>>> cache_t *getInstructionCache( void ) {
>>> return (l1_inst_cache); // error line 421
>>>
>>> How did you correct them in 4.4.1? Please let me know.
>>>
>>> Mahmood Naderan,
>>>
>>> On 3/5/10, Abdullah Kayi <apokayi@xxxxxxxxxxxxxx> wrote:
>>>
>>>> Just to let you know, I managed to compile Ruby with gcc 4.4.1 comes
>>>> with the latest Ubuntu.
>>>>
>>>> AK
>>>>
>>>> Mahmood Naderan wrote:
>>>>
>>>>> Thanks, I will try to make two GCCs coexist with rach other.
>>>>>
>>>>> On 3/5/10, Byn Choi <bynchoi1@xxxxxxxxxxxx> wrote:
>>>>>
>>>>>
>>>>>> You are not locked into using old ubuntu release just to use older
>>>>>> version of gcc. Different releases of gcc can coexist in a system,
>>>>>> you
>>>>>> can simply drop one in in your local directory. Simply configure GEMS
>>>>>> to use the older gcc, look at $GEMS/common/Makefile.common.
>>>>>>
>>>>>> Personally, my system gcc is 4.1.2 while I use locally installed gcc
>>>>>> 3.4.6 for GEMS. Dynamically linked libraries do not need to be
>>>>>> compiled using the same version of gcc as the GEMS modules.
>>>>>>
>>>>>> Byn
>>>>>>
>>>>>> On Mar 5, 2010, at 1:20 AM, Mahmood Naderan wrote:
>>>>>>
>>>>>>
>>>>>>
>>>>>>> Since gcc 3.4 is very old and gcc 4.5 is coming, don't you think it
>>>>>>> is
>>>>>>> much better if GEMS developers try to port their codes to newer
>>>>>>> versions (currently 4.4.3)? That gcc means we have to use ubuntu 7.1
>>>>>>> (or older) or we have to place gcc 3.4 near the new one and then
>>>>>>> force
>>>>>>> the compiler to use 3.4. The latter may caus many confliction
>>>>>>> because
>>>>>>> other c++ libraries have to be downgraded too.
>>>>>>>
>>>>>>> Mahmood Naderan,
>>>>>>>
>>>>>>> On 3/4/10, Dan Gibson <degibson@xxxxxxxx> wrote:
>>>>>>>
>>>>>>>
>>>>>>>> I'd hesitate to claim the gems-users list as 'official' support.
>>>>>>>> Inasmuch as
>>>>>>>> anything is 'supported', we use gcc 3.4.1 internally. I'm
>>>>>>>> reasonably sure
>>>>>>>> Ruby at least will compile with gcc 4.2. As I recall, Opal has some
>>>>>>>> issues
>>>>>>>> with modern gcc.
>>>>>>>>
>>>>>>>> Regards,
>>>>>>>> Dan
>>>>>>>>
>>>>>>>> On Thu, Mar 4, 2010 at 8:51 AM, Mahmood Naderan
>>>>>>>> <mahmood.nt@xxxxxxxxx>wrote:
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>> which version of GCC is officialy supported by the latest GEMS?
>>>>>>>>>
>>>>>>>>> Mahmood Naderan
>>>>>>>>> _______________________________________________
>>>>>>>>> Gems-users mailing list
>>>>>>>>> Gems-users@xxxxxxxxxxx
>>>>>>>>> https://lists.cs.wisc.edu/mailman/listinfo/gems-users
>>>>>>>>> Use Google to search the GEMS Users mailing list by adding "site:
>>>>>>>>> https://lists.cs.wisc.edu/archive/gems-users/" to your search.
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>> --
>>>>>>>> http://www.cs.wisc.edu/~gibson [esc]:wq!
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>> _______________________________________________
>>>>>>> Gems-users mailing list
>>>>>>> Gems-users@xxxxxxxxxxx
>>>>>>> https://lists.cs.wisc.edu/mailman/listinfo/gems-users
>>>>>>> Use Google to search the GEMS Users mailing list by adding
>>>>>>> "site:https://lists.cs.wisc.edu/archive/gems-users/" to your search.
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>> _______________________________________________
>>>>>> Gems-users mailing list
>>>>>> Gems-users@xxxxxxxxxxx
>>>>>> https://lists.cs.wisc.edu/mailman/listinfo/gems-users
>>>>>> Use Google to search the GEMS Users mailing list by adding
>>>>>> "site:https://lists.cs.wisc.edu/archive/gems-users/" to your search.
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>> _______________________________________________
>>>>> Gems-users mailing list
>>>>> Gems-users@xxxxxxxxxxx
>>>>> https://lists.cs.wisc.edu/mailman/listinfo/gems-users
>>>>> Use Google to search the GEMS Users mailing list by adding
>>>>> "site:https://lists.cs.wisc.edu/archive/gems-users/" to your search.
>>>>>
>>>>>
>>>>>
>>>> _______________________________________________
>>>> Gems-users mailing list
>>>> Gems-users@xxxxxxxxxxx
>>>> https://lists.cs.wisc.edu/mailman/listinfo/gems-users
>>>> Use Google to search the GEMS Users mailing list by adding
>>>> "site:https://lists.cs.wisc.edu/archive/gems-users/" to your search.
>>>>
>>>>
>>>>
>>> _______________________________________________
>>> Gems-users mailing list
>>> Gems-users@xxxxxxxxxxx
>>> https://lists.cs.wisc.edu/mailman/listinfo/gems-users
>>> Use Google to search the GEMS Users mailing list by adding
>>> "site:https://lists.cs.wisc.edu/archive/gems-users/" to your search.
>>>
>>>
>>
>> _______________________________________________
>> Gems-users mailing list
>> Gems-users@xxxxxxxxxxx
>> https://lists.cs.wisc.edu/mailman/listinfo/gems-users
>> Use Google to search the GEMS Users mailing list by adding
>> "site:https://lists.cs.wisc.edu/archive/gems-users/" to your search.
>>
>>
>
|