Re: wine-devel could not load binary

[Ryan Schmidt]

On Dec 22, 2018, at 16:06, Ryan Schmidt wrote:

> On Dec 22, 2018, at 15:33, Ryan Schmidt wrote:
> 
>> Another possible solution is to remove our wrapper -- I don't remember why 
>> it exists. When I first added the wine port 12 years ago, I said there were 
>> "font issues", but I don't remember what I meant by that:
>> 
>> https://trac.macports.org/ticket/11779#comment:2
>> 
>> I apparently fixed it by adding the wrapper script:
>> 
>> https://github.com/macports/macports-ports/commit/88d79d741bf86b96ce4fd23386d05b0f90001867
> 
> To try removing the wrapper, you could:
> 
> sudo mv /opt/local/libexec/wine/wine /opt/local/bin/wine
> 
> See if you notice any font problems or error messages with programs you run 
> using wine after that.
> 
> If you later want to undo the change, you can:
> 
> sudo port -f deactivate wine-devel && sudo port activate wine-devel

I've made this change in 4.0-rc3. If you notice any font problems or other 
errors, let me know.

gdb

[James Linder]

Hi

can anybody show me mt errant ways

I installed gdb
codesigned as per 
https://sourceware.org/gdb/wiki/BuildingOnDarwin#Giving_gdb_permission_to_control_other_processes
I get

[Haycorn] /Users/jam/nodups [510]% ggdb nodups.app/Contents/MacOS/nodups
GNU gdb (GDB) 8.0.1
Copyright (C) 2017 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later 
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
and "show warranty" for details.
This GDB was configured as "x86_64-apple-darwin17.2.0".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
.
Find the GDB manual and other documentation resources online at:
.
For help, type "help".
Type "apropos word" to search for commands related to "word"...
Reading symbols from nodups.app/Contents/MacOS/nodups...(no debugging symbols 
found)...done.
(gdb) q

[Haycorn] /Users/jam/nodups [511]% port list gdb
Warning: port definitions are more than two weeks old, consider updating them 
by running 'port selfupdate'.
gdb@8.0.1  devel/gdb

nodeps IS compiled with -g
Anybody please

James

Re: wine-devel could not load binary

[Gijs Vermeulen]

Hi Ryan,

Thank you for the fast responses and sorry for my late one.
I can confirm that 4.0-rc3 works again.
I haven't tested extensively, but if I notice anything odd I'll let you
know.

Regards,
Gijs


Op vr 28 dec. 2018 om 20:10 schreef Ryan Schmidt :

>
>
> On Dec 22, 2018, at 16:06, Ryan Schmidt wrote:
>
> > On Dec 22, 2018, at 15:33, Ryan Schmidt wrote:
> >
> >> Another possible solution is to remove our wrapper -- I don't remember
> why it exists. When I first added the wine port 12 years ago, I said there
> were "font issues", but I don't remember what I meant by that:
> >>
> >> https://trac.macports.org/ticket/11779#comment:2
> >>
> >> I apparently fixed it by adding the wrapper script:
> >>
> >>
> https://github.com/macports/macports-ports/commit/88d79d741bf86b96ce4fd23386d05b0f90001867
> >
> > To try removing the wrapper, you could:
> >
> > sudo mv /opt/local/libexec/wine/wine /opt/local/bin/wine
> >
> > See if you notice any font problems or error messages with programs you
> run using wine after that.
> >
> > If you later want to undo the change, you can:
> >
> > sudo port -f deactivate wine-devel && sudo port activate wine-devel
>
> I've made this change in 4.0-rc3. If you notice any font problems or other
> errors, let me know.
>
>

Vlc build fail

[rmgls]

hello all,

Attempting to build VLC I get the following:

