Re: Poll: should Trac send email notifications when adding or replacing an attachment?

[Rainer Müller]

On 2016-11-03 09:30, René J.V. Bertin wrote:
> Trac never sent notifications when you added or deleted (replaced) an
> attachment, but a recent introduced that as a new feature. I find
> this mostly useless and even annoying because when you update
> (replace, delete) an attachment there will be 2 emails. For active
> tickets I spend too much time weeding through and deleting emails
> devoid of interest.

By now I received more mails from you with complaints about this than
actual "duplicate" Trac notifications for attachment replacements...

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

Re: New mailing list host: lists.macports.org

[Rainer Müller]

On 2016-11-03 00:33, Ralph Seichter wrote:
> On 03.11.16 00:23, Ryan Schmidt wrote:
> 
>> The new mailing list server uses an updated version of mailman that is
>> supposed to handle this problem without the need to remove the email
>> footers.
> 
> If the sender signs message bodies and mailman modifies the bodies, DKIM
> signatures should, by design, become invalid. Like I mentioned before, the
> footers only repeat information given in the message headers anyway, so
> I can't see why we would not simply get rid of them.

To be more specific, we will make use of the mailman option
dmarc_moderation_action set to "Munge From". For sender domains with a
strict DMARC policy (p=reject or p=quarantine), the From address will be
rewritten to the list address and the original sender will be in
Reply-To. This will avoid bounces when the receiving mail server follows
DMARC policies.

To avoid invalidating DKIM at all, we would indeed need to remove the
footers.

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

New mailing list host: lists.macports.org

[Rainer Müller]

Hello,

as part of the move off of macOS forge, we will migrate the mailing
lists to the new mail server. We will migrate all subscriptions and user
preferences and postings to the old mailing list addresses will be
forwarded. However, the new hostname lists.macports.org implies that
addresses and List-Ids will change.

Please adapt your filtering rules and expect mails with addresses
@lists.macports.org.

The migration of all lists to the new host and addresses will happen
this weekend, November 5/6.

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

Re: Moving to GitHub: Status Update, Action Required

[Rainer Müller]

On 2016-10-28 16:02, Craig Treleaven wrote:
>> On Oct 21, 2016, at 2:12 PM, Clemens Lang  wrote:
>> ...
>> Migration Timeline
>> ==
>> The switch to Git will happen on the weekend of October 29th/30th. ...
> 
> Is this still on track?

Yes, expect Subversion to go read-only this weekend. Shortly afterwards,
the repositories on GitHub will be the authoritative source for MacPorts.

The infrastructure team did not schedule the exact time when this will
happen, but definitely this weekend.

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

Re: fetching of some ports fails, but you can wget them from the same URL

[Rainer Müller]

On 2016-09-27 15:45, Ken Cunningham wrote:
> I've noticed this behaviour a few times recently, most recently today with 
> hexchat, but this is not the only example.
> 
> Trying to get a file using macports' fetch fails, but you can manually wget 
> it without trouble.
> 
> I'm not sure if it's an SSL certificate thing, or why this is happening, 
> exactly.

In case of hexchat, the download server enforces strong security that
your client cannot fulfill. Our mirror infrastructure can also not
handle that.

https://trac.macports.org/ticket/51112#comment:6

MacPorts itself uses libcurl for fetching, which is linked against
OpenSSL 0.9.8 or earlier on old versions of OS X. wget from MacPorts
will use OpenSSL 1.0, which is recent enough.

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

Re: Migration of MacPorts installation: Very basic questions

[Rainer Müller]

On 09/26/2016 11:49 PM, Eneko Gotzon wrote:
> In the /Download and execute the restore_ports script/ section (Migration
> procedure of a MacPorts installation
> ), please, how 
> many
> commands are in the provided expression, three?
> 
>  1. curl -O
> 
> https://svn.macports.org/repository/macports/contrib/restore_ports/restore_ports.tcl
>  2. chmod +x restore_ports.tcl
>  3. sudo ./restore_ports.tcl myports.txt
> 
> The same about /Restoring the requested status;/ I believe they are two
> commands; I'm right?
> 
>  1. sudo port unsetrequested installed
>  2. xargs sudo port setrequested < requested.txt
> 
> Thank you very much and, again, excuse me.

Yes, your assumptions are correct.

Should we maybe put them in separate boxes to make this more clear?

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

Re: os x 10.12 sierra syslog

[Rainer Müller]

On 2016-09-26 11:52, Steve Wardle wrote:
> This isn't just a macports problem but someone here may be able to
> help.
> 
> I updated from OS X 10.11 to 10.12 over the weekend. After rebooting
> the machine was still running macports binaries installed under OS X
> 10.11. Postfix, dovecot2 and amavisd were running and logging to
> /var/log/mail.log correctly.
> 
> I removed and reinstalled macports and all the ports for OS X 10.12. 
> Now postlog, postfix, dovecot2 and amavisd run OK but nothing is
> logged to /var/log/mail.log. The /usr/bin/logger command also won't
> log to /var/log/mail.log.
> 
> If I run postlog or logger from my 10.11 backup they do log to
> /var/log/mail.log so syslogd seems to be working as in 10.11 but any
> binaries compiled under 10.12 fail to talk to it.

Please check Console.app instead. macOS 10.12 Sierra introduces "Unified
Logging" that now longer writes to log files on disk.

There is also a log(1) command line utility to query the log database.

https://developer.apple.com/reference/os/1891852-logging

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

Re: Starting gimp2

[Rainer Müller]

On 2016-09-24 22:02, David Liontooth wrote:
> I see the gimp executable in /opt/local/bin, but OS X doesn't seem to
> want to run it. This is on Sierra.

This is not very specific.
What is the behavior exactly?
What messages do you see?

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

Re: macOS Sierra / 10.12 support - where are we?

[Rainer Müller]

On 09/21/2016 08:54 PM, Richard L. Hamilton wrote:
> Are the build-bots building binary packages for Sierra yet, and if they
> aren't already there, may we be notified when they're at a level of
> completeness approximating that of El Capitan builds?  A migration would take
> hours less if one could get mostly binary packages. :-)

Yes, the buildbots for Sierra have already been up for a week. As of now, over
2300 binary archives for Sierra have been uploaded to the mirrors.

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

Re: User for startupitem.executable

[Rainer Müller]

On 2016-09-17 17:12, Javier Alcázar wrote:
> I'm creating a new Portfile with startupitem.executable, and wondering
> what is the best way to execute the command with a specific user.

Just for the future, Portfile development is usually discussed on
macports-dev, where you would reach more developers. The discussion on
macports-users is about usage of the port command and problems with
installs and upgrades.

> I tried using "su -c executable args" but with this approach
> launchd ends up monitoring the "su" process instead of the "executable"
> 
> What would you recommend to do so launchd looks at the "executable" process?

A few ports use this approach, citing from the mongodb port:

  startupitem.executable  sudo -u ${mongouser} ${prefix}/bin/mongod ...

While this adds an additional processes to the hierarchy, I do not see
any problem with that. The su/sudo keeps running until the command exits
and any signals sent to su/sudo will be relayed to the executed process.

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

Re: qemu, and using gcc45+ compilers on systems set up with LibCxxOnOlderSystems and libc++

[Rainer Müller]

On 2016-09-12 05:25, Ken Cunningham wrote:
> I would like to try building qemu, but it doesn't seem to be able to build 
> with clang-3.7 or clang-3.8 (on 10.68 with LibCxxOnOlderSystems and libc++)

QEMU is mostly C and the C++ parts are optional.

> the error for both 
> :info:configure ERROR: Your compiler does not support the __thread specifier 
> for 
> :info:configureThread-Local Storage (TLS). Please upgrade to a 
> version that does.
> 
> this error is out on the net, as far as I can see doesn't have any present 
> fixes; the recommended next step is to try with a newer version of gcc, like 
> 4.9

Check the end of the config.log file in ${worksrcpath} to see the exact
compiler command line and error message.

My guess would be that the linker on Snow Leopard does not support
thread local storage.

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

Re: What's the "right" way to update a port to

[Rainer Müller]

On 2016-08-28 18:46, Gabriel Rosenkoetter wrote:
> Apologies if this is a common question (if there’s a way to search PiperMail 
> archives that isn’t “download all of them and use grep locally”, I’ve never 
> known what it was), but I didn’t see an explicit facility to list a 
> cryptographic signature for the distribution files.
> 
> Is that a done thing?
> 
> (I can see how one could do this by adding the signature file to $distfiles 
> and then putting the signature verification in a post-checksum step, but if 
> there’s some standardized “make sure some sort of PGP exists locally and just 
> warn, rather than fail, if it doesn't” code, I figure it’s probably better to 
> adhere to that.)

No, verification of PGP signatures is not provided by base. gpg is not
available on an standard OS X install. Adding that as a requirement just
to verify the distfile would be quite heavy.

I would recommend maintainers to verify the signature locally and then
generate checksums for inclusion in the Portfile.

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

Re: Fail to execute a custom local portfile

[Rainer Müller]

On 2016-08-21 15:37, Giovanni Grieco wrote:
> But I can’t install my package via ‘port install’ because MacPorts
> throws me the following error:
> 
> “Unable to execute port: Could not open file:
> /Users/…/Documents/macports/… /Portfile”
> 
>  
> 
> I have the file in that directory, I can open and write it. So I don’t
> know what the problem is.
> 
> Permissions are all set to macports:macports 755, both directories and
> files; port lint doesn’t find any error  related to Portfile; I have
> sources.conf with my local repository.

The port command drops privileges to the macports user, which therefore
needs access to the Portfile.

You need to check the permissions on all components of the path leading
up to the Portfile, not just the Portfile itself. In this case, the
~/Documents directory would be 0700 by default, if I remember correctly.

To manually test the access, you can use sudo to switch to this user:

$ sudo -u macports cat $(port file kwm)

You can then check all directory permissions with bash like this:

$ bash -c 'IFS=/; for p in $(port file kwm); do path="${path%/}/$p";
paths+=("$path"); done; ls -lad "${paths[@]}"'

Make sure all directories have at least the +x bit set for everyone,
that allows the macports user to reach through.

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

Re: MacPorts reinstall : problem, sqlite error: database disk image is malformed

[Rainer Müller]

