Re: anyone working on the KiCad port?

[Aljaž Srebrnič]

> On 26 ott 2016, at 17:15, Lars Sonchocky-Helldorf 
>  wrote:
> 
> Hi,
> 
> there is currently no port for KiCad ( http://kicad-pcb.org ) available for 
> MacPorts. Although googling for a port brought up the following two tickets:
> 
> https://trac.macports.org/ticket/47268
> https://trac.macports.org/ticket/50701
> 
> with a last relevant activity about 8 month ago. Are those abandoned or still 
> worked on?
> 
> Thanks a lot,
> 
>   Lars

Hello!
yes, I have a more-or-less functional port of KiCAD, there’s still some work to 
be done, though. I’ll upload the port to trac.

--
Aljaž Srebrnič a.k.a g5pw
My public key:  https://g5pw.me/key
Key fingerprint = 2109 8131 60CA 01AF 75EC  01BF E140 E1EE A54E E677

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

Re: Hang in rust installation

[Aljaž Srebrnič]

> On 28 set 2016, at 16:03, Jack  wrote:
> 
> Hi, Aljaž :
> 
> Thank you. So maybe I should wait for it.

Heh, it looks like you won’t wait for long, 1.12 is scheduled for release 
tomorrow, I’ll update the port ASAP. :)

--
Aljaž Srebrnič a.k.a g5pw
My public key:  https://g5pw.me/key
Key fingerprint = 2109 8131 60CA 01AF 75EC  01BF E140 E1EE A54E E677



signature.asc
Description: Message signed with OpenPGP using GPGMail
___
macports-users mailing list
macports-users@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-users

Re: Hang in rust installation

[Aljaž Srebrnič]

> On 28 set 2016, at 14:29, Jack  wrote:
> 
> Hi, everyone:
> 
> I tried to install Rust on my laptop which has upgraded to macOS Sierra.
> 
> And the installation hanged at the configure stage.
> 
> I tried to run the configure myself, and the message is this:
> 
>   configure: looking for target specific programs
>   configure:
>   configure: CFG_ADB  :=3D
>   rustc(66164,0x7fffa22c53c0) malloc: *** malloc_zone_unregister() failed=
> for 0x7fffa22bb000
> 
> This error is on rust's site(check this: 
> https://github.com/rust-lang/rust/issues/34674)
> 
> And I think they've fix this problem in the most recent dev version.
> 
> Is there anyway to fix this in macports?


Not yet, see https://trac.macports.org/ticket/52247
I’m slightly against moving to the development version.

--
Aljaž Srebrnič a.k.a g5pw
My public key:  https://g5pw.me/key
Key fingerprint = 2109 8131 60CA 01AF 75EC  01BF E140 E1EE A54E E677



signature.asc
Description: Message signed with OpenPGP using GPGMail
___
macports-users mailing list
macports-users@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-users

Re: clang 3.4 can't be configured (part of a selfupdate)

[Aljaž Srebrnič]

> On 26 lug 2016, at 14:13, [ftp83plus]  wrote:
> 
> Hello there, 
> 
> I am currently attempting a "port selfupdate" operation before installing two 
> ports I'd like to test.
> 
> However, it fails for a reason I don't understand:
> Terminal shows:
> --->  Verifying checksums for clang-3.4
> --->  Extracting clang-3.4
> --->  Applying patches to clang-3.4
> --->  Configuring clang-3.4
> Error: Failed to configure clang-3.4, consult 
> /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_lang_llvm-3.4/clang-3.4/work/build/config.log
> Error: org.macports.configure for port clang-3.4 returned: configure failure: 
> command execution failed
> Please see the log file for port clang-3.4 for details:
> 
> /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_lang_llvm-3.4/clang-3.4/main.log
> Error: Problem while installing clang-3.4
> To report a bug, follow the instructions in the guide:
> http://guide.macports.org/#project.tickets 
> <http://guide.macports.org/#project.tickets>
> 
> Pastebin of the main.log
> http://pastebin.com/VrEfMHzA <http://pastebin.com/VrEfMHzA>
Thanks for the notice. Could we get a pastebin of 
'/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_lang_llvm-3.4/clang-3.4/work/build/config.log’?