:info:build  /usr/bin/install -c -m 644 icons/128x128/vlc.png 
icons/128x128/vlc-xmas.png 
'/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_multimedia_VLC/VLC/work/vlc-2.2.8/tmp/destdir/opt/local/share/icons/hicolor/128x128/apps'
:info:build  /usr/bin/install -c -m 644 icons/256x256/vlc.png 
'/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_multimedia_VLC/VLC/work/vlc-2.2.8/tmp/destdir/opt/local/share/icons/hicolor/256x256/apps'
:info:build  /usr/bin/install -c -m 644 vlc.desktop 
'/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_multimedia_VLC/VLC/work/vlc-2.2.8/tmp/destdir/opt/local/share/applications'
:info:build  /usr/bin/install -c -m 644 icons/vlc.ico 
'/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_multimedia_VLC/VLC/work/vlc-2.2.8/tmp/destdir/opt/local/share/vlc'
:info:build  /usr/bin/install -c -m 644 icons/48x48/vlc.png 
icons/48x48/vlc-xmas.png 
'/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_multimedia_VLC/VLC/work/vlc-2.2.8/tmp/destdir/opt/local/share/icons/hicolor/48x48/apps'
:info:build  /usr/bin/install -c -m 644 icons/16x16/vlc.png icons/16x16/vlc.xpm 
'/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_multimedia_VLC/VLC/work/vlc-2.2.8/tmp/destdir/opt/local/share/icons/hicolor/16x16/apps'
:info:build  /usr/bin/install -c -m 644 icons/32x32/vlc.png icons/32x32/vlc.xpm 
icons/32x32/vlc-xmas.xpm 
'/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_multimedia_VLC/VLC/work/vlc-2.2.8/tmp/destdir/opt/local/share/icons/hicolor/32x32/apps'
:info:build  ../autotools/install-sh -c -d 
'/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_multimedia_VLC/VLC/work/vlc-2.2.8/tmp/destdir/opt/local/share/vlc/utils/'
:info:build  ../autotools/install-sh -c -d 
'/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_multimedia_VLC/VLC/work/vlc-2.2.8/tmp/destdir/opt/local/share/vlc/lua/http/css/ui-lightness/images'
:info:build  ../autotools/install-sh -c -d 
'/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_multimedia_VLC/VLC/work/vlc-2.2.8/tmp/destdir/opt/local/share/doc/vlc/lua/meta/reader'
:info:build  ../autotools/install-sh -c -d 
'/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_multimedia_VLC/VLC/work/vlc-2.2.8/tmp/destdir/opt/local/lib/vlc/lua/meta/reader'
:info:build  /usr/bin/install -c utils/gnome-vlc-default.sh 
utils/audio-vlc-default.sh utils/video-vlc-default.sh 
'/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_multimedia_VLC/VLC/work/vlc-2.2.8/tmp/destdir/opt/local/share/vlc/utils/'
:info:build  /usr/bin/install -c -m 644  lua/meta/reader/README.txt 
lua/meta/reader/filename.lua 
'/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_multimedia_VLC/VLC/work/vlc-2.2.8/tmp/destdir/opt/local/share/doc/vlc/lua/meta/reader'
:info:build  /usr/bin/install -c -m 644  
lua/http/css/ui-lightness/images/ui-bg_diagonals-thick_20_66_40x40.png 
lua/http/css/ui-lightness/images/ui-bg_flat_10_00_40x100.png 
lua/http/css/ui-lightness/images/ui-icons_ff_256x240.png 
lua/http/css/ui-lightness/images/ui-bg_gloss-wave_35_f6a828_500x100.png 
lua/http/css/ui-lightness/images/ui-bg_glass_65_ff_1x400.png 
lua/http/css/ui-lightness/images/ui-icons_22_256x240.png 
lua/http/css/ui-lightness/images/ui-bg_glass_100_f6f6f6_1x400.png 
lua/http/css/ui-lightness/images/ui-bg_highlight-soft_100_ee_1x100.png 
lua/http/css/ui-lightness/images/ui-bg_highlight-soft_75_ffe45c_1x100.png 
lua/http/css/ui-lightness/images/ui-bg_diagonals-thick_18_b81900_40x40.png 
lua/http/css/ui-lightness/images/ui-icons_ffd27a_256x240.png 
lua/http/css/ui-lightness/images/ui-icons_228ef1_256x240.png 
lua/http/css/ui-lightness/images/ui-icons_ef8c08_256x240.png 
lua/http/css/ui-lightness/images/ui-bg_glass_100_fdf5ce_1x400.png 
'/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_multimedia_VLC/VLC/work/vlc-2.2.8/tmp/destdir/opt/local/share/vlc/lua/http/css/ui-lightness/images'
:info:build  ../autotools/install-sh -c -d 
'/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_multimedia_VLC/VLC/work/vlc-2.2.8/tmp/destdir/opt/local/share/doc/v

Re: Experiences with union mounts in MacOS?

[Ces VLC]

Thanks a lot, Michael, Daniel, and Richard, for your comments. Union mounts
are a very powerful feature that solves many needs, but, sadly, it's not
something you can rely on for critical-mission projects, because it seems
to be very little tested, if at all. Anyway, there are workarounds that can
provide at least similar functionality, and working with DMGs and symlinks
will help me.

Thanks, and happy new year!!

César




On Sun, Dec 16, 2018 at 8:47 PM Michael  wrote:

> Yea. Short answer: DON'T.
>
> Long answer: Mac OS does not support union mounts. They're there, they are
> honored by posix programs, but everything that using the apple file system
> interface bypasses it.
>
> Which means that just about anything based on cocoa framekworks ...
> optimizes and bypasses union mount visibility.
>
> I ran into  this back on 10.7, and complained, only to get basically this
> back from apple support engineers.
>
>
> On 2018-12-16, at 8:03 AM, Ces VLC  wrote:
>
> Hi!
>
> Sorry for this partially off-topic post, but couldn't imagine another
> place with more people likely to having experiences with little known MacOS
> UNIX features than this.
>
> In order to ease the testing of some builds, I had the idea of using union
> mounts ("mount -o union") to merge several DMGs together in the same folder.
>
> But I'm a bit afraid because it seems to be a little used feature in the
> Mac, so, if I'll be the only one in the planet using it, I guess it can be
> like sort of a minefield walk, likely to use little-tested stuff.
>
> I searched for it, and the only problems I saw reported is that Finder
> doesn't seem to honor union mounts, but that wouldn't be a problem for me,
> as I won't be using Finder for browsing the mount directory. If it works
> fine at the Terminal, then it's fine for me.
>
> Do you have any experience using union mounts on MacOS? Did it work fine
> for you? Did you find any problem/issues?
>
> Thanks!
>
> César
>
>
>
>
>
>
> ---
> Entertaining minecraft videos
> http://YouTube.com/keybounce
>
>

Gimp crashes when loading png or jpg

[Piet van Oostrum]

Hello,

Suddenly my gimp crashes when I try to load a PNG or JPG file. It gives the 
error message:
Plug-in crashed: "file-png"
(/Applications/MacPorts/GIMP.app/Contents/Resources/lib/gimp/2.0/plug-ins/file-png/file-png)

Plug-in crashed: "file-jpeg"
(/Applications/MacPorts/GIMP.app/Contents/Resources/lib/gimp/2.0/plug-ins/file-jpeg/file-jpeg)

This is gimp @2.10.8_0+animation+quartz and gimp2 @2.10.8_2+python27+quartz on 
MacOS High Sierra.
I upgraded on 26 december and before that it worked. I also uninstalled and 
reinstalled both gim and gimp2 from source but that did not help.

Is this a known issue?
-- 
Piet van Oostrum 
WWW: http://piet.vanoostrum.org/
PGP key: [8DAE142BE17999C4]

Re: pkg reclaim and versions check

[Riccardo Mottola via macports-users]

Hi Ken.

Ken Cunningham wrote:

It can be risky to use port reclaim for systems that can't use the buildbots as 
backup, or don't have a buildbot like 10.5 Intel or 10.4 PPC.

You must be quite careful, or you'll be doing a lot of needless rebuilding.

For each port or ports that you know you want, do this:



sorry for asking more details.. but why should it be risky on 10.4 or 10.5?

First, I'd expect reclaim to remove:
- installed stuff that is older than the latest installed release (inactive)
- active stuff, but which was pulled in by otehr packages now removed

of course without buildbot it is more inconvenient to reinstall 
something, but why should it happen?
I everything stays to current, removing something old shouldn't even 
require arebuild!


I had a blink light when I saw it wanted to remove soemthing I 
specifically installed was up to latest version!



Riccardo

PS: in case, can I reclaim manually certain inactive ports?

Re: pkg reclaim and versions check

[Ken Cunningham]

On 2019-01-02, at 10:00 AM, Riccardo Mottola wrote:

> Hi Ken.
> 
> Ken Cunningham wrote:
>> It can be risky to use port reclaim for systems that can't use the buildbots 
>> as backup, or don't have a buildbot like 10.5 Intel or 10.4 PPC.
>> 
>> You must be quite careful, or you'll be doing a lot of needless rebuilding.
>> 
>> For each port or ports that you know you want, do this:
> 
> 
> sorry for asking more details.. but why should it be risky on 10.4 or 10.5?


I think what happens is that port reclaim doesn't maintain the build 
dependencies, only the runtime ones (which is what most people need).

So on a system without a buildbot, some things are called in for the build, 
like clang-5.0 or cmake or gcc7, and they can take a long time to build, esp on 
10.5 - 10.6.  And you probably want them to stay around.

But if you install something that needs one of these to build, spend a day 
building the compiler, then install the software that needs it, and then run 
port reclaim, the compiler gets flushed.

Next update, you're starting over building clang-5.0, cmake, and whatever else 
again (because you have no buildbot to save you).

