On Fri, Jun 15, 2012 at 10:53 PM, Murray Eisenberg <
murrayeisenb...@gmail.com> wrote:
> But what does the texlive variant do? Why would one want or not want that
> variant? So far as I could see, the docs for lcdf-typetools don't describe
> that.
>
But the variant's associated code does: it rem
Disabling variants is done by using the minus sign prefix.
Sudo port whatever -texlive disables the variant.
Murray Eisenberg wrote:
>On 6/15/12 6:53 PM, Jeremy Lavergne wrote:
>>> I don't understand how that would work: I thought lcdf-typetools
>depends on the libraries and/or binaries of eith
On 6/15/12 6:53 PM, Jeremy Lavergne wrote:
I don't understand how that would work: I thought lcdf-typetools depends on the
libraries and/or binaries of either texlive or the Japanese version ptex of TeX.
The texlive variant adds the texlive-bin dependency exclusively for kpathsea.
If you don'
> I don't understand how that would work: I thought lcdf-typetools depends on
> the libraries and/or binaries of either texlive or the Japanese version ptex
> of TeX.
The texlive variant adds the texlive-bin dependency exclusively for kpathsea.
If you don't use the variant, there is no dependen
On 6/15/12 6:42 PM, Jeremy Lavergne wrote:
(1) Exactly what do I need to change in the lcdf-typetools portfile to delete
the dependency? The relevant portion is:
default_variants +texlive
install it with that variant disabled:
sudo port install lcdf-typetools -texlive
I don't understand
> (1) Exactly what do I need to change in the lcdf-typetools portfile to delete
> the dependency? The relevant portion is:
>
> default_variants +texlive
install it with that variant disabled:
sudo port install lcdf-typetools -texlive
smime.p7s
Description: S/MIME cryptographic signature
___
I want to install the port of lcdf-typetools. It depends on
texlive-bin. And texlive-bin in turn depends on texlive-common.
I do _not_ want to use macports to install any components of texlive
whatsoever, as I already have a complete, working installation of
texlive on my OS X Mac via the MacT
On Jun 15, 2012, at 10:13, Pascal Dupuis wrote:
> variant hpc description {build mpif77 and mpif90 using
> -ftree-vectorize} conflicts gcc42
> gcc43 gcc44 gcc45 g95 {
>configure.args-delete --disable-mpi-f77 --disable-mpi-f90
>configure.cflags-delete -m32
>configure.cflags-
On Jun 15, 2012, at 5:51 a.m., Fabrizio Salvatore wrote:
> Do I do it from within Xcode or do I have to run something on the command
> line?
Not sure if there's a way to do it from the command line. I opened up Xcode,
which then asked if I wanted to update the Command-Line Tools. If it doesn't
> Um, I thought I'd done that (and more) when I did "sudo port uninstall
> installed".
Yes, and you did "clean all":
> Some time ago, I followed the migration instructions on another machine and
> did "sudo port clean all". Is that a good option? I remember being
> surprised at how long it t
At 1:37 PM -0400 6/15/12, Jeremy Lavergne wrote:
> I then cleaned perl5.12 and tried "sudo port install perl5.12
+universal". It trundled away installing several universal versions
of dependencies but while 'finishing' it found 4 broken ports and
reinstalled them. Then it found 2 broken port
> I then cleaned perl5.12 and tried "sudo port install perl5.12 +universal".
> It trundled away installing several universal versions of dependencies but
> while 'finishing' it found 4 broken ports and reinstalled them. Then it
> found 2 broken ports (different this time) and reinstalled them.
Bwah haha. I see that you did at the next command. Weee
smime.p7s
Description: S/MIME cryptographic signature
___
macports-users mailing list
macports-users@lists.macosforge.org
http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
Perl needs cleaned:
> Error: Requested variants "" do not match original selection "+universal".
> Please use the same variants again, perform 'port clean perl5.12' or specify
> the force option (-f).
smime.p7s
Description: S/MIME cryptographic signature
___
At 1:01 PM -0400 6/15/12, Craig Treleaven wrote:
The attached log
...is now attached. Sigh.
MacPorts install fail 2012Jun15.txt
Description: Binary data
___
macports-users mailing list
macports-users@lists.macosforge.org
http://lists.macosforge.or
Hi:
I seem to be unable to upgrade or install Qt4-mac on an older Core2
Duo mini. At first, I tried to just use port upgrade (after a
selfupdate). It fell over but I didn't save any logs. This machine
has had MacPorts on it for a long time--4 years plus or minus--but
only for a couple of s
Hello,
I'm an Octave contributor in some specific fields like localisation.
I recently changed of job and now I have at my disposal an Intel Mac
running OSX 10.5. I would like to build a high-performance version of
Octave, this implies to built it with either gcc46 either gcc47, using
64 bits mode
On Thu, Jun 14, 2012 at 08:42:33PM -0400, Richard L. Hamilton wrote:
> Might want to do an update of the command line tools that come with
> Xcode once it's installed, though. At least, I did, and it didn't seem
> to hurt anything.
For the average user, like me, who is just using the tools from
Do I do it from within Xcode or do I have to run something on the command
line?
THanks!
Fab
On 15 June 2012 01:42, Richard L. Hamilton wrote:
>
> On Jun 14, 2012, at 12:43 PM, Andrea D'Amore wrote:
>
> > On Thu, Jun 14, 2012 at 4:25 PM, Fabrizio Salvatore
> > wrote:
> >
> >> once I have updat
19 matches
Mail list logo