On 2016-07-06 09:54, guillaume trebuchet wrote:
> Is it possible to repair the database or reinstall port (the uninstall
> procedure doesn't work because of the registry problem) ?
> 
> for information, i try :
> {{{
> sudo port -fp uninstall installed
> }}}
> And this is the result :
> {{{
> sqlite error: database disk image is malformed (11) while executing query:
> ATTACH DATABASE '/opt/local/var/macports/registry/registry.db' AS registry
>while executing
> "registry::open $db_path"
>(procedure "mportinit" line 610)
>invoked from within
> "mportinit ui_options global_options global_variations"
> Error: /opt/local/bin/port: Failed to initialize MacPorts, sqlite error:
> database disk image is malformed (11) while executing query: ATTACH
> DATABASE '/opt/local/var/macports/registry/registry.db' AS registry
> }}}

The SQLite DB is usually very stable and often able to repair itself.
However, in this case it looks like it is not able to recover from the
damage done to the file at all.

Even restoring a previous version of this registry.db would not be
useful, as the information stored in the registry will no longer match
files present in the filesystem, especially if this shutdown happened
while a port command was running. That would lead to problems later when
installing or upgrading ports encounter unregistered files.

Unfortunately, your best option is to start again from a clean reinstall.

https://guide.macports.org/#installing.macports.uninstalling

As the first step will no longer work, just skip it.

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

Re: How to discover what TeXLive ports I need

[Rainer Müller]

On 2016-05-19 12:06, list_em...@icloud.com wrote:
> That's it. Is there some way to figure out what ports I need to add
> to get specific functionality? Or will I have to bite the bullet and
> do sudo port install texlive +full which warns "Full installation
> scheme (very large!)".

There is an index listing which LaTeX packages are in which MacPorts ports:

https://trac.macports.org/wiki/TeXLivePackages

Where should we add this to make it easier to find? Port descriptions?

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

Re: py35-mpi4 port?

[Rainer Müller]

On 2016-04-22 11:52, George Nurser wrote:
> Hi, Is anybody thinking of doing a py35-mpi4 port?

Are you maybe looking for py35-mpi4py?

Otherwise we would need more information which module you are looking
for, upstream source, etc.

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

Re: Thank you all for the wonderful MacPorts Meeting in Slovenia (and see you again soon ...)

[Rainer Müller]

On 2016-03-18 12:05, Aljaž Srebrnič wrote:
>> Special thanks to Ryan for joining us in a remote session, to Rainer
>> for representing the PortMgr, to Clemens for convincing us that
>> hacking the base might not be as scary as it sounds, for attracting
>> and mentoring new developers, to Dagobert for bringing in a fresh
>> perspective from a different package manager and helping us with the
>> buildbot setup, to Jackson for flying in from the other side of the
>> globe, to Peter for keeping us awake with Italian coffee and not
>> minding to completely change his meeting agenda, to our cook Darko.
>> And finally to Aljaž who set up all the infrastructure for the
>> conference and helped a lot with preparation work.
> 
> And a big thanks goes to Mojca, who found the hotel in the first
> place, negotiated a better internet connection, prepared and handled
> the payments, wrote mails, and generally did everything so that the
> meeting was successful!

Definitely a big shout out to Mojca for taking the initiative to start
this at all. It was such a great time! I am very glad we have such a
nice and friendly community around MacPorts.

>> Some moments have been captured in https://twitter.com/macports, but
>> during the week we are all too busy to document everything we have
>> done and everything that we discussed. You may expect the minutes from
>> the meeting arriving in not too distant future though.
>>
>> We all agreed that we have to meet again. So stay tuned.
> 
> Oh yeah! Judging from the quantity of food we ate, i’ll have to start
> fasting :P

The Slovenian beer I took home will keep me fueled for a while, but I
already miss the spirit of hacking together on MacPorts of the last
days. I really hope that the meeting badge [1] will not stay the only
one in the collection!

Rainer

[1] https://twitter.com/macports/status/708937075089870848
(thanks to Aljaž for this!)
___
macports-users mailing list
macports-users@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-users

Re: QEMU on Powerbook G4 running 10.5.8

[Rainer Müller]

On 2016-03-14 15:23, John T. Chung wrote:
> what's the last version which supports OSX? Could I install an earlier
> version?

I think it would be the one in the ports tree:

$ port info qemu-usermode
qemu-usermode @0.9.0 (emulators)

Rainer

PS: Please keep the mailing list in CC.
___
macports-users mailing list
macports-users@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-users

Re: QEMU on Powerbook G4 running 10.5.8

[Rainer Müller]

On 2016-03-14 05:15, John T. Chung wrote:
> Quick question for you all. I was able to build qemu-system on this
> system, and I see qemu-system-* executables under /opt/local/bin now.
> However does anyone know if this also includes qemu-usermode?
> 
> I am interested in usermode because it seems this will allow me to run
> OSX-intel binaries. (Reverse-rosetta, or ATTESOR)

qemu-usermode is a separate port, but support for OS X was dropped by
upstream. The port provides the latest supported version.

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

Re: Spawning ping for packages.macports.org failed

[Rainer Müller]

On 2016-02-25 23:29, Adam Mercer wrote:
> From this machine I can ping and contact all the hosts it complains about.

The command would be:

ping -noq -c3 -t3 $host | grep round-trip | cut -d / -f 5

> Any ideas what's going on here?

Did you have any ports installed before? Is the machine really new or
did you migrate your old installation?

In particular, do you have a /opt/local/bin/grep which fails to execute?

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

Re: Is there a good version of Time Machine?

[Rainer Müller]

On 2016-02-22 08:52, Dave Horsfall wrote:
> I ask because either it won't back up .dotfiles, or I've forgotten to 
> click one of those box thingies...

They should have been backed up, but you might not see them in Finder
when browsing the backup directory without enabling hidden files.
Use these commands to do so:

defaults write com.apple.finder AppleShowAllFiles true
killall Finder

> Specifically, I want my Firefox config back.

On OS X, the Firefox configuration profiles are not in a hidden
directories, but they should be at:

~/Library/Application\ Support/Firefox/

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

Re: Trying to execute LibcxxOnOlderSytems (2nd ed.)

[Rainer Müller]

On 2016-02-11 01:55, [ftp83plus] wrote:
> should I type
> sudo port -v uninstall cctools +llvm34
> sudo port -v uninstall ld64-136 +llvm34
> 
> then do 
> sudo port -v uninstall llvm-3.4 clang-3.4
> ?
> 
> The guide is not too clear on the exact syntax.

Specify the version and variants as listed in the output. You can also
look this up with 'port installed'. For example:

$ port installed cctools
The following ports are currently installed:
  cctools @877.5_2+llvm34 (active)
  ...

$ sudo port uninstall cctools @877.5_2+llvm34

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

Re: staging sc into destroot failed

[Rainer Müller]

On 2016-01-28 13:02, j. van den hoff wrote:
> does not look like a new "ticket" (or does it?), but something wents
> wrong in the final phase. any ideas?

This was fixed already in r145176 [1]. Clean the previous attempt, get
the new Portfile and try again with the following commands:

  sudo port clean sc
  sudo port selfupdate
  sudo port upgrade sc

Rainer

[1] https://trac.macports.org/changeset/145176
___
macports-users mailing list
macports-users@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-users

Re: how keep particular broken port from trying to reinstall?

[Rainer Müller]

On 2016-01-17 18:13, Murray Eisenberg wrote:
> 1. Each time I upgrade any ports, automatically MacPorts notices that
> the port for qt4-mac is broken and attempts to build it again.
> 
> Is there any way to do upgrades of other points without the
> time-consuming (always failing) attempt to rebuild qt4-mac?

sudo port [upgrade|install] --no-rev-upgrade

> 2. I’d try to uninstall qt4-mac and re-install the older version that, I
> believe, was unbroken.  But there are a whole bunch of other ports that
> depend on it. How may I get around uninstalling those dependent ports
> and reinstalling them later?  (I believe I need to use a “-f” parameter
> but otherwise am uncertain how to do this.)

You probably still have the older qt4-mac installed, so you can simply
reactivate it:

https://trac.macports.org/wiki/howto/InstallingOlderPort#reactivate

Why is the build of qt4-mac failing? You should rather get that fixed in
order to get the latest version.

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

Re: How to obtain a list of ports which were recently added?

[Rainer Müller]

On 2015-12-18 16:20, Kurt Pfeifle wrote:
> I am interested to learn about newly added ports.
> 
> Is there a "port list" command that can sort ports according to their
> release date?
> 
> Most likely, at the present time, there's none.
> 
> Is there another method (web interface or trac ticket query or ...?)
> which I could employ to find *quickly* out what I want?

There is no port database that tracks this kind of metadata. A service
that tracks changes to PortIndex would actually be quite nice...

At the moment, you can only filter the Subversion commit log and look
for added Portfiles. With a little bit of quick hacking I came up with
this command, which prints the port directories added in the last two
weeks:

svn log -v -r"{$(date -v-2w +'%Y-%m-%d')}":HEAD 
https://svn.macports.org/repository/macports/trunk/dports \
|grep -E '^\s{3}A.*Portfile$' |awk -F/ '{print $5}'

With some more processing you could also retrieve the commit message or
extract the port's description.

Hope that helps,
Rainer
___
macports-users mailing list
macports-users@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-users

Re: autogen rdeps

[Rainer Müller]

On 2015-12-13 15:25, Jan Stary wrote:
> On Dec 13 07:32:59, ryandes...@macports.org wrote:
>> On Dec 13, 2015, at 06:40, Jan Stary wrote:
>>>
>>> This is just insane.
>>> I need jpeg and the whole TeX suite to install autoconf?
>>
>> No, you (apparently) need them to install autogen. autogen and autoconf are 
>> different software,
>> available in different ports. If you want autoconf, install the autoconf 
>> port. 
> 
> Sorry, that's a typo - I meant autogen.

If there are no binary archives available (MacPorts do not provide them
for 10.5.x), all ports will be compiled from source, which may include
ports as additional build dependencies that are no longer needed at
runtime. If you are used to other distributions with binary packages
only, this might seem insane to you, but this just cannot be avoided for
a source-based distribution.

Yes, you need these dependencies. They are used to build the
documentation (man pages, possibly HTML, API docs, etc.) in these ports.

About the xorg-* ports discussed earlier in this thread:
http://trac.macports.org/wiki/FAQ#x11-libs

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

Re: xrg build fails after OS X upgrade to 10.11.2 (15C50) and Xcode Version 7.2

[Rainer Müller]

On 2015-12-10 03:21, Manfred Antar wrote:
> It’s something with Xcode 7.2
> Im sure this will be coming up again

Yes, I got a similar report against MacVim:
https://trac.macports.org/ticket/49950

It seems like Xcode 7.2 expects more restrictive permissions on this
path, but it does not ensure they are set at installation.

This is from my OS X 10.10 Yosemite, Xcode 7.1:

drwxrwxr-x  3 root  wheel  102 Oct  2 23:11 
/Applications/Xcode.app/Contents/Developer/Library/PrivateFrameworks/CoreSimulator.framework/Versions/A/XPCServices/com.apple.CoreSimulator.CoreSimulatorService.xpc/

After upgrading to Xcode 7.2, the permissions remained the same:

drwxr-xr-x  3 root  wheel  102 Nov 10 06:21 
/Applications/Xcode.app/Contents/Developer/Library/PrivateFrameworks/CoreSimulator.framework/Versions/A/XPCServices/com.apple.CoreSimulator.CoreSimulatorService.xpc/

Still the same error. I added an entry to ProblemHotlist:
http://trac.macports.org/wiki/ProblemHotlist#xcode7.2

It is definitely a problem within Xcode or its installation/update
process. Filing rdars might be a solution to get attention to this.

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

Re: about XDG_RUNTIME_DIR

[Rainer Müller]

On 2015-11-23 17:32, René J.V. Bertin wrote:
> Freedesktop/XDG-compliant applications may use a user-specific
> location for runtime "stuff" like sockets. On Linux, this location
> usually is something like /run/user/uid. It is typically defined
> globally through the XDG_RUNTIME_DIR env. variable, with a fallback
> if that variable doesn't exist.

> How does MacPorts handle this, is there a consensus? Or are
> applications and "frameworks" left to determine their own fallback
> value because XDG_RUNTIME_DIR will typically NOT be set? The only
> beginning of an answer I have for now is the presence of a few
> ~/.cache/keyring-X directories, which may correspond to the
> similarly named keyring directories in /run/user/uid on my Linux
> rig.

Adding environment variables is complicated and involves interruption by
the required logout/reboot. If possible, we should avoid it and patch
the default settings for libraries and applications instead.

> Context: Qt5's QStandardPaths::RuntimeLocation return value. It
> defaults to ~/Library/Application Support, which I think is fine for
> "native mode" but not for an XDG-compliant mode.

For runtime files, such as sockets, this looks like an unusual location
to me. Putting them in $HOME is unnecessary, as they would not need to
be preserved (not even across reboots, and especially not in backups).

Were there any sandbox limitations involved in this choice?

> Alternatives I see:
> - $TMPDIR/runtime-username (calculated using the QSP RuntimeLocation code 
> used on other Unix hosts)

This sounds like a sane solution to me. Runtime directory can safely be
cleared on session exit or reboot.

> - ~/.cache (to align with what Gnome *may* use).

I have not verified it, but it looks like this is the solution deployed
by GLib:

https://developer.gnome.org/glib/stable/glib-Miscellaneous-Utility-Functions.html#g-get-user-runtime-dir

> I tend to prefer the 1st alternative to stick closest to what happens
> on Linux, but only if Qt5-based and non-Qt5-based applications and
> libraries need NOT agree on the location.

I agree this could become a problem for application interaction when
GLib and Qt use different paths, so we should set a common default.

However, do we also want to support interaction between applications
managed by MacPorts and those installed manually?

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

Re: openssl vs. libressl

[Rainer Müller]

On 2015-11-10 15:21, Daniel J. Luke wrote:
> We could have a port “mp-ssl-lib” that defaults to depending on one
> of the ssl libs (say openssl). It could also be installed as
> mp-ssl-lib +libressl which would modify it’s dependencies and install
> libressl and not openssl.
> 
> Other ports would all depend on ‘mp-ssl-lib’ and not directly only
> openssl or libressl.
> 
> It’s not a perfect solution, but may be nicer than adding
> +openssl/+libressl to every possible port.

This would basically cause the same problems as with the current path:
dependency.

It is still required to rev-upgrade all ports after switching the
variant. All binary archives built with the default option would not
work on a system with a different variant choice on mp-ssl-lib.

Explicit variants in all ports are the only way to prevent that, as the
port contents will actually be different depending on whether you link
against openssl or libressl.

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

Re: openssl vs. libressl

[Rainer Müller]

On 2015-11-09 22:40, René J.V. Bertin wrote:
> Now what if you do
> 
> %> ln -s libssl.35.dylib libssl.1.0.0.dylib ?
> 
> (assuming that libressl indeed installs libssl.35.dylib)
> 
> If that works, it can be handled with a very simple post-destroot addition in 
> both ports .

You should not do this. It might work for some binaries, but it is not
guaranteed to work in all cases.

See both the official statement and a blog post from a Gentoo developer
explaining the problem:

https://github.com/libressl-portable/portable#compatibility-with-openssl

https://blog.flameeyes.eu/2014/07/libressl-drop-in-and-abi-leakage

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

Re: Experiences with El Capitan

[Rainer Müller]

On 2015-11-05 21:00, Dave Horsfall wrote:
> Now, did Macports really feel the need to re-compile the world, over three 
> days?  I got tired of seeing that bloody spinning beach-ball...  Why did 
> it not merely retrieve pre-built binaries, as usual?

As of now, we do not have a buildbot instance for El Capitan yet.

This is mainly due to the absence of an actual admin at Mac OS Forge,
our hosting provider at Apple. This also caused the disruption in
service recently and the ongoing issues with the infrastructure.

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

Re: error upgrading gcc48 port

[Rainer Müller]

On 2015-10-30 13:59, Mojca Miklavec wrote:
> On Fri, Oct 30, 2015 at 1:49 PM, Chris Jones wrote:
>> On 30/10/15 12:26, Fabrizio Salvatore wrote:
>>>
>>> I see that there are two ports related to gcc48, one of which is active:
>>>
>>> --->  The following versions of gcc48 are currently installed:
>>> --->  gcc48 @4.8.2_2
>>> --->  gcc48 @4.8.3_3 (active)
>>>
>>> How do I remove both and make gcc49 the default one?
>>
>> specify the version when uninstalling
>>
>>> sudo port uninstall gcc48@4.8.2_2
> 
> Is there also something like
> sudo port uninstall gcc48@all
> ?

You can achieve that with the intersection of ports with the name gcc48
and ports that are installed:

  sudo port uninstall gcc48 and installed

> Also, what happened to the GSOC project where user would simply select
> which port to uninstall in an interactive way?

The work was merged to trunk, but is not yet available in any released
version of MacPorts.

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

Re: Migration instruction site is down

[Rainer Müller]

On 10/21/2015 01:26 AM, Ryan Crocker wrote:
> I just switched to El Captain and I wanted to migrate macports over to that 
> OS.
>  I tried:
> 
> https://trac.macports.org/wiki/Migration
> 
> but that site is down.  Does anyone have the instructions or another site 
> where
> they are posted. 

Sorry for the inconvenience. Please try one of these:

https://webcache.googleusercontent.com/search?q=cache:https://trac.macports.org/wiki/Migration

https://web.archive.org/web/*/https://trac.macports.org/wiki/Migration

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

Re: Modification of .profile

[Rainer Müller]

On 2015-10-15 23:22, Bachsau wrote:
> May I suggest to add an option for the PKG installer to disable
> automativ modification of user's ~/.profile file? On my system I
> modified my /etc/paths file to include MacPorts ater my own
> /usr/local. When I installed a new version by using the PKG today, I
> found my .profile and PATH modified without request.

The postflight script should only modify your shell configuration files
if your PATH does not yet contain a reference to /opt/local [1]. If it
was set up in /etc/paths, this should have prevented additional
modifications.

I don't know if package installers support custom options or optional
components. Maybe someone else can comment on this.

Rainer

[1]
https://trac.macports.org/browser/trunk/base/portmgr/dmg/postflight.in#L239
___
macports-users mailing list
macports-users@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-users

Re: about MacPorts principles, conventions (and dogmata :)) re: install layouts and Qt

