Project

General

Profile

Actions

Bug #161

closed

swig 3

Added by Guilhem Saurel almost 6 years ago. Updated almost 6 years ago.

Status:
Closed
Priority:
Low
Assignee:
-

Description

Hi,

I noticed that devel/swig is in version 2.0 (packaged by ubuntu in "swig2.0"), but some packages (like mraa) will need v3.0 when other will probably still rely on 2.0.

"swig3.0" is also available in ubuntu, so I think we should add devel/swig3.

My real problem here is that if I add "include ../../devel/swig/depend.mk" in wip/py-mraa, it complains about not finding v2.0, even if mraa needs v3.0 and that it is currently installed on my system.

Actions #1

Updated by Anthony Mallet almost 6 years ago

On Thursday 24 May 2018, at 15:30, Guilhem Saurel wrote:

"swig3.0" is also available in ubuntu, so I think we should add
devel/swig3.

I'd rather convert devel/swig to a sysdep only. swig2 should be
available on most platforms nowadays, and there is no reason to
package it in robotpkg.

My real problem here is that if I add "include
../../devel/swig/depend.mk" in wip/py-mraa, it complains about not
finding v2.0, even if mraa needs v3.0 and that it is currently
installed on my system.

Why/where/when?

For me it says this on ubuntu 16.04 & 18.04:

===> Checking dependencies for mraa-1.9.0
=> Required system package cmake>=2.6: cmake-3.5.1 found
=> Required system package g++>=3: g++-5.4.0 found
=> Required system package gcc>=3: gcc-5.4.0 found
=> Required system package libstdc++: libstdc++ found
=> Required system package pkg-config>=0.22: pkg-config-0.29.1 found
=> Required system package python27>=2.7<2.8: python27-2.7.12 found
=> Required system package swig>=1.3: swig-3.0.8 found # (or 3.0.12 on 18.04)
===> Done depends for mraa-1.9.0

Actions #2

Updated by Guilhem Saurel almost 6 years ago

Le 24/05/2018 à 15:41, Anthony Mallet a écrit :

Issue #161 has been updated by Anthony Mallet.
On Thursday 24 May 2018, at 15:30, Guilhem Saurel wrote:

"swig3.0" is also available in ubuntu, so I think we should add
devel/swig3.

I'd rather convert devel/swig to a sysdep only. swig2 should be
available on most platforms nowadays, and there is no reason to
package it in robotpkg.

Yes

My real problem here is that if I add "include
../../devel/swig/depend.mk" in wip/py-mraa, it complains about not
finding v2.0, even if mraa needs v3.0 and that it is currently
installed on my system.

Why/where/when?

For me it says this on ubuntu 16.04 & 18.04:

===> Checking dependencies for mraa-1.9.0
=> Required system package cmake>=2.6: cmake-3.5.1 found
=> Required system package g++>=3: g++-5.4.0 found
=> Required system package gcc>=3: gcc-5.4.0 found
=> Required system package libstdc++: libstdc++ found
=> Required system package pkg-config>=0.22: pkg-config-0.29.1 found
=> Required system package python27>=2.7<2.8: python27-2.7.12 found
=> Required system package swig>=1.3: swig-3.0.8 found # (or 3.0.12 on 18.04)
===> Done depends for mraa-1.9.0

Interesting, I have swig3.0 and not swig2.0, and, on xenial,

===> Checking dependencies for mraa-1.9.0
=> Required system package cmake>=2.6: cmake-3.5.1 found
=> Required system package g++>=3: g++-5.4.0 found
=> Required system package gcc>=3: gcc-5.4.0 found
=> Required system package libstdc++: libstdc++ found
=> Required system package pkg-config>=0.22: pkg-config-0.29.1 found
=> Required system package python27>=2.7<2.8: python27-2.7.12 found
ERROR: ======================================================================
ERROR: Missing system packages required for mraa-1.9.0:
ERROR:
ERROR: swig>=1.3
ERROR:
ERROR: Please use the system package management tool to install these
ERROR: dependencies. If a robotpkg version of a dependency is available,
ERROR: you can configure robotpkg.conf to use this version instead.

After installing swig2.0,
=> Required system package swig>=1.3: swig-2.0.12 found

I will check in a clean install to investigate

Actions #3

Updated by Anthony Mallet almost 6 years ago

On Thursday 24 May 2018, at 16:05, Guilhem Saurel wrote:

ERROR: Missing system packages required for mraa-1.9.0:
ERROR:
ERROR: swig>=1.3
ERROR:
ERROR: Please use the system package management tool to install these
ERROR: dependencies. If a robotpkg version of a dependency is available,
ERROR: you can configure robotpkg.conf to use this version instead.

What's in the sysdep.log ?

Actions #4

Updated by Guilhem Saurel almost 6 years ago

Le 24/05/2018 à 16:08, Anthony Mallet a écrit :> What's in the sysdep.log ?

On a clean install:

root@5c452463261a:~/robotpkg/wip/py-mraa# cat work.5c452463261a/sysdep.log
Missing system package swig>=1.3:
searching in /opt/openrobots
missing: /opt/openrobots/bin/swig
searching in /usr/local
missing: /usr/local/bin/swig
searching in /usr
missing: /usr/bin/swig
missing: /bin/swig

Please install it before continuing.
- SYSTEM_PREFIX or PREFIX.swig can be set to the installation prefix
of this package in robotpkg.conf.
- If no swig>=1.3 package can be made available in your
system, you can use the robotpkg version, by setting in robotpkg.conf
PREFER.swig= robotpkg

root@5c452463261a:~/robotpkg/wip/py-mraa# which swig
root@5c452463261a:~/robotpkg/wip/py-mraa# sw<tab><tab>
swaplabel swapoff swapon swig3.0 switch_root

Actions #5

Updated by Anthony Mallet almost 6 years ago

On Thursday 24 May 2018, at 16:17, Guilhem Saurel wrote:

root@5c452463261a:~/robotpkg/wip/py-mraa# which swig
root@5c452463261a:~/robotpkg/wip/py-mraa# sw<tab><tab> swaplabel
swapoff swapon swig3.0 switch_root

I see. I can do something to handle this situation.

However, you should probably 'apt install swig' instead of an explicit
'swig3.0'.

Actions #6

Updated by Anthony Mallet almost 6 years ago

  • Status changed from New to Closed
Actions

Also available in: Atom PDF