Yes, ppc 64

On Thu, Mar 25, 2010 at 10:02 AM, Paul Lindner <[email protected]> wrote:

> You might try grabbing the EPEL version of 1.2.8  It built and tested
> without problems:
>
> http://koji.fedoraproject.org/koji/buildinfo?buildID=115778
>
> <http://koji.fedoraproject.org/koji/buildinfo?buildID=115778>I have not
> updated the EPEL build to 1.4.4 yet, and probably won't get to it for while
> (I was waiting for 1.4.5 before doing a rebuild...)  Also, is this a 64 bit
> PPC machine?  That might account for the issues you're facing..
>
>
> On Thu, Mar 25, 2010 at 5:53 AM, Gustavo Aquino 
> <[email protected]>wrote:
>
>> Hi Paul,
>>
>> I'm running Red Hat Enterprise 5.3.
>>
>> This is my environment.
>>
>> #* cat /proc/meminfo *
>> MemTotal:     12527936 kB
>> MemFree:       9049344 kB
>> Buffers:        642560 kB
>> Cached:        2407168 kB
>> SwapCached:          0 kB
>> Active:        1013568 kB
>> Inactive:      2227072 kB
>> HighTotal:           0 kB
>> HighFree:            0 kB
>> LowTotal:     12527936 kB
>> LowFree:       9049344 kB
>> SwapTotal:    12484480 kB
>> SwapFree:     12484480 kB
>> Dirty:            2432 kB
>> Writeback:           0 kB
>> AnonPages:      190208 kB
>> Mapped:          46208 kB
>> Slab:           201536 kB
>> PageTables:       9856 kB
>> NFS_Unstable:        0 kB
>> Bounce:              0 kB
>> CommitLimit:  18748416 kB
>> Committed_AS:   536960 kB
>> VmallocTotal: 8589934592 kB
>> VmallocUsed:     11008 kB
>> VmallocChunk: 8589922432 kB
>> HugePages_Total:     0
>> HugePages_Free:      0
>> HugePages_Rsvd:      0
>> Hugepagesize:    16384 kB
>>
>> *# cat /proc/cpuinfo *
>> processor : 0
>> cpu : POWER6 (architected), altivec supported
>> clock : 4204.000000MHz
>> revision : 3.2 (pvr 003e 0302)
>>
>> processor : 1
>> cpu : POWER6 (architected), altivec supported
>> clock : 4204.000000MHz
>> revision : 3.2 (pvr 003e 0302)
>>
>> processor : 2
>> cpu : POWER6 (architected), altivec supported
>> clock : 4204.000000MHz
>> revision : 3.2 (pvr 003e 0302)
>>
>> processor : 3
>> cpu : POWER6 (architected), altivec supported
>> clock : 4204.000000MHz
>> revision : 3.2 (pvr 003e 0302)
>>
>> timebase : 512000000
>> platform : pSeries
>> machine : CHRP IBM,8204-E8A
>>
>> *# uname -a*
>> Linux srv... 2.6.18-164.11.1.el5 #1 SMP Wed Jan 6 13:31:32 EST 2010 ppc64
>> ppc64 ppc64 GNU/Linux
>>
>>
>> Regards.
>>
>>
>>
>> On Thu, Mar 25, 2010 at 9:46 AM, Paul Lindner <[email protected]> wrote:
>>
>>> memcached builds and tests without problems on fedora ppc:
>>>
>>>
>>> http://kojipkgs.fedoraproject.org/packages/memcached/1.4.4/1.fc12/data/logs/ppc/
>>>
>>>
>>> <http://kojipkgs.fedoraproject.org/packages/memcached/1.4.4/1.fc12/data/logs/ppc/>What
>>> distro are you trying to run memcached on?
>>>
>>>
>>> On Thu, Mar 25, 2010 at 5:35 AM, Gustavo Aquino <
>>> [email protected]> wrote:
>>>
>>>> Anybody ?
>>>>
>>>> How can I build memcached on ppc ?
>>>>
>>>> Regards.
>>>>
>>>>
>>>> On Mon, Mar 22, 2010 at 5:35 PM, Gustavo Aquino <
>>>> [email protected]> wrote:
>>>>
>>>>> Hi,
>>>>>
>>>>> On Mon, Mar 22, 2010 at 4:59 PM, Dustin <[email protected]> wrote:
>>>>>
>>>>>>
>>>>>> On Mar 22, 11:44 am, Gustavo Aquino <[email protected]> wrote:
>>>>>> > testapp: testapp.c:820: validate_response_header: Assertion
>>>>>> > `response->message.header.response.status == status' failed.
>>>>>> > make: *** [test] Aborted
>>>>>>
>>>>>>   Well, good to know you're not passing our tests in the meantime...
>>>>>>
>>>>>> > >  Perhaps run a builder?
>>>>>> http://code.google.com/p/memcached/wiki/BuildFarm
>>>>>> >
>>>>>> > Yes, I will study the possibility to help with buildfarm, today this
>>>>>> > environments are in private network, but I will study a way to put
>>>>>> one VM of
>>>>>> > this environment to buildfarm. What is HW recommendation ? ppc
>>>>>> 4.6Ghz with
>>>>>> > 2Gb is enough ?
>>>>>>
>>>>>>   Sounds like overkill.  We just need enough to do a build and run
>>>>>> through a small correctness test suite.
>>>>>>
>>>>>
>>>>> Good to know.
>>>>>
>>>>>
>>>>>>
>>>>>>  The networking isn't a huge problem.  It needs to make one outbound
>>>>>> connection to our build master and one outbound connection to a git
>>>>>> repository.
>>>>>>
>>>>>
>>>>> Yes I know and I talk about that, but I can do it now, but to long time
>>>>> I will study a way have one virtual environment for it.
>>>>>
>>>>>
>>>>>
>>>>>>
>>>>>> To unsubscribe from this group, send email to memcached+
>>>>>> unsubscribegooglegroups.com or reply to this email with the words
>>>>>> "REMOVE ME" as the subject.
>>>>>>
>>>>>
>>>>>
>>>>  To unsubscribe from this group, send email to memcached+
>>>> unsubscribegooglegroups.com or reply to this email with the words
>>>> "REMOVE ME" as the subject.
>>>>
>>>
>>>  To unsubscribe from this group, send email to memcached+
>>> unsubscribegooglegroups.com or reply to this email with the words
>>> "REMOVE ME" as the subject.
>>>
>>
>>  To unsubscribe from this group, send email to memcached+
>> unsubscribegooglegroups.com or reply to this email with the words "REMOVE
>> ME" as the subject.
>>
>
>  To unsubscribe from this group, send email to memcached+
> unsubscribegooglegroups.com or reply to this email with the words "REMOVE
> ME" as the subject.
>

To unsubscribe from this group, send email to 
memcached+unsubscribegooglegroups.com or reply to this email with the words 
"REMOVE ME" as the subject.

Reply via email to