Re: pet project : LnxPorts

[René J . V . Bertin]

On Wednesday October 07 2015 20:36:24 Sven Kolja Heinemann wrote:
>  ... I don't see why anyone would install something like this on a Linux 
> distribution ...

That's fine, but I think you haven't read my full message, it should explain 
why I'm using MP to install certain things.

MP is not just a distribution system, it's also a programmatic build system 
that's much less rigid (certainly less complex) than Debuntu's equivalent. It 
also adds activation/deactivation and variants, which have no counterparts on 
any Linux distribution I am aware of, certainly not on Ubuntu.

Anyway, it's not my intention to tell anyone they ought to follow my lead, 
except *maybe* those who can relate to my motivations.

R.

___
macports-users mailing list
macports-users@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-users

Available Ports

[hbsimon]

Hi,

I am not sure if I missed something. I did a new OS/X install on my laptop
and installed Macports for El Capitan. After I tried to install my ports
such as gsed, wget, openssl, etc. I get the message Port  not
found. When I go to https://www.macports.org/ports.php?by=all, I am too
cannot list these ports, there are less ports available now as previous.

Did ports get removed or are servers are down?

Best Regards,
Horst



--
View this message in context: 
http://mac-os-forge.2317878.n4.nabble.com/Available-Ports-tp296315.html
Sent from the MacPorts - Users mailing list archive at Nabble.com.
___
macports-users mailing list
macports-users@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-users

Re: Available Ports

[Marius Schamschula]

Horst,

They are still very much here:

pluto:ports marius$ port list gsed wget openssl
gsed   @4.2.2  textproc/gsed
wget   @1.16.3 net/wget
openssl@1.0.2d devel/openssl

I’d be troubled if gsed went away, as I’m that port’s maintainer.

There is something else going on here. What does 

which port

say?

On Oct 7, 2015, at 5:48 PM, hbsimon  wrote:

> Hi,
> 
> I am not sure if I missed something. I did a new OS/X install on my laptop
> and installed Macports for El Capitan. After I tried to install my ports
> such as gsed, wget, openssl, etc. I get the message Port  not
> found. When I go to https://www.macports.org/ports.php?by=all, I am too
> cannot list these ports, there are less ports available now as previous.
> 
> Did ports get removed or are servers are down?
> 
> Best Regards,
> Horst
> 
> 
> 
> --
> View this message in context: 
> http://mac-os-forge.2317878.n4.nabble.com/Available-Ports-tp296315.html
> Sent from the MacPorts - Users mailing list archive at Nabble.com.
> ___
> macports-users mailing list
> macports-users@lists.macosforge.org
> https://lists.macosforge.org/mailman/listinfo/macports-users

Marius
--
Marius Schamschula




___
macports-users mailing list
macports-users@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-users

Re: Incompatible library version

[Jeremy Huddleston Sequoia]

It looks like you either have an outdated version of libtiff or are using 
DYLD_INSERT_LIBRARIES to shoot yourself in the foot.

What's the output of 'otool -L /opt/local/lib/libtiff.5.dylib'?

--Jeremy

> On Oct 7, 2015, at 07:06, Michel Perez  wrote:
> 
> Hello,
> 
> I got the Incompatible library version error whatever the software I lauch.
> I tried to reinstall macport but still get the following error:
> 
> dyld: Library not loaded: /opt/local/lib/libtiff.5.dylib
>   Referenced from: 
> /opt/local/Library/Frameworks/wxWidgets.framework/Versions/wxWidgets/3.0/lib/libwx_osx_cocoau_xrc-3.0.dylib
>   Reason: Incompatible library version: libwx_osx_cocoau_xrc-3.0.dylib 
> requires version 8.0.0 or later, but libtiff.5.dylib provides version 6.0.0
> Trace/BPT trap: 5
> 
> Thanks for your help
> 
> *
> Michel Perez
> Université de Lyon - INSA de Lyon
> MATEIS - UMR CNRS 5510
> 25 avenue Capelle
> 69 621 Villeurbanne Cedex
> Tel.: +33 4 72 43 80 63
> Fax.: +33 4 72 43 85 39
> Mel.: michel.pe...@insa-lyon.fr
> Web: http://michel.perez.net.free.fr
> *
> 
> ___
> macports-users mailing list
> macports-users@lists.macosforge.org
> https://lists.macosforge.org/mailman/listinfo/macports-users



smime.p7s
Description: S/MIME cryptographic signature
___
macports-users mailing list
macports-users@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-users

Re: Available Ports

[hbsimon]

Hi Marius,

I did a clean install of OS/X and MacPorts for El Capitan. I run following and 
it is running on selfupdate forever