So you have to specifically set these things as "requested" to prevent them 
being purged with port reclaim.

> 
> First, I'd expect reclaim to remove:
> - installed stuff that is older than the latest installed release (inactive)
> - active stuff, but which was pulled in by otehr packages now removed
> 
> of course without buildbot it is more inconvenient to reinstall something, 
> but why should it happen?
> I everything stays to current, removing something old shouldn't even require 
> arebuild!
> 
> I had a blink light when I saw it wanted to remove soemthing I specifically 
> installed was up to latest version!
> 
> 
> Riccardo
> 
> PS: in case, can I reclaim manually certain inactive ports?


I often do that -- run

port -v installed gcc6

and then uninstall all the versions you don't want any more.


Ken

Re: gdb

[James Linder]

> On 6 Jan 2019, at 1:00 am, Mojca Miklavec  wrote:
> 
> Dear James,
> 
> I don't quite understand what your question/problem is. Can you please
> be more explicit (ideally on the mailing list).
> 
> Mojca
> 
> On Sat, 5 Jan 2019 at 15:11, James Linder  wrote:
>> 
>> Hi
>> 
>> can anybody show me mt errant ways
>> 
>> I installed gdb
>> codesigned as per 
>> https://sourceware.org/gdb/wiki/BuildingOnDarwin#Giving_gdb_permission_to_control_other_processes
>> I get
>> 
>> [Haycorn] /Users/jam/nodups [510]% ggdb nodups.app/Contents/MacOS/nodups
>> GNU gdb (GDB) 8.0.1
>> Copyright (C) 2017 Free Software Foundation, Inc.
>> License GPLv3+: GNU GPL version 3 or later 
>> This is free software: you are free to change and redistribute it.
>> There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
>> and "show warranty" for details.
>> This GDB was configured as "x86_64-apple-darwin17.2.0".
>> Type "show configuration" for configuration details.
>> For bug reporting instructions, please see:
>> .
>> Find the GDB manual and other documentation resources online at:
>> .
>> For help, type "help".
>> Type "apropos word" to search for commands related to "word"...
>> Reading symbols from nodups.app/Contents/MacOS/nodups...(no debugging 
>> symbols found)...done.
>> (gdb) q
>> 
>> [Haycorn] /Users/jam/nodups [511]% port list gdb
>> Warning: port definitions are more than two weeks old, consider updating 
>> them by running 'port selfupdate'.
>> gdb@8.0.1  devel/gdb
>> 
>> nodeps IS compiled with -g
>> Anybody please

/Applications/Xcode.app/Contents/Developer/usr/bin/make -f Makefile all
/Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/clang++
 -c -pipe -stdlib=libc++ -g -std=gnu++11  -arch x86_64 -isysroot 
/Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX10.13.sdk
 -mmacosx-version-min=10.12 -Wall -W -fPIC -DQT_DEPRECATED_WARNINGS 
-DQT_GUI_LIB -DQT_CORE_LIB -I. -I. 
-I/opt/Qt5.12.0/5.12.0/clang_64/lib/QtGui.framework/Headers 
-I/opt/Qt5.12.0/5.12.0/clang_64/lib/QtCore.framework/Headers -I. 
-I/Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX10.13.sdk/System/Library/Frameworks/OpenGL.framework/Headers
 
-I/Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX10.13.sdk/System/Library/Frameworks/AGL.framework/Headers
 -I/opt/Qt5.12.0/5.12.0/clang_64/mkspecs/macx-clang 
-F/opt/Qt5.12.0/5.12.0/clang_64/lib -o main.o main.cpp


[Haycorn] /Users/jam/nodups [511]% lldb nodups.app/Contents/MacOS/nodups
(lldb) target create "nodups.app/Contents/MacOS/nodups"
warning: (x86_64) 
/Users/jam/nodups/nodups.app/Contents/Frameworks/QtGui.framework/Versions/5/QtGui
 empty dSYM file detected, dSYM was created with an executable with no debug 
info.
warning: (x86_64) 
/Users/jam/nodups/nodups.app/Contents/Frameworks/QtCore.framework/Versions/5/QtCore
 empty dSYM file detected, dSYM was created with an executable with no debug 
info.
Current executable set to 'nodups.app/Contents/MacOS/nodups' (x86_64).

But elsewhere this does work:

[Haycorn] /Users/jam/nodups [512]% cat nodups.pro

TEMPLATE = app
TARGET = nodups
INCLUDEPATH += .

CONFIG += debug
<<< and there IS a -g

DEFINES += QT_DEPRECATED_WARNINGS

# Input
SOURCES += main.cpp


James