[Rainer Müller]

On 2015-10-13 11:47, René J.V. Bertin wrote:
> On Tuesday October 13 2015 11:32:58 Aljaž Srebrnič wrote:
> 
>>
>> Oh, so *that's* why wireshark can’t find QtCore...
> 
> That's only partly true. The main reason may simply be that it doesn't use 
> the Qt4 Portgroup like it should.
> 
> It's a pity that there's nothing in base to print a warning (or raise an 
> error) if a PortGroup is not included.

Uhm, how should the port system know when a port group is missing?

Deviation from the standard layout will lead to more work to detect the
proper location of files in dependents. It should be discouraged.

We have discussed this with the example of the apache2 port for years:
http://trac.macports.org/ticket/21315

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

Re: Problem installing macports

[Rainer Müller]

On 2015-10-12 14:31, Sepideh Razavi wrote:
> /opt/local/libexec/macports/bin/tclsh8.5
> ./src/upgrade_sources_conf_default.tcl "/opt/local"
> 
> couldn't create error file for command: no such file or directory
> 
> while executing
> 
> "open "|$mktemp -t macports_sources_upgrade.XX" r"
> 
> invoked from within
> 
> "set mktempChannel [open "|$mktemp -t
> macports_sources_upgrade.XX" r]"
> 
> (file "./src/upgrade_sources_conf_default.tcl" line 33)
> 
> make: *** [install] Error 1

It looks the installation is unable to create temporary files.
Maybe $TMPDIR points to a non-existent path?

Reboot your machine. That should reset the temporary directory.

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

Re: libgmp

[Rainer Müller]

On 2015-10-11 16:14, Thomas Bodlien wrote:
> This is, what I am getting:
> 
> $ otool -tv /Volumes/SSD/SRC/Mac/Compute\ PI/libgmp.10.dylib  |grep -A6 
> ^___gmpn_sqr_basecase:
> ___gmpn_sqr_basecase:
> 00028fa0  cmpq$0x2, %rdx
> 00028fa4  jae 0x28fb6
> 00028fa6  movq(%rsi), %rdx
> 00028fa9  mulxq   %rdx, %rax, %rdx
> 00028fae  movq%rax, (%rdi)
> 00028fb1  movq%rdx, 0x8(%rdi)

This confirms the theory. The MULX instruction was added to Haswell and
is not supported on earlier CPUs.

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

Re: rdiff-backup not saving metadata, Finder Information, Extended Attributes

[Rainer Müller]

On 2015-10-10 21:20, stevenos...@gmail.com wrote:
> $ rdiff-backup -v4 1 2
> Using rdiff-backup version 1.2.8
> Unable to import module xattr.
> Extended attributes not supported on filesystem at 1

$ python2.7 -c 'import xattr'
Traceback (most recent call last):
  File "", line 1, in 
  File