macbook:horst horst$ sudo port list gsed wget openssl
Warning: Can't open index file for source: 
rsync://rsync.macports.org/release/tarballs/ports.tar
Error: search for portname gsed failed: No index(es) found! Have you synced 
your port definitions? Try running 'port selfupdate'.
macbook:horst horst$ sudo port selfupdate
--->  Updating MacPorts base sources using rsync
MacPorts base version 2.3.4 installed,
MacPorts base version 2.3.4 downloaded.
--->  Updating the ports tree


When I point my Browser https://www.macports.org/ports.php 
 I get  not all the ports, for example in 
Category mail I get only 1 port:


Thanks and Regards,
Horst


> On 08 Oct 2015, at 10:02, Marius Schamschula-3 [via Mac OS Forge] 
>  wrote:
> 
> Horst,
> 
> They are still very much here:
> 
> pluto:ports marius$ port list gsed wget openssl
> gsed   @4.2.2  textproc/gsed
> wget   @1.16.3 net/wget
> openssl@1.0.2d devel/openssl
> 
> I’d be troubled if gsed went away, as I’m that port’s maintainer.
> 
> There is something else going on here. What does 
> 
> which port
> 
> say?
> 
> On Oct 7, 2015, at 5:48 PM, hbsimon <[hidden email] 
> > wrote:
> 
>> Hi,
>> 
>> I am not sure if I missed something. I did a new OS/X install on my laptop
>> and installed Macports for El Capitan. After I tried to install my ports
>> such as gsed, wget, openssl, etc. I get the message Port  not
>> found. When I go to https://www.macports.org/ports.php?by=all 
>> , I am too
>> cannot list these ports, there are less ports available now as previous.
>> 
>> Did ports get removed or are servers are down?
>> 
>> Best Regards,
>> Horst
>> 
>> 
>> 
>> --
>> View this message in context: 
>> http://mac-os-forge.2317878.n4.nabble.com/Available-Ports-tp296315.html 
>> 
>> Sent from the MacPorts - Users mailing list archive at Nabble.com 
>> .
>> ___
>> macports-users mailing list
>> [hidden email] 
>> https://lists.macosforge.org/mailman/listinfo/macports-users
> 
> Marius
> --
> Marius Schamschula
> 
> 
> 
> 
> 
> ___ 
> macports-users mailing list 
> [hidden email]  
> https://lists.macosforge.org/mailman/listinfo/macports-users 
> 
> 
> 
> If you reply to this email, your message will be added to the discussion 
> below:
> http://mac-os-forge.2317878.n4.nabble.com/Available-Ports-tp296315p296317.html
>  
> 
> To unsubscribe from Available Ports, click here 
> .
> NAML 
> 




--
View this message in context: 
http://mac-os-forge.2317878.n4.nabble.com/Available-Ports-tp296315p296322.html
Sent from the MacPorts - Users mailing list archive at Nabble.com.___
macports-users mailing list
macports-users@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-users

Fwd: Available Ports

[Horst Simon]

> Begin forwarded message:
> 
> From: Horst Simon 
> Subject: Re: Available Ports
> Date: 08 October 2015 11:22:26 AEDT
> To: "Marius Schamschula-3 [via Mac OS Forge]" 
> 
> 
> Hi Marius,
> 
> I did a clean install of OS/X and MacPorts for El Capitan. I run following 
> and it is running on selfupdate forever
> 
> macbook:horst horst$ sudo port list gsed wget openssl
> Warning: Can't open index file for source: 
> rsync://rsync.macports.org/release/tarballs/ports.tar 
> 
> Error: search for portname gsed failed: No index(es) found! Have you synced 
> your port definitions? Try running 'port selfupdate'.
> macbook:horst horst$ sudo port selfupdate
> --->  Updating MacPorts base sources using rsync
> MacPorts base version 2.3.4 installed,
> MacPorts base version 2.3.4 downloaded.
> --->  Updating the ports tree
> 
> 
> When I point my Browser https://www.macports.org/ports.php 
>  I get  not all the ports, for example in 
> Category mail I get only 1 port:
> 
> 
> Thanks and Regards,
> Horst
> 
> 
>> On 08 Oct 2015, at 10:02, Marius Schamschula-3 [via Mac OS Forge] 
>> > > wrote:
>> 
>> Horst,
>> 
>> They are still very much here:
>> 
>> pluto:ports marius$ port list gsed wget openssl
>> gsed   @4.2.2  textproc/gsed
>> wget   @1.16.3 net/wget
>> openssl@1.0.2d devel/openssl
>> 
>> I’d be troubled if gsed went away, as I’m that port’s maintainer.
>> 
>> There is something else going on here. What does 
>> 
>> which port
>> 
>> say?
>> 
>> On Oct 7, 2015, at 5:48 PM, hbsimon <[hidden email] 
>> > wrote:
>> 
>>> Hi,
>>> 
>>> I am not sure if I missed something. I did a new OS/X install on my laptop
>>> and installed Macports for El Capitan. After I tried to install my ports
>>> such as gsed, wget, openssl, etc. I get the message Port  not
>>> found. When I go to https://www.macports.org/ports.php?by=all 
>>> , I am too
>>> cannot list these ports, there are less ports available now as previous.
>>> 
>>> Did ports get removed or are servers are down?
>>> 
>>> Best Regards,
>>> Horst
>>> 
>>> 
>>> 
>>> --
>>> View this message in context: 
>>> http://mac-os-forge.2317878.n4.nabble.com/Available-Ports-tp296315.html 
>>> 
>>> Sent from the MacPorts - Users mailing list archive at Nabble.com 
>>> .
>>> ___
>>> macports-users mailing list
>>> [hidden email] 
>>> https://lists.macosforge.org/mailman/listinfo/macports-users 
>>> 
>> 
>> Marius
>> --
>> Marius Schamschula
>> 
>> 
>> 
>> 
>> 
>> ___ 
>> macports-users mailing list 
>> [hidden email]  
>> https://lists.macosforge.org/mailman/listinfo/macports-users 
>> 
>> 
>> 
>> If you reply to this email, your message will be added to the discussion 
>> below:
>> http://mac-os-forge.2317878.n4.nabble.com/Available-Ports-tp296315p296317.html
>>  
>> 
>> To unsubscribe from Available Ports, click here 
>> .
>> NAML 
>> 