Could you note your OS version and hardware, too?

--
Aljaž Srebrnič a.k.a g5pw
My public key:  https://g5pw.me/key
Key fingerprint = 2109 8131 60CA 01AF 75EC  01BF E140 E1EE A54E E677

___
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 ...)

[Aljaž Srebrnič]

> On 18 mar 2016, at 11:29, Mojca Miklavec  wrote:
> 
> Hi,
> 
> All good things come to an end and so did the wonderful week that we
> spent together in Gozd Martuljek.
> 
> While I was initially hoping to see a larger group of people come
> together, the relatively small group of hackers eventually turned out
> to be the perfect recipe for boosting up the motivation, allowing us
> for very productive one-to-one learning experience and hacking
> sessions, resulting in quite satisfactory amount of work being done,
> new people getting confidence in hacking the core of MacPorts, new
> people joining the project, ...
> 
> The spirit was so motivating that our "chef" nearly had to tear us
> apart from the notebooks to make us come to the lunch and dinner.
> Nevertheless we still managed to find some time to enjoy the wonderful
> weather playing snowleyball on fresh air.
> 
> 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!

> 
> 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

--
Aljaž Srebrnič a.k.a g5pw
My public key:  http://bit.ly/g5pw_pubkey

___
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

[Aljaž Srebrnič]

> On 13 ott 2015, at 10:02, René J.V. Bertin  wrote:
> 
> Just saw this in a log of a build against the "nouveau" qt4-mac port:
> 
> PKG_CONFIG_PATH='/opt/local/libexec/qt4/lib/pkgconfig'
> 
> Voilà what putting everything in a sandboxy leads to, situations à la 
> HomeBrew that I don't even have a word for (madness?).

Oh, so *that's* why wireshark can’t find QtCore...

--
Aljaž Srebrnič a.k.a g5pw
My public key:  http://bit.ly/g5pw_pubkey



signature.asc
Description: Message signed with OpenPGP using GPGMail
___
macports-users mailing list
macports-users@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-users

Re: Error when starting python3

[Aljaž Srebrnič]

> On 20/set/2015, at 11:14, Glenn Ramsey  wrote:
> 
> Neither of those had any output.
> 
> I installed python 3.4, which worked OK, and then reinstalled 3.5rc4 and it
> works now. It must have been some sort of configuration issue as you 
> suggested.
> 
> Thanks for your reply.

Ok, glad you sorted it out!

--
Aljaž Srebrnič a.k.a g5pw
My public key:  http://bit.ly/g5pw_pubkey

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

Re: Error when starting python3

[Aljaž Srebrnič]

> On 14/set/2015, at 05:55, Glenn Ramsey  wrote:
> 
> Hi All,
> 
> I get this error when starting python3:
> 
> $ python3
> Python 3.5.0rc4 (default, Sep 14 2015, 13:58:59)
> [GCC 4.2.1 Compatible Apple LLVM 6.1.0 (clang-602.0.53)] on darwin
> Type "help", "copyright", "credits" or "license" for more information.
> Failed calling sys.__interactivehook__
> Traceback (most recent call last):
>  File
> "/opt/local/Library/Frameworks/Python.framework/Versions/3.5/lib/python3.5/site.py",
> line 380, in register_readline
>import rlcompleter
>  File
> "/opt/local/Library/Frameworks/Python.framework/Versions/3.5/lib/python3.5/rlcompleter.py",
> line 167, in 
>readline.set_completer(Completer().complete)
> AttributeError: module 'readline' has no attribute 'set_completer'
> 
> Do I need to install a dependency or is this a bug?

This looks like a configuration issue on your end, it works on my machine.
Could you post the output of:

echo $PYTHONSTARTUP

and

cat $PYTHONSTARTUP

Thanks,
Aljaž
--
Aljaž Srebrnič a.k.a g5pw
My public key:  http://bit.ly/g5pw_pubkey

