Re: gcc-dirs - how it is supposed to work?

2017-01-02 Thread Arkadiusz Miśkiewicz
On Monday 02 of January 2017, Elan Ruusamäe wrote:
> On 02.01.2017 12:12, Arkadiusz Miśkiewicz wrote:
> > "gcc for multilib on x86_64 needs gcc x32 installed. That requires
> > gcc-dirs from both architectures"
> > 
> > so I want to install gcc x86_64 and gcc x32 on the same machine.
> 
> but aren't there multilib packages (ix86 and x32) built from gcc-x86-64
> .spec?
> 
> i.e install "gcc-x32 -n th-x64_64" not "gcc -n th-x32"
> 
> why do we have *multilib* packages then?

Ahh. With -multilib-x32 packages it installs fine.

-- 
Arkadiusz Miśkiewicz, arekm / ( maven.pl | pld-linux.org )
___
pld-devel-en mailing list
pld-devel-en@lists.pld-linux.org
http://lists.pld-linux.org/mailman/listinfo/pld-devel-en


Re: gcc-dirs - how it is supposed to work?

2017-01-02 Thread Elan Ruusamäe

On 02.01.2017 12:12, Arkadiusz Miśkiewicz wrote:

"gcc for multilib on x86_64 needs gcc x32 installed. That requires gcc-dirs
from both architectures"

so I want to install gcc x86_64 and gcc x32 on the same machine.


but aren't there multilib packages (ix86 and x32) built from gcc-x86-64 
.spec?


i.e install "gcc-x32 -n th-x64_64" not "gcc -n th-x32"

why do we have *multilib* packages then? perhaps those should be dropped 
in favour of using builds from specific arch trees?


as for the gcc-dirs problem:
i would package x32/ix86 dirs in x86_64 gcc-dirs.spec

--
glen

___
pld-devel-en mailing list
pld-devel-en@lists.pld-linux.org
http://lists.pld-linux.org/mailman/listinfo/pld-devel-en


Re: gcc-dirs - how it is supposed to work?

2017-01-02 Thread Arkadiusz Miśkiewicz
On Monday 02 of January 2017, Elan Ruusamäe wrote:
> On 02.01.2017 10:46, Arkadiusz Miśkiewicz wrote:
> > Maybe creating single noarch package with all directories for all our
> > architectures would be a better solution?
> 
> what are you doing anyway? describe the usecase then with big picture
> given can suggest actually something.

See first mail

"gcc for multilib on x86_64 needs gcc x32 installed. That requires gcc-dirs 
from both architectures"

so I want to install gcc x86_64 and gcc x32 on the same machine.

-- 
Arkadiusz Miśkiewicz, arekm / ( maven.pl | pld-linux.org )
___
pld-devel-en mailing list
pld-devel-en@lists.pld-linux.org
http://lists.pld-linux.org/mailman/listinfo/pld-devel-en


Re: gcc-dirs - how it is supposed to work?

2017-01-02 Thread Elan Ruusamäe

On 02.01.2017 10:46, Arkadiusz Miśkiewicz wrote:

Maybe creating single noarch package with all directories for all our
architectures would be a better solution?
what are you doing anyway? describe the usecase then with big picture 
given can suggest actually something.


--
glen

___
pld-devel-en mailing list
pld-devel-en@lists.pld-linux.org
http://lists.pld-linux.org/mailman/listinfo/pld-devel-en


Re: gcc-dirs - how it is supposed to work?

2017-01-02 Thread Arkadiusz Miśkiewicz
On Monday 02 of January 2017, Arkadiusz Miśkiewicz wrote:
> On Sunday 01 of January 2017, Elan Ruusamäe wrote:
> > On 01.01.2017 22:36, Arkadiusz Miśkiewicz wrote:
> > > poldek:/all-avail> just-install --test gcc-dirs-1.0-6.x32
> > > gcc-dirs-1.0-6.x32: equal version installed, skipped
> > > Nothing to do
> > 
> > poldek -i should work
> > 
> > i.e afaik:
> > just-install and poldek -i behave differently
> 
> doesn't work:
> 
> [root@carme-pld ~]# poldek -n th -n th-i686 -n th-x32 -i gcc-dirs-1.0-6.x32
> Retrieving th-i686::packages.ndir.md...
> Retrieving th-i686::packages.ndir.gz...
> .. 100.0% [14.2M (175.7K/s)]
> Retrieving th-i686::packages.ndir.dscr.gz...
> .. 100.0% [2.1M (2.1M/s)]
> Retrieving th-x32::packages.ndir.md...
> Retrieving th-x32::packages.ndir.gz...
> .. 100.0% [10.8M (2.3M/s)]
> Retrieving th-x32::packages.ndir.dscr.gz...
> .. 100.0% [1.5M (319.3K/s)]
> Loading [pndir]th-arch...
> Loading [pndir]th-noarch...
> Loading [pndir]th-i686...
> Loading [pndir]th-x32...
> 58789 packages read
> gcc-dirs-1.0-6.x32: equal version installed, skipped
> Nothing to do
> [root@carme-pld ~]# rpm -q gcc-dirs
> gcc-dirs-1.0-6.x86_64