___
macports-users mailing list
macports-users@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-users

Re: Available Ports

[Marius Schamschula]

Horst,

The first time running selfupdate after the install takes a long time. This is 
expected.

On Oct 7, 2015, at 7:12 PM, hbsimon  wrote:

> Hi Marius,
> 
> I did a clean install of OS/X and MacPorts for El Capitan. I run following 
> and it is running on selfupdate forever
> 
> macbook:horst horst$ sudo port list gsed wget openssl
> Warning: Can't open index file for source:  href="rsync://rsync.macports.org/release/tarballs/ports.tar" 
> class="">rsync://rsync.macports.org/release/tarballs/ports.tar
> Error: search for portname gsed failed: No index(es) found! Have you synced 
> your port definitions? Try running 'port selfupdate'.
> macbook:horst horst$ sudo port selfupdate
> --->  Updating MacPorts base sources using rsync
> MacPorts base version 2.3.4 installed,
> MacPorts base version 2.3.4 downloaded.
> --->  Updating the ports tree
> 
> 
> When I point my Browser https://www.macports.org/ports.php I get  not all the 
> ports, for example in Category mail I get only 1 port:
> 
>  class="">
> Thanks and Regards,
> Horst
> 
> 
>> On 08 Oct 2015, at 10:02, Marius Schamschula-3 [via Mac OS Forge] <[hidden 
>> email]> wrote:
>> 
>> Horst,
>> 
>> They are still very much here:
>> 
>> pluto:ports marius$ port list gsed wget openssl
>> gsed   @4.2.2  textproc/gsed
>> wget   @1.16.3 net/wget
>> openssl@1.0.2d devel/openssl
>> 
>> I’d be troubled if gsed went away, as I’m that port’s maintainer.
>> 
>> There is something else going on here. What does 
>> 
>> which port
>> 
>> say?
>> 
>> On Oct 7, 2015, at 5:48 PM, hbsimon <> href="x-msg://2/user/SendEmail.jtp?type=node&node=296317&i=0" 
>> target="_top" rel="nofollow" link="external" class="">[hidden email]> wrote:
>> 
>>> Hi,
>>> 
>>> I am not sure if I missed something. I did a new OS/X install on my laptop
>>> and installed Macports for El Capitan. After I tried to install my ports
>>> such as gsed, wget, openssl, etc. I get the message Port  not
>>> found. When I go to https://www.macports.org/ports.php?by=all, I am too
>>> cannot list these ports, there are less ports available now as previous.
>>> 
>>> Did ports get removed or are servers are down?
>>> 
>>> Best Regards,
>>> Horst
>>> 
>>> 
>>> 
>>> --
>>> View this message in context: 
>>> http://mac-os-forge.2317878.n4.nabble.com/Available-Ports-tp296315.html
>>> Sent from the MacPorts - Users mailing list archive at Nabble.com.
>>> ___
>>> macports-users mailing list
>>> >> target="_top" rel="nofollow" link="external" class="">[hidden email]
>>> https://lists.macosforge.org/mailman/listinfo/macports-users
>> 
>> Marius
>> --
>> Marius Schamschula
>> 
>> 
>> 
>> 
>> 
>> ___ 
>> macports-users mailing list 
>> > target="_top" rel="nofollow" link="external" class="">[hidden email] 
>> https://lists.macosforge.org/mailman/listinfo/macports-users
>> 
>> 
>> If you reply to this email, your message will be added to the discussion 
>> below:
>> http://mac-os-forge.2317878.n4.nabble.com/Available-Ports-tp296315p296317.html
>> To unsubscribe from Available Ports, click here.
>> NAML
> 
> 
> View this message in context: Re: Available Ports
> Sent from the MacPorts - Users mailing list archive at Nabble.com.
> ___
> macports-users mailing list
> macports-users@lists.macosforge.org
> https://lists.macosforge.org/mailman/listinfo/macports-users