___
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

[Aljaž Srebrnič]

Well, the answer lies in this command:
$ portrdeps percona-toolkit
The following ports are dependencies of percona-toolkit @2.1.5_0+perl5_16:
  p5.16-time-hires
perl5.16
  gdbm
gettext
  expat
  libiconv
gperf
  ncurses
  p5.16-dbd-mysql
p5.16-dbi
  p5.16-test-simple
  p5.16-sql-statement
p5.16-clone
p5.16-params-util
mysql5
  zlib
xz
  openssl
  tcp_wrappers
  readline
  p5.16-term-readkey

So all MacPorts does is upgrading all dependencies recursively. This is by 
default, I believe.

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!).

So, I either suggest running "sudo port -cn upgrade percona-toolkit", or 
defining an alias like "alias sp="sudo port -cn" and using that.

I hope this helps,
Aljaž

On 04/lug/2013, at 14:32, Enrico Placci  wrote:

> Hello everybody,
> I hope my email does not sound too whiney, my intention is to give 
> constructive feedback, hopefully my frustration won't overshadow that.
> I'm writing you from a burning laptop, where macports decided to be too smart 
> and did what it thought I wanted.
> A few years ago I absolutely loved how macports did exactly what I told it to 
> do:
> # port install myport 
> myport is already installed
> # port upgrade myport
> upgrading myport
> 
> I absolutely loved it! Sometimes you just need something quickly and you 
> don't care what version it is. Maybe you just forgot you previously installed 
> it.
> 
> Also it didn't upgrade all dependencies unless you asked it to. 
> Again, sometimes you want to get some tool compiled quickly and you don't 
> care if a new minor version of gtk is out, the previous one will work just 
> fine.
> 
> So what I started doing is I don't update port definitions for months so that 
> I don't have to upgrade half my libraries every time I install a tool, which 
> is quite annoying as I'd like to compile a recent version of the new thing 
> I'm installing, and I'd like to upgrade only the dependencies that need 
> upgrading.
> 
> So today I wanted to upgrade percona-toolkit. I did a "port selfupdate" and a 
> "port upgrade percona-toolkit" . 
> These are the requirements of percona-toolkit:
> 
> ---
> Most tools require:
> 
>   * Perl v5.8 or newer
>   * Bash v3 or newer
>   * Core Perl modules like Time::HiRes
> 
> Tools that connect to MySQL require:
> 
>   * Perl modules DBI and DBD::mysql
>   * MySQL 5.0 or newer



--
Aljaž Srebrnič a.k.a g5pw
My public key:  http://bit.ly/g5pw_pubkey


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

Re: R Fails to Build

[Aljaž Srebrnič]

Interesting!
I build R just fine on a macbook with 10.8.3.
However, R-app needs to be fixed, and I have a patch, I just need the OK by the 
maintainer.

On 27/apr/2013, at 23:15, Michael Davis  wrote:

> My attempt failed at the same place (when accessing devQuartz.c in the build).
> 
> Michael
> 
> From: Rodolfo Aramayo 
> Date: Saturday, April 27, 2013 2:51 PM
> To: Chris Jones 
> Cc: Rodolfo Aramayo , MacPorts Users 
> 
> Subject: Re: R Fails to Build
> 
> Apologies,
> 
> My first email (with entire log attached) was put on hold
> Here I am attaching the last 500 lines of the log file
> Thanks
> 
> --R
> 
> 
> On Sat, Apr 27, 2013 at 3:23 PM, Chris Jones  wrote:
>> 
>> On 27 Apr 2013, at 08:49 PM, Rodolfo Aramayo  wrote:
>> 
>> > Hi,
>> >
>> > I am having trouble upgrading R and I am having trouble determining if a 
>> > ticket has already been reported
>> > Is anyone having the same problem?
>> 
>> Might help if you bothered to post the exact error you are getting ...
>> 
>> > Should I file a ticket?
>> >
>> > Thanks
>> >
>> > --R
>> > ___
>> > macports-users mailing list
>> > macports-users@lists.macosforge.org
>> > https://lists.macosforge.org/mailman/listinfo/macports-users
> 
> ___ macports-users mailing list 
> macports-users@lists.macosforge.org 
> https://lists.macosforge.org/mailman/listinfo/macports-users
> ___
> macports-users mailing list
> macports-users@lists.macosforge.org
> https://lists.macosforge.org/mailman/listinfo/macports-users



