Date: Mon, 18 Dec 2017 16:27:23 +0000 (UTC)
From: Taner Tas <taner76@gmail.com>
Reply-To: Taner Tas <taner76@gmail.com>
To: Natanael Copa <ncopa@alpinelinux.org>
Cc: alpine-aports@lists.alpinelinux.org
Message-ID: <1874079718.574977.1513614443477@mail.yahoo.com>
In-Reply-To: <20171218135410.5747053e@ncopa-desktop.copa.dup.pw>
References: <20171209214953.5555-1-taner76@gmail.com> <20171218135410.5747053e@ncopa-desktop.copa.dup.pw>
Subject: Re: [alpine-aports] [PATCH] testing/advancemame: new aport
Precedence: list
MIME-Version: 1.0
Content-Type: multipart/alternative; 
	boundary="----=_Part_574976_2116215033.1513614443476"

------=_Part_574976_2116215033.1513614443476
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

=20

    On Monday, December 18, 2017, 3:54:16 PM GMT+3, Natanael Copa <ncopa@al=
pinelinux.org> wrote: =20
=20
 Hi,

Thank you for your contriubtion. Please see question below.


> +=C2=A0=C2=A0=C2=A0 make -j4

Why can this build only use 4 cores for building? Our arm server has 48
cores and our ppc64le may have up to 160 threads.

Hi,Since the package is some hefty comparing to my other contributions, I c=
ould only rise up to 4 threads during my tests due to the my Phenom X4 cpu.=
 You can adjust any reasonable value or you can just discard it in order to=
 respect your buildfarm's abuild.conf. Btw, there is no compelling reason f=
or it. The package version is 3.6 now and build parameters adjusted to avoi=
d stack protection error with this version. Should I send the patch from sc=
ratch or need to send the update patch after acceptance accordingly?
Regards.Taner =20
------=_Part_574976_2116215033.1513614443476
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<html><head></head><body><div style=3D"font-family:Helvetica Neue, Helvetic=
a, Arial, sans-serif;font-size:13px;"><div></div>
            <div><br></div><div><br></div>
           =20
            <div id=3D"ydpf0248fccyahoo_quoted_4265938474" class=3D"ydpf024=
8fccyahoo_quoted">
                <div style=3D"font-family:'Helvetica Neue', Helvetica, Aria=
l, sans-serif;font-size:13px;color:#26282a;">
                   =20
                    <div>
                        On Monday, December 18, 2017, 3:54:16 PM GMT+3, Nat=
anael Copa &lt;ncopa@alpinelinux.org&gt; wrote:
                    </div>
                    <div><br></div>
                    <div><br></div>
                    <div><div dir=3D"ltr">Hi,<br clear=3D"none"><br clear=
=3D"none">Thank you for your contriubtion. Please see question below.<br cl=
ear=3D"none"><br clear=3D"none"><br clear=3D"none">&gt; +&nbsp;&nbsp;&nbsp;=
 make -j4<br clear=3D"none"><br clear=3D"none">Why can this build only use =
4 cores for building? Our arm server has 48<br clear=3D"none">cores and our=
 ppc64le may have up to 160 threads.<div class=3D"ydpf0248fccyqt1488295812"=
 id=3D"ydpf0248fccyqtfd83085"><br clear=3D"none"><br clear=3D"none">Hi,</di=
v><div class=3D"ydpf0248fccyqt1488295812" id=3D"ydpf0248fccyqtfd83085">Sinc=
e the package is some hefty comparing to my other contributions, I could on=
ly rise up to 4 threads during my tests due to the my Phenom X4 cpu. You ca=
n adjust any reasonable value or you can just discard it in order to respec=
t your buildfarm's abuild.conf. Btw, there is no compelling reason for it. =
The package version is 3.6 now and build parameters adjusted to avoid stack=
 protection error with this version. Should I send the patch from scratch o=
r need to send the update patch after acceptance accordingly?</div><div cla=
ss=3D"ydpf0248fccyqt1488295812" id=3D"ydpf0248fccyqtfd83085"><br></div><div=
 class=3D"ydpf0248fccyqt1488295812" id=3D"ydpf0248fccyqtfd83085">Regards.</=
div><div class=3D"ydpf0248fccyqt1488295812" id=3D"ydpf0248fccyqtfd83085">Ta=
ner</div></div></div>
                </div>
            </div></div></body></html>
------=_Part_574976_2116215033.1513614443476--


---
Unsubscribe:  alpine-aports+unsubscribe@lists.alpinelinux.org
Help:         alpine-aports+help@lists.alpinelinux.org
---