Marius
--
Marius Schamschula




___
macports-users mailing list
macports-users@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-users

Re: Available Ports

[Horst Simon]

Hi Marius,

I posted too early, after selfupdate, I started the install of ports, but this 
still does not explain why the port list URL does not show all available ports.

Kind Regrads,
Horst
 
> On 08 Oct 2015, at 11:22, Horst Simon  wrote:
> 
> Hi Marius,
> 
> I did a clean install of OS/X and MacPorts for El Capitan. I run following 
> and it is running on selfupdate forever
> 
> macbook:horst horst$ sudo port list gsed wget openssl
> Warning: Can't open index file for source: 
> rsync://rsync.macports.org/release/tarballs/ports.tar 
> 
> Error: search for portname gsed failed: No index(es) found! Have you synced 
> your port definitions? Try running 'port selfupdate'.
> macbook:horst horst$ sudo port selfupdate
> --->  Updating MacPorts base sources using rsync
> MacPorts base version 2.3.4 installed,
> MacPorts base version 2.3.4 downloaded.
> --->  Updating the ports tree
> 
> 
> When I point my Browser https://www.macports.org/ports.php 
>  I get  not all the ports, for example in 
> Category mail I get only 1 port:
> 
> 
> Thanks and Regards,
> Horst
> 
> 
>> On 08 Oct 2015, at 10:02, Marius Schamschula-3 [via Mac OS Forge] 
>> > > wrote:
>> 
>> Horst,
>> 
>> They are still very much here:
>> 
>> pluto:ports marius$ port list gsed wget openssl
>> gsed   @4.2.2  textproc/gsed
>> wget   @1.16.3 net/wget
>> openssl@1.0.2d devel/openssl
>> 
>> I’d be troubled if gsed went away, as I’m that port’s maintainer.
>> 
>> There is something else going on here. What does 
>> 
>> which port
>> 
>> say?
>> 
>> On Oct 7, 2015, at 5:48 PM, hbsimon <[hidden email] 
>> > wrote:
>> 
>>> Hi,
>>> 
>>> I am not sure if I missed something. I did a new OS/X install on my laptop
>>> and installed Macports for El Capitan. After I tried to install my ports
>>> such as gsed, wget, openssl, etc. I get the message Port  not
>>> found. When I go to https://www.macports.org/ports.php?by=all 
>>> , I am too
>>> cannot list these ports, there are less ports available now as previous.
>>> 
>>> Did ports get removed or are servers are down?
>>> 
>>> Best Regards,
>>> Horst
>>> 
>>> 
>>> 
>>> --
>>> View this message in context: 
>>> http://mac-os-forge.2317878.n4.nabble.com/Available-Ports-tp296315.html 
>>> 
>>> Sent from the MacPorts - Users mailing list archive at Nabble.com 
>>> .
>>> ___
>>> macports-users mailing list
>>> [hidden email] 
>>> https://lists.macosforge.org/mailman/listinfo/macports-users 
>>> 
>> 
>> Marius
>> --
>> Marius Schamschula
>> 
>> 
>> 
>> 
>> 
>> ___ 
>> macports-users mailing list 
>> [hidden email]  
>> https://lists.macosforge.org/mailman/listinfo/macports-users 
>> 
>> 
>> 
>> If you reply to this email, your message will be added to the discussion 
>> below:
>> http://mac-os-forge.2317878.n4.nabble.com/Available-Ports-tp296315p296317.html
>>  
>> 
>> To unsubscribe from Available Ports, click here 
>> .
>> NAML 
>> 

___
macports-users mailing list
macports-users@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-users

Re: Available Ports

[Brandon Allbery]

On Wed, Oct 7, 2015 at 8:17 PM, hbsimon  wrote:

> I posted too early, after selfupdate, I started the install of ports, but
> this still does not explain why the port list URL does not show all
> available ports.


Sounds like port index generation on the server broke?


-- 
brandon s allbery kf8nh   sine nomine associates
allber...@gmail.com  ballb...@sinenomine.net
unix, openafs, kerberos, infrastructure, xmonadhttp://sinenomine.net
___
macports-users mailing list
macports-users@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-users

Re: Available Ports

[Ryan Schmidt]

On Oct 7, 2015, at 19:12, hbsimon wrote:
> 
> When I point my Browser https://www.macports.org/ports.php I get  not all the 
> ports, for example in Category mail I get only 1 port:

Yup, that page shows there are 913 ports total, when in fact there should be 
over 24,000 ports total. 