--
Aljaž Srebrnič a.k.a g5pw
My public key:  http://bit.ly/g5pw_pubkey

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

Re: port info problem

[Aljaž Srebrnič]

Hello!
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. So, 
the way to solve this is:

- Enable cairo only if +x11 is requested
- Remove cairo from default_variants

either of the options are to be implemented by the maintainer. You should open 
a ticket at http://trac.macports.org and Cc the maintainer.

In the meantime, you can check out the port information by entering:

$ port info R-framework -cairo


On 09/apr/2013, at 12:08, Federico Calboli  wrote:

> Dear All,
> 
> I was checking (out of academic curiosity) the port for R.
> 
> :~$ port info R
> R @2.15.3 (math, science)
> Variants: aqua, debug, gcc43, gcc44, gcc45, gcc46, [+]gcc47, 
> [+]recommended
> 
> Description:  R is a language and environment for statistical 
> computing and graphics. R provides a wide variety of statistical (linear
>  and nonlinear modeling, classical statistical tests, 
> time-series analysis, classification, clustering, ...) and graphical
>  techniques, and is highly extensible.
> Homepage: http://www.r-project.org/
> 
> Build Dependencies:   pkgconfig
> Library Dependencies: gettext, icu, glib2, jpeg, libiconv, cairo, pango, 
> readline, tcl, tk, tiff, xorg-libXmu, xorg-libXScrnSaver, gcc47
> Conflicts with:   R-framework
> Platforms:darwin
> License:  GPL-2 GPL-3
> Maintainers:  kjell.ko...@me.com
> 
> I was curious to know more about R-framework, due to the conflict with R, so 
> I tried
> 
> :~$ port info R-framework
> Error: Inconsistent variant specification: R-framework variant +x11 is 
> required by at least one of +cairo +accelerate +gcc47 +recommended, but 
> specified -x11
> Error: Unable to open port: Error evaluating variants
> 
> WTF?  I might not be interested installing a port (in fact I do not install R 
> through macports in the first place), but why can't I get info about it if I 
> want?  The fact I do not want macports to install x11 has nothing to do with 
> my ability to read info about a port.
> 
> Bizarre.
> 
> BW
> 
> F
> 
> ___
> macports-users mailing list
> macports-users@lists.macosforge.org
> https://lists.macosforge.org/mailman/listinfo/macports-users



--
Aljaž Srebrnič a.k.a g5pw
My public key:  http://bit.ly/g5pw_pubkey

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

Re: Notes...that flash by and are gone...(was Re: any good audio/video editing apps in macports?)

[Aljaž Srebrnič]

; after the port(1) job finishes, and the user, uh, I don't know,
>> reads them?
> 
> You mean something like others and I were discussing both on-list
> and off-list earlier this morning, and also mentioned above?
> Yeah, in a text-only version, that would be, in my opinion for
> what it apparently is not worth crap here, would be the best
> way to do that.
> 
>> Whether you have ever heard about the Keep It Simple, Stupid
>> principle before or not, you are trying to fsck it in the ear.
> 
> You consider 75 lines of code for both the client and the server
> (including all blank lines and comments---basically just
> "wc -l *" output) NOT simple?  Wow.  That's pretty severe.
> 
> Not only that, but the idea was to also keep the IMPLEMENTATION
> simple, too.  I think my idea would have done that quite well.
> 
> Ok, so it's a bad idea.  I did say, in my first mention of this, that if
> nobody wanted to use it, "oh well."  It doesn't bother me a bit if nobody
> liks this or any of my ideas...my rather insignificant ego doesn't give a
> shit, and even then, I tell it to go fsck itself if it speaks up at all.
> So I'll just scrap the idea and go back to what I was doing before.
> Besides, I'd hate to have to make those [sarcasm mode on afterburners]
> very complicated [sarcasm off] one or two line changes to adapt to the
> non-GUI version instead of the GUI one.  Yeah, that might take a whole
> minute or two of my time….