Maybe creating single noarch package with all directories for all our 
architectures would be a better solution?

-- 
Arkadiusz Miśkiewicz, arekm / ( maven.pl | pld-linux.org )
___
pld-devel-en mailing list
pld-devel-en@lists.pld-linux.org
http://lists.pld-linux.org/mailman/listinfo/pld-devel-en


Re: gcc-dirs - how it is supposed to work?

2017-01-01 Thread Arkadiusz Miśkiewicz
On Sunday 01 of January 2017, Elan Ruusamäe wrote:
> On 01.01.2017 22:36, Arkadiusz Miśkiewicz wrote:
> > poldek:/all-avail> just-install --test gcc-dirs-1.0-6.x32
> > gcc-dirs-1.0-6.x32: equal version installed, skipped
> > Nothing to do
> 
> poldek -i should work
> 
> i.e afaik:
> just-install and poldek -i behave differently

doesn't work:

[root@carme-pld ~]# poldek -n th -n th-i686 -n th-x32 -i gcc-dirs-1.0-6.x32
Retrieving th-i686::packages.ndir.md...
Retrieving th-i686::packages.ndir.gz...
.. 100.0% [14.2M (175.7K/s)]
Retrieving th-i686::packages.ndir.dscr.gz...
.. 100.0% [2.1M (2.1M/s)]
Retrieving th-x32::packages.ndir.md...
Retrieving th-x32::packages.ndir.gz...
.. 100.0% [10.8M (2.3M/s)]
Retrieving th-x32::packages.ndir.dscr.gz...
.. 100.0% [1.5M (319.3K/s)]
Loading [pndir]th-arch...
Loading [pndir]th-noarch...
Loading [pndir]th-i686...
Loading [pndir]th-x32...
58789 packages read
gcc-dirs-1.0-6.x32: equal version installed, skipped
Nothing to do
[root@carme-pld ~]# rpm -q gcc-dirs
gcc-dirs-1.0-6.x86_64


-- 
Arkadiusz Miśkiewicz, arekm / ( maven.pl | pld-linux.org )
___
pld-devel-en mailing list
pld-devel-en@lists.pld-linux.org
http://lists.pld-linux.org/mailman/listinfo/pld-devel-en


Re: gcc-dirs - how it is supposed to work?

2017-01-01 Thread Elan Ruusamäe

On 01.01.2017 22:36, Arkadiusz Miśkiewicz wrote:

poldek:/all-avail> just-install --test gcc-dirs-1.0-6.x32
gcc-dirs-1.0-6.x32: equal version installed, skipped
Nothing to do


poldek -i should work

i.e afaik:
just-install and poldek -i behave differently

--
glen

___
pld-devel-en mailing list
pld-devel-en@lists.pld-linux.org
http://lists.pld-linux.org/mailman/listinfo/pld-devel-en


gcc-dirs - how it is supposed to work?

2017-01-01 Thread Arkadiusz Miśkiewicz

gcc for multilib on x86_64 needs gcc x32 installed. That requires gcc-dirs 
from both architectures but:

[root@carme-pld ~]# rpm -q gcc-dirs
gcc-dirs-1.0-6.x86_64
[root@carme-pld ~]# poldek -n th -n th-i686 -n th-x32
Loading [pndir]th-arch...
Loading [pndir]th-noarch...
Loading [pndir]th-i686...
Loading [pndir]th-x32...
58789 packages read
Loading [rpmdb]/var/lib/rpm...
5621 packages loaded

Welcome to the poldek shell mode. Type "help" for help with commands.

poldek:/all-avail> install --test gcc-dirs-1.0-6.x32
Processing dependencies...
gcc-dirs-1.0-6.x86_64 obsoleted by gcc-dirs-1.0-6.x32
There are 1 package to install, 1 to remove:
I gcc-dirs-1.0-6.x32
R gcc-dirs-1.0-6.x86_64
Need to get 3.6KB of archives (3.6KB to download).

^^ wants to remove x86_64 - why? lack of colored binary files in 
package?

poldek:/all-avail> just-install --test gcc-dirs-1.0-6.x32
gcc-dirs-1.0-6.x32: equal version installed, skipped
Nothing to do
poldek:/all-avail>

that also doesn't work

How is that supposed to work?

-- 
Arkadiusz Miśkiewicz, arekm / ( maven.pl | pld-linux.org )
___
pld-devel-en mailing list
pld-devel-en@lists.pld-linux.org
http://lists.pld-linux.org/mailman/listinfo/pld-devel-en