Possibly some port is written wrong, which would cause port index to fail. Or 
maybe another it failed for another reason. The Mac OS Forge admin should have 
received an email explaining the failure. ___
macports-users mailing list
macports-users@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-users

Re: Available Ports

[Manfred Antar]

> On Oct 7, 2015, at 6:11 PM, Ryan Schmidt  wrote:
> 
> On Oct 7, 2015, at 19:12, hbsimon wrote:
> 
>> When I point my Browser https://www.macports.org/ports.php I get  not all 
>> the ports, for example in Category mail I get only 1 port:
> 
> Yup, that page shows there are 913 ports total, when in fact there should be 
> over 24,000 ports total. 
> 
> Possibly some port is written wrong, which would cause port index to fail. Or 
> maybe another it failed for another reason. The Mac OS Forge admin should 
> have received an email explaining the failure. 
> ___
> macports-users mailing list
> macports-users@lists.macosforge.org
> https://lists.macosforge.org/mailman/listinfo/macports-users

I’m seeing something wierd here too:

(macports)3529}port -v sync
--->  Updating the ports tree
Synchronizing local ports tree from 
rsync://rsync.macports.org/release/tarballs/ports.tar
receiving file list ... done
ports.tar

sent 55526 bytes  received 112 bytes  22255.20 bytes/sec
total size is 62689280  speedup is 1126.73
receiving file list ... done
ports.tar.rmd160

sent 64 bytes  received 117 bytes  120.67 bytes/sec
total size is 512  speedup is 2.83
Creating port index in 
/opt/local/var/macports/sources/rsync.macports.org/release/tarballs/ports
Warning: failed to open old entry for devel/dbus-python, making a new one
Adding port devel/dbus-python
Adding subport dbus-python27
Adding subport dbus-python34
Failed to parse file devel/dbus-python/Portfile with subport 'dbus-python35': 
couldn't execute "/opt/local/bin/python3.5-config": no such file or directory
Adding subport dbus-python24
Adding subport dbus-python25
Adding subport dbus-python26
Adding subport dbus-python31
Adding subport dbus-python32
Adding subport dbus-python33

Total number of ports parsed:   10 
Ports successfully parsed:  9 
Ports failed:   1 
Up-to-date ports skipped:   24823

keep getting error about dbus-python35
I don’t have python35 installed


Manfred
___
macports-users mailing list
macports-users@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-users

Re: Available Ports

[Ryan Schmidt]

On Oct 7, 2015, at 8:18 PM, Manfred Antar wrote:

> I’m seeing something wierd here too:
> 
> (macports)3529}port -v sync
> --->  Updating the ports tree
> Synchronizing local ports tree from 
> rsync://rsync.macports.org/release/tarballs/ports.tar
> receiving file list ... done
> ports.tar
> 
> sent 55526 bytes  received 112 bytes  22255.20 bytes/sec
> total size is 62689280  speedup is 1126.73
> receiving file list ... done
> ports.tar.rmd160
> 
> sent 64 bytes  received 117 bytes  120.67 bytes/sec
> total size is 512  speedup is 2.83
> Creating port index in 
> /opt/local/var/macports/sources/rsync.macports.org/release/tarballs/ports
> Warning: failed to open old entry for devel/dbus-python, making a new one
> Adding port devel/dbus-python
> Adding subport dbus-python27
> Adding subport dbus-python34
> Failed to parse file devel/dbus-python/Portfile with subport 'dbus-python35': 
> couldn't execute "/opt/local/bin/python3.5-config": no such file or directory
> Adding subport dbus-python24
> Adding subport dbus-python25
> Adding subport dbus-python26
> Adding subport dbus-python31
> Adding subport dbus-python32
> Adding subport dbus-python33
> 
> Total number of ports parsed: 10 
> Ports successfully parsed:9 
> Ports failed: 1 
> Up-to-date ports skipped: 24823
> 
> keep getting error about dbus-python35
> I don’t have python35 installed

Thanks for reporting that!

In fact, if you had python35 installed, you wouldn't see the error.

This is a bug in the dbus-python port, and may be the cause of the index 
failure on the server.

I've filed a bug report:

https://trac.macports.org/ticket/49180

___
macports-users mailing list
macports-users@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-users

Re: Incompatible library version

[Michel Perez]

Thanks Jeremy for your reply
The output of otool command is:

mperez$ otool -L /opt/local/lib/libtiff.5.dylib
/opt/local/lib/libtiff.5.dylib:
/opt/local/lib/libtiff.5.dylib (compatibility version 8.0.0, current 
version 8.4.0)
/opt/local/lib/liblzma.5.dylib (compatibility version 8.0.0, current 
version 8.1.0)
/opt/local/lib/libjpeg.9.dylib (compatibility version 11.0.0, current 
version 11.0.0)
/opt/local/lib/libz.1.dylib (compatibility version 1.0.0, current 
version 1.2.8)
/usr/lib/libSystem.B.dylib (compatibility version 1.0.0, current 
version 1213.0.0)