It's not really a bad idea, but it belongs in a GUI like pallet IMHO. There are 
other solutions for the command line, not everyone likes things popping up from 
the console (and, well, it is a little counter-intuitive for the CLI to pop up 
additional windows when the main "text" is in the console itself).

> 
> Later,
>   --jim


73 de IV3BSI, hoping to catch you in HF.
--
Aljaž Srebrnič a.k.a g5pw
My public key:  http://bit.ly/g5pw_pubkey


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

Re: Update ocatve to the latest version

[Aljaž Srebrnič]

On 31/ago/2012, at 23:54, Peng Yu  wrote:

> Hi Michael,
> 
> Thanks. I get the following warning. Is there a compile option should
> be enabled for octave?
> 
> ~$ /opt/local/bin/octave -q
> warning: no graphical display found

Looks like there's a problem with X11, are you on mountain lion? DO you have 
XQuartz installed?

> octave:1>
> 
> ~$ octave --version
> GNU Octave, version 3.6.2
> Copyright (C) 2012 John W. Eaton and others.
> This is free software; see the source code for copying conditions.
> There is ABSOLUTELY NO WARRANTY; not even for MERCHANTABILITY or
> FITNESS FOR A PARTICULAR PURPOSE.
> 
> Octave was configured for "x86_64-apple-darwin10.8.0".
> 
> Additional information about Octave is available at http://www.octave.org.
> 
> Please contribute if you find this software useful.
> For more information, visit http://www.octave.org/help-wanted.html
> 
> Read http://www.octave.org/bugs.html to learn how to submit bug reports.
> ~$ which octave
> /opt/local/bin/octave
> 
> 
> 
> On Tue, Aug 28, 2012 at 12:38 PM, Michael Dickens
>  wrote:
>> I've updated octave-devel in r97159.  For those using octave and wanting
>> the latest, please do a seflupdate and then see if the new octave-devel
>> works for you.  The octave-* ports may or not work with the Octave
>> 3.6.2, but they should still be compatible with the octave (3.2) port.
>> Someone (not me) will be working towards upgrading the octave-* ports to
>> be compatible with 3.6, and once those are well enough along then we'll
>> move octave-devel to octave.  For now, continue to use octave-devel. -
>> MLD
>> ___
>> macports-users mailing list
>> macports-users@lists.macosforge.org
>> http://lists.macosforge.org/mailman/listinfo/macports-users



Aljaž Srebrnič
-- --
My public key:  http://bit.ly/g5pw_pubkey


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

Re: Update ocatve to the latest version

[Aljaž Srebrnič]

On 25/ago/2012, at 02:07, Jerry  wrote:

> 
> On Aug 24, 2012, at 3:57 PM, Ryan Schmidt wrote:
> 
>> 
>> On Aug 24, 2012, at 11:09, Peng Yu  wrote:
>> 
>>> The current octave version is fairly old, considering that the current
>>> release is of version 3.6.2. Is there a reason that prevents the
>>> update to a more recent version of octave? Thanks!
>> 
>> Try the octave-devel port. See also https://trac.macports.org/ticket/32894
>> 
> octave-devel is 3.4.3. Version 3.6.2 has been out for several months.

Me and the maintainer are working on it. There is a portfile from kitchen.andy 
that works, we are just polishing some errors, we'll be soon done.

> 
> Jerry
>> 
>> ___
>> macports-users mailing list
>> macports-users@lists.macosforge.org
>> http://lists.macosforge.org/mailman/listinfo/macports-users
> 
> ___
> macports-users mailing list
> macports-users@lists.macosforge.org
> http://lists.macosforge.org/mailman/listinfo/macports-users



Aljaž Srebrnič
-- --
My public key:  http://bit.ly/g5pw_pubkey

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