"/opt/local/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/site-packages/xattr/__init__.py",
line 12, in 
from .lib import (XATTR_NOFOLLOW, XATTR_CREATE, XATTR_REPLACE,
  File
"/opt/local/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/site-packages/xattr/lib.py",
line 4, in 
import cffi
ImportError: No module named cffi

I fixed the missing dependency in r141108. Wait for the updated port or
just install the port manually:

$ sudo port install --unrequested py27-cffi

> Unable to import module posix1e from pylibacl package.
> POSIX ACLs not supported on filesystem at 1

We do not have a port for pylibacl. However, OS X does not even use
POSIX ACLs, so I do not know how useful it would be...

> Unable to import win32security module. Windows ACLs
> not supported by filesystem at 1
> escape_dos_devices not required by filesystem at 1

I guess we can ignore those.

> -
> Detected abilities for source (read only) file system:
>   Access control lists Off
>   Extended attributes  Off
>   Windows access control lists Off
>   Case sensitivity Off
>   Escape DOS devices   Off
>   Escape trailing spaces   Off
>   Mac OS X style resource forksOn
>   Mac OS X Finder information  Off
> -

For the Finder information, rdiff-backup tries to use
Carbon.File.FSSpec, which is no longer supported:

$ python2.7 -c 'import Carbon.File; import MacOS; print
Carbon.File.FSSpec(".");'
Traceback (most recent call last):
  File "", line 1, in 
AttributeError: 'module' object has no attribute 'FSSpec'

These problems should rather be discussed and addressed by rdiff-backup
developers. They are not caused by the packaging, but exist in the
upstream version.

Hope that helps,
Rainer
___
macports-users mailing list
macports-users@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-users

Re: libgmp

[Rainer Müller]

On 2015-10-11 00:24, Thomas Bodlien wrote:
> can it be, that the compiler is creating Haswell specific machine-code?

Yes, very likely. MacPorts does not pass any -march or -mtune arguments
by default to the compiler. The gmp port even disables archive_sites to
force a build on the local machine. The Portfile points to ticket in
Trac [1], which is inaccessible at the moment.


The crash log tells us it was an illegal instruction:

  Exception Type: EXC_BAD_INSTRUCTION (SIGILL)
  Exception Codes: 0x0001, 0x
  Exception Note: EXC_CORPSE_NOTIFY

The instruction can be found at this location:

  Thread 8 Crashed:
  0 libgmp.10.dylib 0x00010005bfa9 __gmpn_sqr_basecase + 9

In the libgmp.10.dylib I built locally, there is no suspicious
instruction at this location:

  $ otool -tv /opt/local/lib/libgmp.10.dylib |grep -A6 ^___gmpn_sqr_basecase:
  ___gmpn_sqr_basecase:
  00025b40  cmpq$0x2, %rdx
  00025b44  jae 0x25b54
  00025b46  movq(%rsi), %rax
  00025b49  mulq%rax
  00025b4c  movq%rax, (%rdi)
  00025b4f  movq%rdx, 0x8(%rdi)

Can you check this in the version you are shipping?

Rainer

[1] http://trac.macports.org/ticket/41614
___
macports-users mailing list
macports-users@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-users

Re: Trace/BPT trap: 5 on Mac OS 10.9.2 Mavericks

[Rainer Müller]

On 2015-10-09 18:13, Clemens Lang wrote:
> - On 9 Oct, 2015, at 17:38, Brandon Allbery allber...@gmail.com wrote:
> 
>> That kind of path is normally used with application bundles (that is, stuff
>> under /Applications). What exactly are you trying to run? And do you have any
>> DYLD variables set in the environment?
>>
>> $ env | grep DYLD
> 
> Note that due to System Integrity Protection, "env" no longer lists any DYLD_
> variables on El Capitan. Try
>   $ (set -o posix; set) | grep DYLD
> instead.

This has the limitation that it will show all shell variables, not just
those which are exported. This is a subtle difference and the command
above probably works in most cases. The following would only show
exported variables and their values:

  for i in $(compgen -e); do echo "$i=${!i}"; done

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

Re: Darwin Version

[Rainer Müller]

On 2015-10-04 12:25, William H. Magill wrote:
> As with the “success” above, the answer appears to be with the
> Migration Instructions. The problem is that the visual queues given
> by the “command indent and boxing” are much more emphatic than the
> numbered items. i.e. the Eye overrides RTFM.

Thank you for your input. I tried to improve the Migration wiki page.

Please check again:
http://trac.macports.org/wiki/Migration

> Step one needs to be — download and install the version of MacPorts
> appropriate to the new release found at the top of  the QuickStart
> page, NOT “port -qv”!
> 
> Or put another way, the instructions on the QuickStart page and the
> Migration page need to be better integrated. Step 2 in the Migration
> Procedure is the key.
> 
> Maybe wording like:
> 
> "Reinstall MacPorts base. After updating the development tools,
> install the base MacPorts system  for your new platform, either from
> the appropriate installer (download it from the QuickStart section)
> or from source.”

Users going to the Migration page should already be familiar with
MacPorts itself as they used it on the previous release of OS X.
I don't think they need the QuickStart anymore.

> Similarly, the numbering of the Migration Guide is somewhat
> confusing.
> 
> 2.a should probably be moved to 3.a and the rest of 3 renumbered
> accordingly.

I don't understand that. 2a was the macports.conf update, which is
closer to updating MacPorts base than reinstalling ports. I left this at
step 2.

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

Re: El Capitan build errors...

[Rainer Müller]

On 2015-10-04 20:16, Richard L. Hamilton wrote:
> Here's my latest set of errors with log excerpts, now that I got
> further by applying the qt4-mac patch described in the ticket.
> They're in order by number of other ports dependent on them, i.e. of
> those I ran into, clucene had the most.  Latest MacPorts, latest
> everything.

Please check Trac first if the problem was already reported:

El Capitan:   http://trac.macports.org/wiki/ElCapitanProblems
Search for ports: https://trac.macports.org/wiki/Tickets

If no report exists yet, please file a separate new Ticket for each
port. Follow the guidelines and specifically set the maintainer in the
CC field, so they get a notification.

See the guide here:
https://guide.macports.org/#project.tickets

Thanks!

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

Re: Versions in ports

[Rainer Müller]

On 2015-09-18 14:18, Artur Szostak wrote:
> I have created a ticket with the patch as suggested:
> https://trac.macports.org/ticket/48909
> 
> Kind regards.

Thank you for the contribution. I finally committed it in r140804.

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

Re: Darwin Version

[Rainer Müller]

On 10/03/2015 03:35 PM, Jeffrey A. Singleton wrote:
> So I go to the migration page as mentioned in the error and begin with Step 1:
> 
> root@minimac ~ #  port -qv installed > myports.txt
> Error: Current platform "darwin 15" does not match expected platform 
> "darwin 14"
> Error: If you upgraded your OS, please follow the migration instructions:
> https://trac.macports.org/wiki/Migration
> Error: /opt/local/bin/port: Failed to initialize MacPorts, OS platform 
> mismatch

This is actually Step *3*. You skipped 1. reinstalling Xcode and 2. reinstalling
MacPorts. It is already a numbered list of steps...

What should we change on the wiki page to make it more clear?
This is an honest question. I am open to suggestions.

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

Re: Darwin Version

[Rainer Müller]

On 2015-10-01 15:43, Bachsau wrote:
> Hi, could anyone please tell me where MacPorts saves on which
> operating system version it was installed, so i can bump it? It says
> "Current platform 'darwin 15' does not match expected platform
> 'darwin 14'". I read the Migration instructions, but sorry. No. It is
> idiotic to reinstall all of my stuff. I'm pretty sure that if I could
> get rid of that useless message, everything would work pretty well.

It may appear to be still working right now, but there is no guarantee
that it will work at all. Even if it seems to be working now, later
updates will cause problems. For example updates will link to a
different set of new system libraries.

Although cumbersome, the migration procedure ensures that everything
keeps working after upgrading to a new OS X release.

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

Re: Versions in ports

[Rainer Müller]

On 2015-09-15 12:18, Artur Szostak wrote:
>> If there is any documentation advocating upgrading individual
>> ports, or especially documentation advocating downgrading a port,
>> please send us the URL so that we can correct the information.
> 
> How about the manpage. When looking at the description of the upgrade
> command there is not a single notice or disclaimer that upgrading an
> individual port is not recommended because it can lead to problems. I
> would also expect it to mention that the standard way to upgrade is
> always: port upgrade outdated 

Sounds like a good improvement. Actually, the next 2.x release will
feature a new documentation system with a separate man page for each of
the commands. For example, the current trunk versions of the port(1) and
port-upgrade(1) man pages can be viewed in the repository [1,2].

If you have an idea how to incorporate this information, you are very
welcome to submit patches for the documentation (just text would be okay
as well, formatting is the easy part).

For the man pages, we switched to AsciiDoc syntax, so editing should be
quite easy now. Updating the guide is a bit more cumbersome as it is
written in DocBook XML, but the README at [3] has at least some pointers
on how to check for syntax errors.

Rainer

[1] https://svn.macports.org/repository/macports/trunk/base/doc/port.1.txt
[2]
https://svn.macports.org/repository/macports/trunk/base/doc/port-upgrade.1.txt
[3] https://svn.macports.org/repository/macports/trunk/doc-new/
___
macports-users mailing list
macports-users@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-users

Re: Versions in ports

[Rainer Müller]

Hi Artur,

On 2015-09-14 16:22, Artur Szostak wrote:
> After about a year's worth of experience with MacPorts, there is
> something that I still do not understand: why is there no mechanism
> to express version requirements in the dependency information for a
> Portfile? I have been running into a number of situations where
> upgrading or downgrading an individual port leads to an
> inconsistent/incompatible combination of package versions. It seems
> that unless you are busy hacking away at your system, the only
> reasonable upgrade path is always: sudo port upgrade installed

I agree with you that versioned dependencies would help in certain
situations. However, it also means maintainers would need to invest
additional time and tests to find out the lowest/highest working version
would be.

As MacPorts only provides a single version of each software in the ports
tree, keeping track of these compatibilities is actually quite hard. If
we had versioned dependencies, we could add them once they are reported,
but I do not think the project has the capacity to actively check for
this before committing updates.

FWIW, 'sudo port upgrade outdated' should be preferred. With the
'installed' pseudo-port ports will be parsed which takes some time.

> To me, it feels like the MacPorts documentation is misleading the end
> user to believe that upgrading/downgrading individual packages is a
> routine and safe procedure, when my experience tells me otherwise.
> Can anyone point me to the reason behind these design decisions?

I doubt there ever was a design decision to leave it out. In the same
way there is no way variants can be used in a dependency, this cannot be
fixed without rewriting lots of the current MacPorts base. We have a
project funded by Google Summer of Code this year to add a SAT solver,
which will be a first step for more possibilities how dependencies are
handled in the future.

There should be no documentation telling you that leaving ports outdated
is safe – only the latest version/revision of ports is supposed to work
with each other. We should get that fixed.

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

Re: encounter error while it is installing arm-none-linux-gnueabi-gcc for my mountain lion with macport

[Rainer Müller]

On 2015-09-10 16:44, 心如烛光 wrote:
> And here is the log of the port:
> *_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_cross_arm-none-linux-gnueabi-gcc/arm-none-linux-gnueabi-gcc/work/build/gcc'*
> *:info:build make: *** [all-gcc] Error 2*
> *:info:build make: Leaving directory

This is cut off, the real error message will be above these lines.

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

Re: How to reliable detect a MacPorts-ported compiler?

[Rainer Müller]

On 2015-09-09 16:02, Daniel J. Luke wrote:
>> On Sep 9, 2015, at 12:35 AM, Jeffrey Walton  wrote:
>>
>>> Again, I have to ask why you want to do this.
>>
>> My apologies, I was not trying to be rude. I specifically avoided
>> addressing any of these questions because of the bikeshedding
>> involved.
>>
>>> What problem are you seeing with FSF GCC compiled with MacPorts that you do 
>>> not see with FSF GCC compiled on a Mac by some other means?
>>
>> None that I am aware.
>>
>> But that's not the problem I am trying to solve.
> 
> the confusion here is that it seems to be that you would be better served in 
> detecting FSF GCC (generally) rather than a macports build of FSF GCC 
> (specifically).

I would have used something like this:

#if defined(__APPLE__) && \
  (defined(__GNUC__) || defined(__GNUG__)) && \
  !defined(__clang__) && !defined(__ICC)
/* the compiler is gcc/g++ on OS X */
#endif

However, Fink ships a patched version of GCC enabling this feature on
Darwin [1], which would make an accurate detection a lot more complicated.

While looking into this, I noticed that even though clang accepts it,
the behavior is different compared to GCC, even on Linux. The reordering
might only happen in the current module, not globally, depending on the
version of clang [2]. The behavior will change once again if you use
-flto or pass multiple files at once to the compiler.

Rainer

[1]
http://fink.cvs.sourceforge.net/viewvc/fink/dists/10.7/stable/main/finkinfo/languages/gcc5.patch?revision=1.2&view=markup#l219
[2] https://llvm.org/bugs/show_bug.cgi?id=11480
___
macports-users mailing list
macports-users@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-users

Re: How to reliable detect a MacPorts-ported compiler?

[Rainer Müller]

On 2015-09-07 02:46, Jeffrey Walton wrote:
> We have some users reporting issues under MacPort-ported compilers
> (specifically, Issue 37664, https://trac.macports.org/ticket/37664).
> 
> How do I reliably detect a MacPorts-ported compiler?

Wouldn't it be more correct to detect gcc on OS X as apparently this
feature is not supported no matter where the compiler comes from?

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

Re: Error: Insufficient privileges to write to MacPorts install prefix.

[Rainer Müller]

On 2015-08-07 07:03, Jim Mattingly wrote:
> Getting the above-referenced error code when attempting command: port
> install pspp, Have even tried sudo, although it is only a single-user
> computer at home, then sudo scolds me and asks for a password I don’t
> have. Downloaded Xcode from app store and macports, according to
> macports guide, and env command worked just fine, but both install
> and selfupdate commands tell me I don’t have the necessary privileges
> to run them. Simply running commands on apple terminal with Xcode
> open. Any ideas what to do? I’m perhaps a relatively advance user,
> but not an IT pro, so perhaps there is something simple I’m
> overlooking.

You can't use sudo without setting a password for your user account.

https://support.apple.com/en-us/HT202035

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

Re: configure: error: cannot find QtCore header

[Rainer Müller]

On 2015-06-11 13:09, Hinckley Dan wrote:
> I have qt5-mac installed and am compiling a program which looks for
> qtccore. The error I get is:
> 
> checking QtCore usability... no
> checking QtCore presence... no
> checking for QtCore... no
> configure: error: cannot find QtCore header; try setting CPPFLAGS.

You should look into config.log to get the details of this failing test.

Perhaps it is also trying to link a simple program which requires
setting LDFLAGS as well.

Have you made sure it is actually looking for the right version of Qt?
Often, Qt 5.x is referenced by Qt5Core and Qt 4.x is QtCore.

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

Re: accelerated zlib experiment (and parallel afsctool)

[Rainer Müller]

On 2015-06-05 22:24, Lawrence Velázquez wrote:
> On Jun 5, 2015, at 4:17 PM, René J.V. Bertin  wrote:
> 
>> Rather as a different port I think, or simply as an update to the existing 
>> port, but only if there's demand.
> 
> There's no difference. The point is that we don't want to become a de facto 
> upstream.

+1

Coming back to the original discussion, there is some traction towards a
real fork of zlib named zlib-ng. Although there are no releases so far,
but might be worth to keep in mind (or contribute there).

https://github.com/Dead2/zlib-ng

Disclaimer: I have not checked anything with regard to its licensing.

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

Re: zlib acceleration?

[Rainer Müller]

On 2015-05-29 11:21, René J.V. Bertin wrote:
> After re-running the benchmarks with the HEADS from the respective
> implementations, the picture changes and the CloudFlare patch becomes
> much more interesting. The CloudFlare patch in its current form does
> require the -msse4 flag as it uses a crc intrinsic from that instruction
> set. Are there still Macs around that do *not* have SSE 4.1, supposing
> they ever existed (apart from PPC Macs of course)?

There are Macs from 2006/2007 with a 32-bit Intel Core Duo processor
that do not support SSE 4.1. It is doubtful whether the default
compilers on these old platforms support these instruction sets.
However, that should not be a problem, as we could probably exclude
these old Macs by enabling the feature only on recent enough versions of
OS X which require newer processors anyway.


Looking at the CloudFlare patch, the implementation does not seem to
check for availability of the SSE 4 instruction set with CPUID and does
not offer any fallback.

However, the rest of the patch does not look applicable either.
Especially this GPL header here bothers me a lot:
https://github.com/cloudflare/zlib/blob/gcc.amd64/contrib/amd64/crc32-pclmul_asm.S

Furthermore, "Function stolen from linux kernel 3.14.", although they
did not even add any GPL copyright notice to the file:
https://github.com/cloudflare/zlib/blob/gcc.amd64/crc32.c#L244

After applying this to the zlib port, the resulting binary would
certainly be covered by the GPL-2 and not the zlib license anymore. That
would introduce lots of compatibility problems.

Even if this CloudFlare patch offers any performance improvements, the
authors did not bother to implement it the sane way respecting licenses
for further distribution. In this form, it will never be included
upstream and we should not do it either.


The Intel patch looks better, applying zlib license to the files added.
Also it has a check for availability of the SSE 4.2 feature before
execution of the machine instruction.

Unfortunately, I couldn't find any zlib mailing list archive containing
the discussion of including the Intel patches.

Overall I concur with Ryan. Development of an library as mature as zlib
is usually conservative and I would let the upstream maintainers decide
if they want to include these patches in their next release.

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

Re: yosemite and 2008/9 macbookpro compatability, macports install settings for older architecture?

[Rainer Müller]

On 2015-05-28 15:16, ^. .^ wrote:
> i recently upgraded a late 2008 macbookpro to yosemite. with SSD it
> seems to work ok.

Did you follow the migration procedure?

http://trac.macports.org/wiki/Migration

> when running macports to install software i get the following error
> 
> 
>  Error: Cannot install ImageMagick for the arch(s) 'x86_64' because
>  Error: its dependency libtool is only installed for the arch 'i386'
>  Error: and the configured universal_archs 'i386 ppc' are not sufficient.
>  Error: Unable to execute port: architecture mismatch
> 
> 
> 
> I found the macports.conf file and uncommented
> build_arch   i386
> 
> and i cleaned all. but the error remains the same. this machine did not
> have macports on it last time around so i did not follow the whole list
> of migration commands. but should i?
> 
> or what else am i missing?

You probably migrated this MacPorts installation from an older machine,
which still used 32-bit as default build architecture.

After reinstalling MacPorts as recommended by the migration procedure,
please compare your macports.conf against the macports.conf.default. You
will find both files in /opt/local/etc/macports/ after installing the
latest MacPorts version.

Most probably you even want to replace the macports.conf entirely with
the default options unless you made any changes on purpose.

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

Re: libjpeg vs. libjpeg-turbo

[Rainer Müller]

On 2015-05-20 12:49, René J.V. Bertin wrote:
> On Wednesday May 20 2015 12:11:08 Clemens Lang wrote:
> 
> How do libjpeg-turbo and mozjpeg compare except in the latter's
> features to create slightly smaller files (at what computing cost)?

http://www.libjpeg-turbo.org/About/Mozjpeg

In short: mozjpeg produces smaller files by using progressive JPEG
encoding, but it is significantly slower. Note this only applies to
encoding, the images are compatible with any JPEG decoder.

> That would still require all ports to use this kind of dependency. If
> both alternatives are really interchangeable, I'd rather see them as
> variants of a master port, e.g. port:jpeg with +turbo being the
> default variant and +moz (or +mozjpeg) being an alternative variant.
> That would provide users with choice without imposing an unnecessary
> change on port maintainers. With (at least) Debian and Ubuntu this is
> handled by the jpeg-turbo packages indicating that they replace (are
> alternatives to) the standard libjpeg versions; sadly MacPorts
> doesn't have a similar feature. I've already raised this idea a while
> ago, but cannot remember how it was received...

Variants are not useful for completely different software projects with
distinct releases and versioning schema. What would you use in the port
version?

Yes, having virtual "provides" dependencies would solve this. But we
don't have that and we are currently using the path: style dependencies
to achieve something similar. Discussions about adding such features
should take place on macports-dev.

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

Re: libjpeg vs. libjpeg-turbo

[Rainer Müller]

On 2015-05-20 10:46, Clemens Lang wrote:
> I would rather like to see us drop libjpeg completely and replace it with
> libjpeg-turbo. Does anybody object to this approach?

As the maintainer of mozjpeg, I have started experiments locally by
replacing port:jpeg with path:lib/libjpeg.dylib:jpeg in various Portfiles.

As of mozjpeg @3.0, it is ABI compatible with libjpeg-turbo, so
interchanging these two works without problems.

Both mozjpeg and libjpeg-turbo install libjpeg.8.dylib, but the jpeg
port installs libjpeg.9.dylib. Therefore, jpeg cannot simply be replaced
with one of the others without rebuilding all dependents.

Rainer


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

Re: error while "building uhd"

[Rainer Müller]

On 2015-03-04 23:09, Jim Goudie wrote:
> Office:~ Jim$ vim
> /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_science_uhd/uhd/main.log
> 
> :info:build
> /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_science_uhd/uhd/work/uhd-003_008_002/host/lib/usrp/common/ad9361_driver/ad9361_synth_lut.h:11:
> error: integer constant is too large for ‘long’ type

On which version of OS X are you building this? (`sw_vers`)
Which version of Xcode? (`xcodebuild -version`)
Is this a 32-bit machine?

I guess the constants in this file would need to be declared with a '.0'
suffix for double.

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

Re: sane-backends

[Rainer Müller]

On 2015-03-01 21:56, hweber wrote:
> sane-backends on macports is on @1.0.24. 
> http://www.sane-project.org/sane-mfgs.html lists sane-genesys 1.0-63. 1.0-63 
> does not work unter OSX 10.10? What is the reason that macports stays at 
> 1.0.24? My new scanner needs 1.0-63 ist there anywhere a solution?

Don't get confused by these version numbers. As listed on top of the
website, the current stable version of sane-backends is 1.0.24, which is
also the version MacPorts provides.

This version number 1.0-63 listed is for the genesys backend, which is
distributed as part of sane-backends.

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

Re: [MacPorts] #46947: sox: please update to @14.4.2

[Rainer Müller]

On 2015-02-26 15:19, Jan Stary wrote:
> Going through the log of the build,
> I see that it not only checks for the libraries
> mentioned as dependencies in the Portfile,
> but also checks for ncurses and libiconv.
> 
> I don't see them mentioned anywhere in SoX;
> is this somehow internal to macports?
> 
> The resulting sox binary does not depend on them.

The complete hierarchy of dependencies is checked to ensure that
everything is in place as it should be.

You can see the hierarchy with the following command:

$ port rdeps sox

To condense the list, each port is only listed once when it appears the
first time. You can also take a look at the full list, but be warned
that this can become quite a long list.

$ port rdeps --full sox

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

MIsbehaving DNS servers (was: Re: {distfiles, packages, rsync, trac}.macports.org are back up)

[Rainer Müller]

On 2014-11-27 20:01, Dave Horsfall wrote:
> Which reminds me: I erred in a previous post about Mac/FreeBSD ports 
> recovering in the face of "helpful" ISPs interfering with the DNS; FreeBSD 
> merely keeps trawling through a local list (updated every so often) until 
> it gets a bite, ignoring any silly responses along the way.
> 
> I really must set up my own name server, instead of relying upon my broken 
> ISP (they are The Phone Company, after all, and own all of the 
> infrastructure).

Usually MacPorts is able to detect this kind of DNS problems, in which
case the following link will be provided:

https://trac.macports.org/wiki/MisbehavingServers

We can detect the problem by resolving a domain name that definitely
does not exist, but we can never be sure whether the DNS response for
any other domain name in the list of mirrors is valid or not. We only
guess if we get HTML content instead of the expected tarball, it is
probably this problem.

Furthermore, just skipping over a bogus answer instead of NXDOMAIN would
be wrong in my opinion. It is a problem with the internet connection as
provided by your ISP, you should contact them and ask them to resolve
it. Hopefully, the deployment of DNSSEC in the (near) future will stop
this DNS hijacking anyway.

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

Re: {distfiles,packages,rsync,trac}.macports.org are back up (eom)

[Rainer Müller]

On 2014-11-27 18:58, Shreeraj Karulkar wrote:
> I am not entirely sure yet. Most people are off this week and I am on 
> vacation too. There has been a lot of activity one some of our servers and we 
> are having issues with disk space. 
> I'm trying to get them to be stable with the limited bandwidth I currently 
> have. 

Thank you for the update. I appreciate you are doing this from vacation.
I hope you can get more detailed insight once you are back.

Rainer

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

Re: {distfiles,packages,rsync,trac}.macports.org are back up (eom)

[Rainer Müller]

On 2014-11-27 18:30, Dave Horsfall wrote:
> Out of curiosity, why this sudden instability?

This is something the server admins at Mac OS Forge should answer and I
added them to CC in this message.

I saw multiple reports due to unreachable servers over the last weeks.
We either need to stop that from happening or make the sync/selfupdate
process more reliable with an automatic fallback to other mirrors.

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

Re: anti-shellshock suggestions

[Rainer Müller]

On 2014-09-29 10:53, René J.V. Bertin wrote:
> Couple points:
> 
> - `port livecheck bash` indicate we're 2 point releases behind

Your ports tree must be out of date, bash is currently @4.3.27.

> - how about adding a variant to the bash (and dash) portfiles allowing users 
> to copy the MacPorts version into /bin (moving the original version to 
> something like bash.macportsBackup if that backup doesn't yet exist)?

MacPorts policy is to never touch files provided by Apple. If you want
to do that, you should do it knowing that it is your own risk.

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

Re: Warning When Using OpenDNS

[Rainer Müller]

On 2014-05-22 12:01, Jamie Paul Griffin wrote:
> I was looking into additional online security measure a while ago. I cam 
> across some info discussing the benefits of using OpenDNS name servers which 
> I then decided to try. 
> 
> Since doing that, port prints a warning: Warning: Your DNS servers 
> incorrectly claim to know the address of nonexistent hosts. This may cause 
> checksum mismatches for some ports.
> 
> What are the thoughts on this, is using their name servers beneficial and 
> will it likely cause issues when using port?

Here is some more information on the MacPorts wiki:
https://trac.macports.org/wiki/MisbehavingServers

FYI, the next release will also print the link to this page in the
message in the hope that it explains why this is happening.

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

Re: CFLAGS

[Rainer Müller]

On 2014-04-30 15:14, Thomas Bodlien wrote:
> Is port picking up CFLAGS and LDFLAGS environment-variables?

If you mean those set in the environment before running the port
command, no. CFLAGS/LDFLAGS are set according to the Portfile. This is
by design to make the builds reproducible and to achieve compatibility
with pre-compiled binary archives.

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

Re: macports ssh slower than osx ssh

[Rainer Müller]

On 2014-04-09 16:47, Brad Allison wrote:
> Why is macports ssh 4 seconds slower than osx built in ssh when using
> gss-api?
> 
> brad-allison-pro:~ brad.allison$ time /opt/local/bin/ssh -2 -v -l root
> m2inf-kerberostest-01 date > /tmp/kerbtest-ssh-macports.txt 2>&1
> 
> real0m20.890s
> user0m0.007s
> sys 0m0.008s
> 
> 
> brad-allison-pro:~ brad.allison$ time /usr/bin/ssh -2 -v -l root
> m2inf-kerberostest-01 date > /tmp/kerbtest-ssh-osx.txt 2>&1
> 
> real0m15.894s
> user0m0.011s
> sys 0m0.008s

It's really hard to tell where the additional time is spent without
doing full profiling of the processes.

Maybe the implementation in kerberos5 used by the openssh port is just
slower than Heimdal used by the system openssh?

Could also be that the MacPorts version makes more attempts to verify
different host keys (for example supporting ECDSA) and that adds
additional filesystem lookups and round trip times.

Rainer

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

Re: pbzip2 isn't faster

[Rainer Müller]

On Fri, 04 Apr 2014 20:39:26 -0500, Ryan Schmidt wrote:
> Since the MacPorts build system now accommodates adding third-party
> software into the build, if pbzip2 works reliably, it might be nice
> to include it with MacPorts and use it at least for compression and
> decompression of the archives, if not also for bzip2 distfiles and
> patchfiles.

Fedora is currently in the progress of switching to lbzip2. I don't
know how if this implementation is related to pbzip2, but the goals
sound similar.

https://fedoraproject.org/wiki/Changes/lbzip2

We do not have a port for it yet, though.

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

Re: A smarter migration behaviour (was Re: usage numbers for macports vs. homebrew?)

[Rainer Müller]

On 2014-03-22 19:48, Davor Cubranic wrote:
> The amount of traffic to this list that comes down to “you need to run the 
> migration steps from the [Migration] page” is astounding, and it must be a 
> real drain on the time of those who by now must have answered hundreds of 
> such questions.
> 
> It seems to me like we could go a long way toward solving the problem by:
> 
> 1. saving at install time the output of `uname -r` (OS release) into a file 
> in /opt/local/etc/macports/
> 2. every time `port` is run, compare the stored with the current value and 
> stop with an error message if they differ (or more likely if they differ in 
> more than the patch level)

You actually describe what is already coming with the next release:
http://trac.macports.org/changeset/113478

> The error message could direct the user to the Migration page. (Even better 
> if we had a new `port` action to perform the migration steps automatically, 
> even if it wasn’t particularly picky whether a port is being reinstalled 
> because it was requested or simply active at the time of the migration.)

Doing the migration automatically is difficult, because you first have
to remove all ports for clean builds and only then start installing the
previous set of ports.

What would be the strategy for a resume if any port fails to install?
What if the user gives up at some point, never wants to complete the
migration, and starts installing unrelated ports?

We are already going too far into a development discussion in this
thread for the users mailing list, so I'll stop at this point.

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

Re: usage numbers for macports vs. homebrew?

[Rainer Müller]

On 2014-03-18 22:09, James Berry wrote:
> For the website, I think the following would help:
> 
>  * Updated design, colors, etc.

That has always been the plan, but it just needs someone to do it.
I think the last update on the website design dates back to 2007...

I would even replace the website with the Trac wiki front page
altogether, also getting rid of one of the duplicated installation
instructions on website/wiki/guide. However, some users seem to like the
port search the current website provides (which is broken right now
since the server migration).

>  * More integrated web app with better access to ports, etc.

Which could also be integrated with the upcoming statistics gathering in
the next MacPorts release.

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

Re: Vim upgrade in latest MacPorts lost gvim

[Rainer Müller]

On 2014-03-13 05:52, Jim Graham wrote:
> On Wed, Mar 12, 2014 at 09:09:47PM +0100, Clemens Lang wrote:
>> The best GUI for Macs probably is MacVim (from the equally named port),
>> which uses a native GUI.
> 
> But is MacVim the vim/gvim distro from vim.org?  Or is it some variant
> that may or may not support all of what vim/gvim does? 

Yes, it is using the same code as the terminal vim, but provides a GUI
on top. Similar to the way it is done in gvim with GTK+ or other toolkits.

It also provides a mvim command which would be the equivalent of gvim.

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

Re: Vim upgrade lost spelling and syntax highlights

[Rainer Müller]

On 2014-03-05 00:08, LuKreme wrote:
> On 04 Mar 2014, at 11:34 , Rainer Müller  wrote:
>> On Tue, 04 Mar 2014 09:42:32 -0700, LuKreme wrote:
>>> Can't open file /opt/local/share/vim/syntax/syntax.vim
>>> Warning: Cannot find word list "en.utf-8.spl" or “en.ascii.spl"
>>
>> Do you customize the 'runtimepath' setting in any way in your .vimrc?
> 
> No.
> 
> The only thing that has anything like a path is 
> 
> set spellfile=~/.spell.en.add

Maybe some plugin changes runtimepath? Try without your .vimrc. The
correct path for these files would be at /opt/local/share/vim/vim74/
(it's missing the vim74 directory in the message above...).

I can't think of another reason why else vim would look in the wrong
directory...

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

Re: Vim upgrade lost spelling and syntax highlights

[Rainer Müller]

Hello,

On Tue, 04 Mar 2014 09:42:32 -0700, LuKreme wrote:
> Can't open file /opt/local/share/vim/syntax/syntax.vim
> Warning: Cannot find word list "en.utf-8.spl" or “en.ascii.spl"

Do you customize the 'runtimepath' setting in any way in your .vimrc?
This might happen if you remove default system directories. Maybe you
hardcoded /opt/local/share/vim/vim73/, but now it needs to
be /opt/local/share/vim/vim74/?

> and none of the spelling or syntax coloring loads. Don’t see anything
> obvious in the variants.
> 
> vim @7.4.052 (editors)
> Variants: athena, big, breakindent, cscope, gtk1, gtk2,
> [+]huge, lua, motif, perl, python, python25, python26, python27,
> python31, python32, python33, ruby, ruby18, ruby19, ruby20, small,
> tcl, tiny, universal, x11, xim

The port info output does not show what you actually installed.
Please check 'port installed vim' instead.
 
> Also, isn’t 7.4.052 a bit old? I thought the current was 7.4.192?

It was released in October, so it's not really old. This is also the
version on which the current MacVim release is based on. Be aware that
not all patches always affect vim built for Mac OS X in MacPorts, as
they may target Windows or other platforms.

Is there a particular bug fix from a later patch you are looking for?

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

Re: -std=c++11 or -std=gnu++0x

[Rainer Müller]

On 2014-02-02 10:19, Christopher Dawes wrote:
> #include 
> #include 
> #include 

Unrelated, but in C++ you should use  and  instead of
the .h files.

> Now trying to compile gives:
> chrisd$ g++ -std=c++11 -o test test.cpp
> Undefined symbols for architecture x86_64:
>   "isalnum(int)", referenced from:
>   _main in ccDuU6gp.o
> ld: symbol(s) not found for architecture x86_64
> collect2: error: ld returned 1 exit status

There is a problem with the header files shipped with OS X. This is
tracked in this ticket:

  http://trac.macports.org/ticket/41033

The problem only exists with the combination of g++-mp-4.* and
-std=c++11, compiling earlier C++ code using g++-mp-4.* should work. The
best known workaround is to use clang++ instead of g++ for C++11 code.

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

Scheduled downtime on Jan 28, 15-19 UTC

[Rainer Müller]

Hello,

there will be a scheduled downtime for all MacPorts services due to
maintenance at our hosting provider MacOSforge. The servers will be
available with new IP addresses after the downtime, which will take up
to an hour until the change propagates in DNS due to caching.

The services will be affected on Tuesday, January 28th, from 15:00 to at
least 19:00 UTC.

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

Re: Where do I find the changelog of a port package?

[Rainer Müller]

On 2013-11-28 11:45, Kurt Pfeifle wrote:
> Sometimes I'm interested in finding out the differences between the old
> and the new-to-be installed version of a port.
> 
> Is there a canonical way to get access to a changelog?
> 
> I'm interested in the upstream changelog within the sources (should
> there be one)  as well as in the changes the port maintainer might have
> applied (to portfile, to sources, whatever...)

There is no way to view the upstream ChangeLog as that varies a lot
across different projects. For the changes done to a port by the
maintainer, you can only view the Subversion log directly.

For example, for the vim port this would be here in Trac:
https://trac.macports.org/log/trunk/dports/editors/vim

There is also a tool in our contrib directory which automates this
process. port-whatsnew finds the date you installed a port and presents
the Subversion commit log since then:

https://trac.macports.org/browser/contrib/port-whatsnew/port-whatsnew
(also pending ticket http://trac.macports.org/ticket/38110)

> Also, the "port list someport" shows the version info only in an
> incomplete way. In order to see more, you need to run"port installed
> someport".
> 
> Is there a way to get the same version info in"port list" as I get
> with"port installed"?

https://trac.macports.org/wiki/FAQ#portlist

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

Re: Question about a part of tex-live

[Rainer Müller]

On 2013-10-25 17:41, Comer Duncan wrote:
> I have recently noted that I need to add revtex4.1 to the tex-live
> distribution I installed from macports.  Does anyone know how I can do
> this? I am afraid that if I just copy the revtex4.1 distribution to
> /opt/local/share/texmf-texlive/tex/latex I may well screw up by not
> making the permissions right and not appropriately adding revtex4.1 to
> the database.  

I strongly advise against making any changes to /opt/local manually.

In your case, check this list of TeX Live Packages available in MacPorts
and search for revtex:
https://trac.macports.org/wiki/TeXLivePackages

So, revtex and revtex4 are actually available in TeX Live and are
provided by the port texlive-publishers. Just use the following command
to install the port and you should be done:

  sudo port install texlive-publishers

If you would need a TeX package that is not available in TeX Live or you
need a newer version than what is packaged in MacPorts, install it to
your home directory at ~/texmf (TEXMFHOME) instead.

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

Re: guntar missing on Mac OS X Maverics

[Rainer Müller]

On 2013-10-23 17:06, Watson Ladd wrote:
>>> Will make&make install 2.2.0 from source also have this issue?
>>
>> ./configure && make && make install should work fine.
> Sadly it isn't working for me: complaining about missing Tcl
> configuration. I'll try to figure out what is going on and fix it.

Do you have the latest Xcode with Command Line Tools? Try 'xcode-select
--install' which will present you both the option to either install
Xcode using the Mac App Store (afterwards install the Command Line Tools
from Xcode Preferences) or install the Command Line Tools only.

Both options will give you a working MacPorts, although some ports may
require Xcode anyway, so this would be the preferred option.

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

Re: guntar missing on Mac OS X Maverics

[Rainer Müller]

On 2013-10-23 12:49, Toshiyuki Kamada wrote:
> I managed to symlink /usr/bin/tar to /usr/bin/gnutar as a quick avoiding 
> glitch.

If you install from source–which is the recommended way at the moment
until a disk image is available–you avoid this problem.

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

Re: poedit @1.5.7_1: grayed out menu entries, disabled window

[Rainer Müller]

Hi,

I am the maintainer of poedit.

On 2013-10-16 11:17, Davide Liessi wrote:
> I have just upgraded my installed ports and I have a problem with poedit.
> All menu entries are grayed out and the program window is completely
> disabled (if I click anywhere in the program window I get the alert
> sound from the system and nothing happens).
> Also, the only way to close the program is using "force quit".

I don't have any problems on Mac OS X 10.8.5. I would assume this to be
related to the latest update of wxWidgets to 3.0.0.

$ port -q installed wxWidgets-3.0
  wxWidgets-3.0 @3.0.0_1 (active)

Please make sure you also have this version (which should be the case
after upgrading poedit, but just to be sure).

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

Re: Fwd: macports instal pkg - alert msg

[Rainer Müller]

On 2013-10-11 12:22, uga...@talktalk.net wrote:
> I have completed first 'successful' MacPorts instal, but something seems
> not to be quite right. 
> 
> What have I done, and how do I put it right?
> 
> Following the MacPorts guide, I ran (and I am not sure I needed to do
> this); sudo port pkg mypaint

Creating a pkg is only necessary if you want to redistribute this
package. Otherwise just use a normal installation:

  sudo port install mypaint


In case you really want to redistribute this package, you should not use
/opt/local as prefix and /Applications/MacPorts as applications_dir to
create the package in the first place. Please choose a different prefix
to avoid conflicts.

> [...]
> I seem to have a duplicate tree structure within destroot. Is this as it
> should be? I now have;
> HD/opt/local/var/macports/build/ _opt_local_var_macports. . .
> /MyPaint/work/destroot/opt/ . . (see above)
> and;
> HD/opt/local/var/macports/build/ _opt_local_var_macports. . .
> /MyPaint/work/destroot/Applications/MacPorts/MyPaint.app

This looks correct.

> A further MyPaint.app is located. HD/Applications/MacPorts/MyPaint.pp

This is the installed version from the pkg installer.

> Previously, I had installed an earlier release of MyPaint using a pkg
> installer and this located the directories (bin, include, lib, & share)
> listed above in destroot/ directly in HD/opt/ directory.

Then it was probably not created by a default MacPorts installation,
which uses /opt/local.

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

Re: Upgrade outdated in Mavericks

[Rainer Müller]

On 2013-10-09 19:48, Ryan Schmidt wrote:
> 
> On Oct 9, 2013, at 11:27, Brandon Allbery wrote:
>> On Wed, Oct 9, 2013 at 12:21 PM, Gary Little wrote:
>>> Is there a solution to running running “upgrade outdated” after installing 
>>> the GM for Mavericks? 
>>
>> Did you follow http://trac.macports.org/wiki/Migration ?
> 
> If there is still a problem after following Migration (and I expect there 
> will be the usual numerous issues) you can file a bug report so that we can 
> keep track of the problem but we probably won't be able to fix it until 
> Mavericks is released publicly.

Seems like we never created a wiki page listing specific problems with
Mountain Lion, although we did this for Lion [1] and Snow Leopard [2].
Distinguishing between Lion and Mountain Lion is hard using the limited
Trac query language...

Would it make sense to do this once again for Mavericks?

Rainer

[1] https://trac.macports.org/wiki/LionProblems
[2] https://trac.macports.org/wiki/SnowLeopardProblems
___
macports-users mailing list
macports-users@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-users

Re: rmtrash

[Rainer Müller]

On 2013-10-08 09:50, David Epstein wrote:
> Here is a record of what I typed and the response
> 
> H2:~% port search rmtrash
> rmtrash @0.3.3_2 (sysutils)
> move the file to OS X's Trash
> H2:~% sudo port install sysutils
> Error: Port sysutils not found
> 
> Can someone enlighten me on what the situation is with rmtrash? The above two 
> port commands seem to contradict each other, or am I misinterpreting?

In this port search output, "sysutils" is the category of the port.
Please use this command to install rmtrash:

  sudo port install rmtrash

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

Re: Goffice build failure

[Rainer Müller]

On 2013-10-04 14:28, Mark Bestley wrote:
> I tried to install goffice but got failure
> 
> Error: org.macports.archivefetch for port goffice returned: 
> gtk-osx-application must be installed with +gtk3.
> 
> I uninstalled gtk-osx-application and then retried goffice but got the same 
> error
> 
> 
> How can I install goffice wothout explicitly finding something it depends on 
> and manually install that?

See also these tickets with patches for goffice. Although linking
against gtk-osx-application without declaring a dependency would
probably be a problem:

https://trac.macports.org/ticket/40553
https://trac.macports.org/ticket/40697

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

Re: Xcode 5.0 ok?

[Rainer Müller]

On 2013-09-20 09:46, Tabitha McNerney wrote:
> Has anyone tried upgrading to Xcode 5.0 now that its being made
> available by Apple publicly? Are there any concerns or flags to be aware
> of with Xcode 5 and MacPorts 2.2.0 on OS X 10.8.4 or 10.8.5?

So far I did not experience any issues.

Before I was able to install the Command Line Tools of Xcode 5.0, I was
asked to enter my Apple ID to authenticate me as developer. The download
did not work at first due to allegedly missing authorization. A few
hours later it worked, though.

Is a developer account now required for the Command Line Tools for
everyone? Since Xcode can be downloaded in the App Store with just a
regular account this seemed strange to me.

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

Re: How to get binaries if they are available

[Rainer Müller]

On 2013-09-07 10:16, Barrie Stott wrote:
> I did an upgrade recently and a binary was installed. In the console log were 
> a couple of lines: 
> 
> --->  Attempting to fetch bash-completion-2.1_5.darwin_10.noarch.tbz2 from 
> http://mse.uk.packages.macports.org/sites/packages.macports.org/bash-completion
> --->  Attempting to fetch bash-completion-2.1_5.darwin_10.noarch.tbz2.rmd160 
> from 
> http://mse.uk.packages.macports.org/sites/packages.macports.org/bash-completion
> 
> As I understand it, the second one is the binary because of the rmd160 part 
> but it seems to be trying to get a non-binary first and only trying to get a 
> binary when that fails.

Actually the first one is the binary package, the second is the detached
signature file using the RIPEMD-160 algorithm. That is required to
ensure this file was actually built by a of our buildbots. The detached
signature file is only fetched if the download of a binary was successful.

> Is this because only one of binary/non-binary ever exists at a packages site?
> If not, how can I get a source package only when there is no binary?

MacPorts will automatically build from source if no binary archive is
available.

Rainer

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

Re: Console Vim

[Rainer Müller]

On 2013-09-05 09:33, Phil Dobbin wrote:
> Hi all.
> 
> Vim 7.4 is out & MacPorts's version is way behind (7.3.762).
> 
> Is 7.4 coming in the near future?

Yes.

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

Also, don't trust version numbers too blindly. Vim 7.4 is mostly a
bugfix release. The only new major component is the new regex engine
which you probably won't notice much in daily work.

Anything else specific you need from the new version?

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

Re: tmux needs an older file on 10.4.11

[Rainer Müller]

On 2013-09-03 09:18, Jan Stary wrote:
> I am trying to build sysutils/tmux on MacOSX 10.4.11
> It fails because 10.4.11 (Darwin 8.11.0) does not have
> libproc.h that is included by tmux's osdep-darwin.c:
> 
>   osdep-darwin.c:22:21: error: libproc.h: No such file or directory
> 
> This problem has been encountered before,
> and there is even a known workaround.
> use an older version of osdep-darwin.c
> 
> http://sourceforge.net/mailarchive/forum.php?thread_name=51A035A8.6090504%40gmail.com&forum_name=tmux-users

There is also a ticket tracking this problem:

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

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

Re: Macports does what I want (?) not what I say

[Rainer Müller]

On 2013-07-04 14:44, Aljaž Srebrnič wrote:
> The answer as to why are your command line options ignored by
> MacPorts is quite simple. I suppose (and here I'm gonna guess) you
> didn't really do a "port upgrade percona-toolkit" but rather a "sudo
> port upgrade percona-toolkit". The thing is, sudo ignores all your
> aliases! but since you "shadowed" a command (port) with an alias
> (alias port="port -cn") sudo didn't complain and happily executed the
> port command (with no options!).

This is a correct description of the situation. Although this is not
helping in the initial discussion, I want to share an unobvious feature
of bash with you that helps in situations like this. Quoting the man page:

  If the last character of the alias value is a blank, then the next
  command word following the alias is also checked for alias expansion.

Therefore, add the following to your .bashrc:

  alias sudo='sudo '

The space at the end tells bash to look up aliases for the next word.
This means that typing "sudo foo" will lead to 'foo' being looked up as
a shell alias.

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

Re: Visualized MacPorts Ports

[Rainer Müller]

On 2013-07-03 18:16, Jean-François Caron wrote:
> I'm wondering if there is a MacPorts equivalent to the python-apt
> package, for getting MacPorts information directly within python.  Or
> otherwise a good way to access the MacPorts list of ports,
> dependencies, and categories from Python.

There is no API for Python. However, you can query the information
straight-forward with the port tool.

List of all available ports:
  port -q echo all

List of all dependencies of a specific port:
  port -q echo depof:$NAME

There is no such thing as suggest/recommends in MacPorts, but it still
has different kinds of dependencies. On the one hand there are
depends_fetch, depends_extract and depends_build, that are only required
for building the port. On the other hand there are depends_lib and
depends_run which are required at runtime. The command above using
depof: includes all of them.

I guess it's more interesting to see runtime dependencies for such a
graph, but you could also add both build and runtime dependencies with a
different weight as in the graph for Ubuntu. Anyway, we should
distinguish between these two types of dependencies.

Retrieving only the runtime dependencies of a specific port in a nice
line-wise format proves to be a lot harder:

port -q info --depends_lib --depends_run $NAME |tr ',' '\n' |awk -F: 'NF
> 0 {print $NF}'

I hope that helps you to get started for a similar project. In case you
need more assistance with the port command, just ask :-)

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

Re: Code signing issues with macports-gcc48 compiled binaries

[Rainer Müller]

On 2013-06-30 20:25, Nicolas Hatier wrote:
> Compiled with gcc 4.8 (macports)
> 
> > /opt/local/bin/gcc-mp-4.8 a.cpp
> > security unlock-keychain ~/my.keychain
> password to unlock /Users/me/my.keychain: 
> > codesign -f -s "identity" --keychain ~/my.keychain a.out
> codesign_allocate: object: /Users/me/a.out malformed object (unknown
> load command 9)
> a.out: object file format invalid or unsuitable
> (failure)

Can you please provide the output of 'otool -l a.out' to see what the
offending load command 9 actually is?

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

Re: Suggestion: Time to Use Trello?

[Rainer Müller]

On 2013-06-26 13:19, Rodolfo Aramayo wrote:
> Many projects out there are transitioning to trello
> 
> https://trello.com/

What the heck does it do? The website tells me something about
organizing things. There seems to be an app, but also a web page, so is
it a service? Sorry, but I am unable to figure out what this is.

Anyway, how would this be helpful in the context of using MacPorts?

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

Re: duplicate listing of ports by `port list installed'

[Rainer Müller]

On 2013-06-19 12:33, j. van den hoff wrote:
> I have these questions:
> 
> 1.
> the duplicate listings do not hint at any relevant corruption of my
> macports setup, right?
> 
> 2.
> what is the reason for the occurrence of the duplicate listings?
> 
> 3.
> is there a way to get rid of the duplicates?

https://trac.macports.org/wiki/FAQ#portlist

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

Re: bash completion error

[Rainer Müller]

On 2013-05-12 12:28, Phil Dobbin wrote:
> I've installed bash & bash-completion from MacPorts & when adding the
> required line to my bash_profile to enable the completion as advised, I get:
> 
> 'bash: [: 05b: integer expression expected]'
> 
> I've stared at it 'til I'm blue in the face but I can't see why it
> expects an integer.
> 
> By the way this is on an old 800MHz G4 PowerMac running 10.4.11 that I
> bought yesterday for a fiver if that makes any difference at all.

Are you using /opt/local/bin/bash? As stated in 'port notes
bash-completion' you need at least bash 4.1. I don't know which version
of bash shipped with 10.4.11 as /bin/bash.

The bash_completion script tries to detect old bash versions, but maybe
it's even too old for that check to work properly?

Even on later versions of Mac OS X, your /bin/bash is too old as Apple
left it at 3.2, the last version available under GPL-2 and later
versions are GPL-3.

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

Re: MacPorts wants to install apple-gcc42 on 10.6 all of a sudden?

[Rainer Müller]

On 2013-04-22 16:16, "René J.V. Bertin" wrote:
>> As said, if there is, this is unsupported. You should instead file bugs
>> for the ports that break with clang so they can have clang or broken
>> versions of it selectively blacklisted.
> 
> Sure, but apart from that a user can have good reasons to use a compiler 
> (and/or options) of choice, no? Just one of them: I was amazed to see how 
> much better autovectorisation has become in gcc 4.7 - in one benchmark of 
> code taken from Perian, the 'scalar' version of a YUV conversion routine all 
> of a sudden executed as much faster as a handcoded SSE2 version as that 
> hand-coded version executes w.r.t. the scalar version using gcc-4.2 or MSVC 
> 2010 ...
> I'm using gcc-mp-4.7 whenever I can ever since, not regretting it a bit. 

We do not have resources to handle build errors induced by using various
versions of gcc provided by MacPorts. The general use case is to get a
working installation. Optimizations of the kind described by you are for
intense tasks such as scientific computation or video encoding in
multimedia applications.

For developers, there is a way to set default_compilers from
macports.conf or from the command line to override the automatic
detection based on the Xcode version, but that is not in the default
configuration file. It is meant for developers only and I expect those
who are meant to use this can figure out how it works :-)

Also note that the toolchains provided by Apple (both the old gcc 4.2
and llvm/clang) are patched for use on Mac OS X. Most importantly that
is the introduction of a driver around the normal compilers invoked with
the -arch flags. This allows to build universal binaries in one step,
which is not possible with mainline gcc. Using gcc from MacPorts for
compiling other ports reduces the available features and makes use of
the +universal variant impossible.

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

Re: reconfigure doesn't take?

[Rainer Müller]

On 2013-04-21 00:07, Roger Pack wrote:
> Possibly this is caused by having a version of macports "already in
> the path"?  Can anyone confirm?  Maybe configure should fail or warn
> in this case, if so?

I haven't checked the original problem yet, but yes, having another
MacPorts installation in PATH will cause problems. You want to link
against software provided by Mac OS X and not from the other MacPorts
installation. The configure script automatically removes the target
prefix from PATH, but not any other MacPorts installation.

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

Re: A few random usability suggestions...

[Rainer Müller]

On 2011-11-19 07:23, Roger Pack wrote:
> If I do this:
> $ sudo port install vlc -f

This does not do what you expect, but it is correct syntax. This would
deselect a variant named "f".

> The "help" syntax might be expandable a bit..
> 
> $ port help install
> Usage: install
> 
> Installs the given ports
> 
> (doesn't list any options available to the install command?)

This one should be fixed soon once I get around merging the new help
system to trunk (and of course, the next release after that...).

https://trac.macports.org/wiki/NewHelpSystem

> Also it seems to be missing a "reinstall" command...perhaps one could
> be added, perhaps like the equivalent of
>  sudo port uninstall suchAndSuch
>  sudo port clean –all suchAndSuch
>  sudo port install suchAndSuch
> or the like [?]

Right, there is no 'port reinstall'. Although as a workaround this one
works to force a reinstallation of a port:

  sudo port -n upgrade --force suchAndSuch

> Also I would have expected this to work:
> $ sudo port install twolame # it installs binary twolame
> $ sudo port install -s twolame # it "reinstalls, but from source"
> (currently it "does nothing")
> 
> At least output something like "twolame is already installed" but,
> better yet, I had hoped that it would basically reinstall it, from
> source, realizing that its initial installation had been from a binary
> package.

There is no information stored whether a port was installed from a
pre-compiled archive or from source. In fact, install always uses an
archive, just sometimes it has to be built locally first.

To force a reinstallation from source:

  sudo port -s -n upgrade --force suchAndSuch

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

Re: github source

[Rainer Müller]

On 2013-04-20 22:50, Roger Pack wrote:
> As a note, in case there's a poll or anything, here's my +1 for at
> least having a github mirror, if not moving to github entirely for
> trunk development.

What kind of benefit do you expect from a mirror on github?

The channel to submit bug reports and patches is our Trac instance
hosted by MacOSforge. Also note there are read-only git repositories
available already:

http://www.macosforge.org/post/git-mirrors/

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

Re: port info problem

[Rainer Müller]

On 2013-04-09 13:23, Federico Calboli wrote:
> On 9 Apr 2013, at 12:02, Aljaž Srebrnič  wrote:
>> well, that is because in your variants.conf you have disabled x11 (-x11), 
>> but the default variants of R-framework specifies +cairo, which requires 
>> +x11.
> 
> I know what variants I have disabled, and I do not want to change them.  All 
> I am trying to do is to get some info about a port, and I am gobsmacked my 
> ability to get info about a port is tied to my variants choices.  

[...]

>> In the meantime, you can check out the port information by entering:
>>
>> $ port info R-framework -cairo
> 
> Thanks, that kind of does it, but port info should be variant independent -- 
> it's just damn info after all!

No, the output is not independent of the variants. Selecting a variant
changes the output given by 'port info', most often the required
dependencies.

For the info command, the Portfile is evaluated with the variant
selection specified on the command line and/or from variants.conf.
That's the intended behavior.

As an alternative, there is also 'port info --index' which shows
information from the PortIndex only, without taking any dynamically
computed information into account, for example options set in variants
or selecting default variants.

What you noticed there is a bug in the Portfile and needs to be fixed by
its maintainer. The default_variants +cairo should not be applied when
-x11 is selected.

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

Re: GTK2_RC_FILE and ~/.gtkrc-2.0 ignored

[Rainer Müller]

On 2013-03-22 01:07, Kevin Layer wrote:
> I've googled and googled and tried a bunch of things, but I can't get
> GTK2 installed via macports to use any theme.  I did this
> 
>   # port install gtk-theme-switch gnome-themes
> 
> and I even downloaded themes from here
> 
>   http://art.gnome.org/themes/gtk2 
> 
> and changed my ~/.gtkrc-2.0 file and GTK2_RC_FILE env variable to
> point directly to the gtkrc in the theme, but nothing works.  The
> buttons and everything else in the app looks the same before and after
> all this work.
> 
> Anyone have ideas I can try?   Thanks.

I don't know where I would start looking. However, I can tell you that
the way you tried it works for me. I am using a ~/.gtkrc-2.0 with a
single line to select the Clearlooks theme from port gtk-engines2:

  gtk-theme-name = "Clearlooks"

I confirmed that the GTK theme is actually affected by this setting by
running the gtk-demo binary.

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