I do not know if I shot myself in the foot, but it hurts: not a single macport 
program works !
Thanks again,
Michel
> On 08 Oct 2015, at 01:28, Jeremy Huddleston Sequoia  
> wrote:
> 
> It looks like you either have an outdated version of libtiff or are using 
> DYLD_INSERT_LIBRARIES to shoot yourself in the foot.
> 
> What's the output of 'otool -L /opt/local/lib/libtiff.5.dylib'?
> 
> --Jeremy
> 
>> On Oct 7, 2015, at 07:06, Michel Perez  wrote:
>> 
>> Hello,
>> 
>> I got the Incompatible library version error whatever the software I lauch.
>> I tried to reinstall macport but still get the following error:
>> 
>> dyld: Library not loaded: /opt/local/lib/libtiff.5.dylib
>>  Referenced from: 
>> /opt/local/Library/Frameworks/wxWidgets.framework/Versions/wxWidgets/3.0/lib/libwx_osx_cocoau_xrc-3.0.dylib
>>  Reason: Incompatible library version: libwx_osx_cocoau_xrc-3.0.dylib 
>> requires version 8.0.0 or later, but libtiff.5.dylib provides version 6.0.0
>> Trace/BPT trap: 5
>> 
>> Thanks for your help
>> 
>> *
>> Michel Perez
>> Université de Lyon - INSA de Lyon
>> MATEIS - UMR CNRS 5510
>> 25 avenue Capelle
>> 69 621 Villeurbanne Cedex
>> Tel.: +33 4 72 43 80 63
>> Fax.: +33 4 72 43 85 39
>> Mel.: michel.pe...@insa-lyon.fr
>> Web: http://michel.perez.net.free.fr
>> *
>> 
>> ___
>> macports-users mailing list
>> macports-users@lists.macosforge.org
>> https://lists.macosforge.org/mailman/listinfo/macports-users
> 

*
Michel Perez
Université de Lyon - INSA de Lyon
MATEIS - UMR CNRS 5510
25 avenue Capelle
69 621 Villeurbanne Cedex
Tel.: +33 4 72 43 80 63
Fax.: +33 4 72 43 85 39
Mel.: michel.pe...@insa-lyon.fr
Web: http://michel.perez.net.free.fr
*

___
macports-users mailing list
macports-users@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-users

Re: Incompatible library version

[Jeremy Sequoia]

Yep, it looks like you probably have DYLD_INSERT_LIBRARIES or DYLD_LIBRARY_PATH 
set.  Don't do that ;).  

To confirm, run 'set | grep DYLD'

Check your shell init scripts.

Sent from my iPhone...

> On Oct 7, 2015, at 22:12, Michel Perez  wrote:
> 
> Thanks Jeremy for your reply
> The output of otool command is:
> 
> mperez$ otool -L /opt/local/lib/libtiff.5.dylib
> /opt/local/lib/libtiff.5.dylib:
>   /opt/local/lib/libtiff.5.dylib (compatibility version 8.0.0, current 
> version 8.4.0)
>   /opt/local/lib/liblzma.5.dylib (compatibility version 8.0.0, current 
> version 8.1.0)
>   /opt/local/lib/libjpeg.9.dylib (compatibility version 11.0.0, current 
> version 11.0.0)
>   /opt/local/lib/libz.1.dylib (compatibility version 1.0.0, current 
> version 1.2.8)
>   /usr/lib/libSystem.B.dylib (compatibility version 1.0.0, current 
> version 1213.0.0)
> 
> I do not know if I shot myself in the foot, but it hurts: not a single 
> macport program works !
> Thanks again,
> Michel
>> On 08 Oct 2015, at 01:28, Jeremy Huddleston Sequoia  
>> wrote:
>> 
>> It looks like you either have an outdated version of libtiff or are using 
>> DYLD_INSERT_LIBRARIES to shoot yourself in the foot.
>> 
>> What's the output of 'otool -L /opt/local/lib/libtiff.5.dylib'?
>> 
>> --Jeremy
>> 
>>> On Oct 7, 2015, at 07:06, Michel Perez  wrote:
>>> 
>>> Hello,
>>> 
>>> I got the Incompatible library version error whatever the software I lauch.
>>> I tried to reinstall macport but still get the following error:
>>> 
>>> dyld: Library not loaded: /opt/local/lib/libtiff.5.dylib
>>>  Referenced from: 
>>> /opt/local/Library/Frameworks/wxWidgets.framework/Versions/wxWidgets/3.0/lib/libwx_osx_cocoau_xrc-3.0.dylib
>>>  Reason: Incompatible library version: libwx_osx_cocoau_xrc-3.0.dylib 
>>> requires version 8.0.0 or later, but libtiff.5.dylib provides version 6.0.0
>>> Trace/BPT trap: 5
>>> 
>>> Thanks for your help
>>> 
>>> *
>>> Michel Perez
>>> Université de Lyon - INSA de Lyon
>>> MATEIS - UMR CNRS 5510
>>> 25 avenue Capelle
>>> 69 621 Villeurbanne Cedex
>>> Tel.: +33 4 72 43 80 63
>>> Fax.: +33 4 72 43 85 39
>>> Mel.: michel.pe...@insa-lyon.fr
>>> Web: http://michel.perez.net.free.fr
>>> *
>>> 
>>> ___
>>> macports-users mailing list
>>> macports-users@lists.macosforge.org
>>> https://lists.macosforge.org/mailman/listinfo/macports-users
> 
> *
> Michel Perez
> Université de Lyon - INSA de Lyon
> MATEIS - UMR CNRS 5510
> 25 avenue Capelle
> 69 621 Villeurbanne Cedex
> Tel.: +33 4 72 43 80 63
> Fax.: +33 4 72 43 85 39
> Mel.: michel.pe...@insa-lyon.fr
> Web: http://michel.perez.net.free.fr
> *
> 
___
macports-users mailing list
macports-users@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-users