Re: Xcode 4.3: Apparently Persistent License Agreement

[Aljaž Srebrnič]

On 18/feb/2012, at 13:42, Kevin Reid wrote:

> On Feb 17, 2012, at 22:54, Anthony Michael Agelastos wrote:
> 
>> When I peruse the main.log file it creates, I notice the following at the 
>> bottom.
>> 
>> 
>> :info:build You have not agreed to the Xcode license agreements, please run 
>> xcodebuild standalone from within a Terminal window to review and agree to 
>> the Xcode license agreements.
>> 
>> 
>> This looks like I need to agree to the license agreement. The only issue, 
>> though, is that I already have. I launch Xcode 4.3 (through Finder and `open 
>> /Applications/Xcode.app`) and it doesn't prompt me with anything. I even 
>> created a "Hello World!" console application and successfully built it with 
>> Xcode 4.3. Does anyone have any ideas with regards to this? I have also 
>> attached the main.log.
> 
> I haven't used Xcode 4.3, but I would suggest following its instructions: run 
> the xcodebuild command in order to acknowledge the license agreement -- _as 
> the macports user_ since that's what is used for builds, IIRC. (I'm assuming 
> that the "read license" flag is stored per-user.)

unfortunately this doesn't work, probably because the license agreement is 
stored in the home directory of the user (which is /var/empty for macports user)

> 
> -- 
> Kevin Reid  
> 
> ___
> macports-users mailing list
> macports-users@lists.macosforge.org
> http://lists.macosforge.org/mailman/listinfo.cgi/macports-users

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

Re: Noobish question

[Aljaž Srebrnič]

On 01/feb/2012, at 23:38, Ryan Schmidt wrote:

> 
> On Feb 1, 2012, at 10:58, Aljaž Srebrnič wrote:
> 
>> No, no PortGroup is used, but compiler.cpath solves the issue!
>> It is strangely undocumented, though… :/
> 
> Yup. It was never clear to me why we added CPATH and LIBRARY_PATH to MacPorts 
> base, since the existing CPPFLAGS and LDFLAGS we set in the configure phase 
> should have the same effect for properly-behaved ports, and 
> improperly-behaved ports should be fixed. Now that Xcode 4.2 users are using 
> clang, and clang does not use CPATH or LIBRARY_PATH [1], it may truly be time 
> to admit that CPATH and LIBRARY_PATH are not helping us (they are merely 
> causing those of us who don't use clang to commit ports that may not work for 
> users using clang), and remove them.
> 
> Then again, this may be fixed in future versions of clang. CPATH support was 
> already added [2]; adding LIBRARY_PATH support [3] has not been discussed yet 
> however.
> 
> Out of curiosity, why are you needing to remove CPATH? What problem is having 
> it set causing you?

I was doing some testing on msp430-* ports and when i had libunwind-headers 
installed (which provided /opt/local/include/unwind.h) the build phase for 
msp430-gcc* failed because it was including the unwind.h in 
/opt/local/include/unwind.h and not the one in the build directory…
Note: the install failed in the libgcc build phase (when clang is _not_ used)

> 
> [1] http://lists.macosforge.org/pipermail/macports-dev/2011-August/015543.html
> [2] http://llvm.org/bugs/show_bug.cgi?id=8971
> [3] http://llvm.org/bugs/show_bug.cgi?id=10296
> 

Aljaž Srebrnič
-- --
My public key:  http://bit.ly/g5pw_pubkey
___
macports-users mailing list
macports-users@lists.macosforge.org
http://lists.macosforge.org/mailman/listinfo.cgi/macports-users

Re: Can't seem to get PHP function exif_read_data to work

[Aljaž Srebrnič]

Well, you could do a $port contents php5-exif and see where all the
files are installed, and check if that directory is in you PHP
include_path! :)