Incompatible library version

[Michel Perez]

Hello,

I got the Incompatible library version error whatever the software I lauch.
I tried to reinstall macport but still get the following error:

dyld: Library not loaded: /opt/local/lib/libtiff.5.dylib
  Referenced from: 
/opt/local/Library/Frameworks/wxWidgets.framework/Versions/wxWidgets/3.0/lib/libwx_osx_cocoau_xrc-3.0.dylib
  Reason: Incompatible library version: libwx_osx_cocoau_xrc-3.0.dylib requires 
version 8.0.0 or later, but libtiff.5.dylib provides version 6.0.0
Trace/BPT trap: 5

Thanks for your help

*
Michel Perez
Université de Lyon - INSA de Lyon
MATEIS - UMR CNRS 5510
25 avenue Capelle
69 621 Villeurbanne Cedex
Tel.: +33 4 72 43 80 63
Fax.: +33 4 72 43 85 39
Mel.: michel.pe...@insa-lyon.fr
Web: http://michel.perez.net.free.fr
*

___
macports-users mailing list
macports-users@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-users

Rebuild old version of port?

[Adam Dershowitz]

Is there a way that I can rebuild and reactivate an older version of a  port?  
I know about this link:  
https://trac.macports.org/wiki/howto/InstallingOlderPort 
  but the problem I 
have is a little bit different.
I have the old versions still on my computer, including the source (these were 
ports that build from source), and they are for a port that is not hosted on 
macports.  
The problem is that one of the dependents changed, so if I just activate the 
old version it fails.  So, what I want is essentially to “activate from source” 
or “rebuild @version)” since I already have the source and the port for the old 
version.  
I can just activate the old version because there is the issue of a bad link, 
so it needs to be rebuilt.  
I tried: 
sudo port install myport @myoldversion but it tried to rebuild the new version, 
which is not what I want.  
I also tried just giving the source flag:
sudo port activate -s myport @myoldversion but then it just activated the old 
version.  

I actually had no intention of yet upgrading this port, but when I upgraded one 
of the dependents , macports found that the port was now broken, and proceeded 
to download the new version of the port before rebuilding.  But, that new 
version is actually broken (for a completely unrelated reason).  So, now I 
can’t use the new version of the port, and I want to go back to the old 
version, but I can just activate it, because of the dependent issue.  So, I 
want to just have macports rebuild the old version from source.  

Any guidance?  

--Adam



___
macports-users mailing list
macports-users@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-users

pet project : LnxPorts

[René J . V . Bertin]

Morning!

OK now, don't get me wrong, this is not an announcement that I'll be forking 
off MacPorts to begin a fully supported Linux variant! :)

However, if anyone on here is like me (a developer's not to say hacker's 
mindset, and swinging back and forth between the OS X and Linux household 
members), they might see the use for being able to install select ports through 
a familiar and well-tested package/distribution system without interfering with 
the host.

Reasons this tempts *me* include MacPorts' de/activation feature, the fact that 
I've come to know its inner workings much more intimately than I probably 
should, but above all the fact I'm running a LTS version (KUbuntu 14.04) which 
means I don't always get the latest updates for things that are not 
security-related. Probably because DebUntu's packaging system can make it very 
complicated if not impossible to update individual packages that are "sitting 
in the midst of an interdependency web". For other packages it can be a b*tch 
to update the packaging scripts to accommodate a (much) newer version so that a 
build bot (PPA) can build and serve them as a personalised system update. 

One such "package" would be Qt5; Ubuntu gives us 5.2.1 and even though Qt 
guarantees that I could update to 5.5.0 with full backwards compatibility it's 
just too much work to do this via a PPA. Enter the qt5 ports I've been working 
on for about 6 months now. My Linux desktop isn't Qt5-based, so I can make do 
with a (more) recent Qt5 installed in a prefix like /opt/local . 

I had already built a few of the ports I (co)maintain on Linux, so it was easy 
enough to decide to see if Qt5 would build. There was the issue of the much 
larger amount of dependencies, though, so I decided to test an approach that 
relaxes MacPorts reproducible-build principle considerably. Did I say my Linux 
netbook is *slow*? Rather than forcing "internal" dependencies, I'd see how far 
I'd come using dependencies from the host.

A lot of that is handled through platform-specific depends_* declarations in 
the Portfile, but I also tweaked the pkgconfig port. Basically, I let 
port:pkgconfig install (through a Linux-specific variant) 
/opt/local/bin/pkgconfig that is in fact a shell wrapper that calls 
/usr/bin/pkgconfig after setting the environment such the command will look 
first in MacPorts' pkg-config database before looking in the system database.

With that, very little further modifications (but lots of patience) were needed 
to get my port:qt5-kde to build under Linux. And it works just peachy.

So for anyone still with me and interested by the above, I'm now maintaining an 
additional port repository for Linux (which should come before my regular port 
repository in /opt/local/etc/macports/sources.conf):

http://github.com/RJVB/lnxports

and the regular repository: http://github.com/RJVB/macstrop

R.
___
macports-users mailing list
macports-users@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-users

Re: pet project : LnxPorts

[Sven Kolja Heinemann]

If your Linux Distribution does not provide latest packages, you can either 
install them from 3rd party repositories or try another distribution like Arch 
Linux or Gentoo, or compile them from upstream using the userland of your 
distribution. 

MacPorts exists to make OS X a complete BSD distribution, because its missing a 
package manager and optional components. I don't see why anyone would install 
something like this on a Linux distribution that already has a fully featured 
package manager. It would just make things more complicated.

> Am 07.10.2015 um 19:59 schrieb René J.V. Bertin :
> 
> Morning!
> 
> OK now, don't get me wrong, this is not an announcement that I'll be forking 
> off MacPorts to begin a fully supported Linux variant! :)
> 
> However, if anyone on here is like me (a developer's not to say hacker's 
> mindset, and swinging back and forth between the OS X and Linux household 
> members), they might see the use for being able to install select ports 
> through a familiar and well-tested package/distribution system without 
> interfering with the host.
> 
> Reasons this tempts *me* include MacPorts' de/activation feature, the fact 
> that I've come to know its inner workings much more intimately than I 
> probably should, but above all the fact I'm running a LTS version (KUbuntu 
> 14.04) which means I don't always get the latest updates for things that are 
> not security-related. Probably because DebUntu's packaging system can make it 
> very complicated if not impossible to update individual packages that are 
> "sitting in the midst of an interdependency web". For other packages it can 
> be a b*tch to update the packaging scripts to accommodate a (much) newer 
> version so that a build bot (PPA) can build and serve them as a personalised 
> system update. 
> 
> One such "package" would be Qt5; Ubuntu gives us 5.2.1 and even though Qt 
> guarantees that I could update to 5.5.0 with full backwards compatibility 
> it's just too much work to do this via a PPA. Enter the qt5 ports I've been 
> working on for about 6 months now. My Linux desktop isn't Qt5-based, so I can 
> make do with a (more) recent Qt5 installed in a prefix like /opt/local . 
> 
> I had already built a few of the ports I (co)maintain on Linux, so it was 
> easy enough to decide to see if Qt5 would build. There was the issue of the 
> much larger amount of dependencies, though, so I decided to test an approach 
> that relaxes MacPorts reproducible-build principle considerably. Did I say my 
> Linux netbook is *slow*? Rather than forcing "internal" dependencies, I'd see 
> how far I'd come using dependencies from the host.
> 
> A lot of that is handled through platform-specific depends_* declarations in 
> the Portfile, but I also tweaked the pkgconfig port. Basically, I let 
> port:pkgconfig install (through a Linux-specific variant) 
> /opt/local/bin/pkgconfig that is in fact a shell wrapper that calls 
> /usr/bin/pkgconfig after setting the environment such the command will look 
> first in MacPorts' pkg-config database before looking in the system database.
> 
> With that, very little further modifications (but lots of patience) were 
> needed to get my port:qt5-kde to build under Linux. And it works just peachy.
> 
> So for anyone still with me and interested by the above, I'm now maintaining 
> an additional port repository for Linux (which should come before my regular 
> port repository in /opt/local/etc/macports/sources.conf):
> 
> http://github.com/RJVB/lnxports
> 
> and the regular repository: http://github.com/RJVB/macstrop
> 
> R.
> ___
> macports-users mailing list
> macports-users@lists.macosforge.org
> https://lists.macosforge.org/mailman/listinfo/macports-users
___
macports-users mailing list
macports-users@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-users