g...@gulik.org Gmail wrote:
>
> I'm having a weird problem where I can't get the PHP exif module to
> work.  It IS installed but I get the error " *Fatal error*: Call to
> undefined function exif_read_data() in.." in my script.
>
>
> # port list installed | grep php
> php5   @5.3.8  lang/php5
> php5-exif  @5.3.8  php/php5-exif
> php5-geoip @1.0.7  php/php5-geoip
> php5-iconv @5.3.8  php/php5-iconv
> php5-intl  @5.3.8  php/php5-intl
> php5-intl  @5.3.8  php/php5-intl
> php5-mbstring  @5.3.8  php/php5-mbstring
> php5-mcrypt@5.3.8  php/php5-mcrypt
> php5-mysql @5.3.8  php/php5-mysql
> php5-openssl   @5.3.8  php/php5-openssl
> php5-sqlite@5.3.8  php/php5-sqlite
>
>
> I'm pretty new to macports so I've run out of ideas why it's not working.
> I did check the output of the phpinfo() function and no references to
> EXIF show up there.
>
> -- 
> Greg Gulik http://www.gulik.com/greg/
> greg @ gulik.com
>
> ___
> macports-users mailing list
> macports-users@lists.macosforge.org
> http://lists.macosforge.org/mailman/listinfo.cgi/macports-users

-- 
Aljaž Srebrnič
-- --
My public key <http://bit.ly/g5pw_pubkey>
About me <http://about.me/g5pw>

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

Root install problem

[Aljaž Srebrnič]

Hi all! when installing ROOT, I get this:

$ sudo port -vv install root 
+builtin_ftgl+gcc45+mysql+opengl+python26+qt_mac+roofit+ssl+xml
--->  Computing dependencies for root.
--->  Staging root into destroot
. missing (directory not created: File exists)
./Applications missing (directory not created: File exists)
./Developer missing (directory not created: File exists)
./Library missing (directory not created: File exists)
make: Entering directory 
`/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_science_root/root/work/root'
Installing binaries in 
/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_science_root/root/work/destroot/opt/local/bin
Installing libraries in 
/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_science_root/root/work/destroot/opt/local/lib/root
Installing headers in 
/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_science_root/root/work/destroot/opt/local/include/root
Installing 
/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_science_root/root/work/root/main/src/rmain.cxx
 in 
/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_science_root/root/work/destroot/opt/local/include/root
Installing cint/cint/include cint/cint/lib and cint/cint/stl in 
/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_science_root/root/work/destroot/opt/local/lib/root/cint
Installing icons in 
/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_science_root/root/work/destroot/opt/local/share/root/icons
Installing fonts in 
/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_science_root/root/work/destroot/opt/local/share/root/fonts
Installing misc docs in 
/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_science_root/root/work/destroot/opt/local/share/doc/root
Installing tutorials in 
/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_science_root/root/work/destroot/opt/local/share/root/tutorials
Installing tests in 
/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_science_root/root/work/destroot/opt/local/share/root/test
Installing macros in 
/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_science_root/root/work/destroot/opt/local/share/root/macros
Installing man(1) pages in 
/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_science_root/root/work/destroot/opt/local/share/man/man1
Installing config files in 
/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_science_root/root/work/destroot/opt/local/etc/root
Installing Autoconf macro in 
/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_science_root/root/work/destroot/opt/local/share/aclocal
Installing Emacs Lisp library in 
/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_science_root/root/work/destroot/opt/local/share/emacs/site-lisp
Installing GDML conversion scripts in 
/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_science_root/root/work/destroot/opt/local/lib/root
make: Leaving directory 
`/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_science_root/root/work/root'
Error: Target org.macports.destroot returned: error renaming 
"/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_science_root/root/work/destroot/opt/local/lib/root/ROOT.py":
 no such file or directory
Warning: the following items did not execute (for root): org.macports.activate 
org.macports.destroot org.macports.install
Log for root is at: 
/opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_release_ports_science_root/root/main.log
Error: Status 1 encountered during processing.
To report a bug, see <http://guide.macports.org/#project.tickets>

Any idea why ROOT.py is missing?

Aljaž Srebrnič
-- --
My public key: http://bit.ly/81qoyC

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