Re: Error installing MacPorts to alternate prefix
On 2014-4-3 05:14 , Craig Treleaven wrote:
> At 7:24 PM +0200 4/2/14, Clemens Lang wrote:
>> ...
>>> Possibly being reckless, I went ahead with the make install...which
>>> wandered off into the weeds, muttering:
>>>
>>> >/opt/local/bin/tclsh src/images_to_archives.tcl
>>> >"/opt/dvr/share/macports/Tcl"
>>> >can't find package msgcat
>>> > while executing
>>> >"package require msgcat"
>>> > (file "/opt/dvr/share/macports/Tcl/registry2.0/registry.tcl"
>>> line 40)
>>> > invoked from within
>>> >"source /opt/dvr/share/macports/Tcl/registry2.0/registry.tcl"
>>> > ("package ifneeded registry 1.0" script)
>>> > invoked from within
>>> >"package require registry 1.0"
>>> > (file "src/images_to_archives.tcl" line 10)
>>> >make: *** [install] Error 1
>>
>> That suggests you are building against Tcl 8.6, possibly because you
>> have the
>> Tcl port installed and didn't remove $prefix from your $PATH while
>> configuring MacPorts. MacPorts currently doesn't support Tcl 8.6.
>
> Yes, thanks, that would be it. Perhaps the install instructions [1]
> might mention this?
>
> Craig
>
> [1] http://guide.macports.org/#installing.macports
> OR http://www.macports.org/install.php
You can't build against anything but the bundled copy of Tcl as of the
next release.
- Josh
___
macports-dev mailing list
macports-dev@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-dev
Re: git.macports.org not syncing since 11 March
Clemens You are right there doesn’t seem to be anything wrong with the access from the internet, and I have checked that the internal access to git.macports.org is also okay. I even restarted the cron daemon but it still shows the latest update on git.macports of March 11. I’ll looking but running out of ideas. Shree On Apr 2, 2014, at 9:25 AM, Clemens Lang wrote: > Hi Shree > >> That is odd, we have one Firewall Rule from the Internet to git.macports.org >> for git and it was tested successfully. > > I don't think Internet -> git.macports.org is the problem, but rather > (1) there's something wrong with the post-commit hook or cronjob updating the > Git mirror > (2) there's a network problem from that server to git.macports.org. > > > -- > Clemens Lang ___ macports-dev mailing list macports-dev@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-dev
Re: Error installing MacPorts to alternate prefix
At 7:24 PM +0200 4/2/14, Clemens Lang wrote:
...
Possibly being reckless, I went ahead with the make install...which
wandered off into the weeds, muttering:
>/opt/local/bin/tclsh src/images_to_archives.tcl
>"/opt/dvr/share/macports/Tcl"
>can't find package msgcat
> while executing
>"package require msgcat"
> (file "/opt/dvr/share/macports/Tcl/registry2.0/registry.tcl" line 40)
> invoked from within
>"source /opt/dvr/share/macports/Tcl/registry2.0/registry.tcl"
> ("package ifneeded registry 1.0" script)
> invoked from within
>"package require registry 1.0"
> (file "src/images_to_archives.tcl" line 10)
>make: *** [install] Error 1
That suggests you are building against Tcl 8.6, possibly because you have the
Tcl port installed and didn't remove $prefix from your $PATH while
configuring MacPorts. MacPorts currently doesn't support Tcl 8.6.
Yes, thanks, that would be it. Perhaps the install instructions [1]
might mention this?
Craig
[1] http://guide.macports.org/#installing.macports
OR http://www.macports.org/install.php
___
macports-dev mailing list
macports-dev@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-dev
Re: Error installing MacPorts to alternate prefix
Hi,
> I've run into an error trying to install MacPorts 2.2.1. Configure
> and make indicated no errors. Make test complained:
>
> >===> making test in src/port1.0
> >/opt/local/bin/tclsh tests/portutil.tcl /opt/dvr/share/macports/Tcl
> >couldn't read file
> >"/opt/dvr/share/macports/Tcl/macports1.0/macports_fastload.tcl": no
> >such file or directory
> > while executing
> >"source [file join [lindex $argv 0] macports1.0 macports_fastload.tcl]"
> > (file "tests/portutil.tcl" line 5)
> >make[2]: *** [test] Error 1
> >make[1]: *** [test] Error 1
> >make: *** [test] Error 1
That's normal and expected to fail if you haven't run make install yet.
The testsuite needs an installed version of MacPorts.
> Possibly being reckless, I went ahead with the make install...which
> wandered off into the weeds, muttering:
>
> >/opt/local/bin/tclsh src/images_to_archives.tcl
> >"/opt/dvr/share/macports/Tcl"
> >can't find package msgcat
> > while executing
> >"package require msgcat"
> > (file "/opt/dvr/share/macports/Tcl/registry2.0/registry.tcl" line 40)
> > invoked from within
> >"source /opt/dvr/share/macports/Tcl/registry2.0/registry.tcl"
> > ("package ifneeded registry 1.0" script)
> > invoked from within
> >"package require registry 1.0"
> > (file "src/images_to_archives.tcl" line 10)
> >make: *** [install] Error 1
That suggests you are building against Tcl 8.6, possibly because you have the
Tcl port installed and didn't remove $prefix from your $PATH while
configuring MacPorts. MacPorts currently doesn't support Tcl 8.6.
--
Clemens Lang
___
macports-dev mailing list
macports-dev@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-dev
Re: git.macports.org not syncing since 11 March
Hi Shree > That is odd, we have one Firewall Rule from the Internet to git.macports.org > for git and it was tested successfully. I don't think Internet -> git.macports.org is the problem, but rather (1) there's something wrong with the post-commit hook or cronjob updating the Git mirror (2) there's a network problem from that server to git.macports.org. -- Clemens Lang ___ macports-dev mailing list macports-dev@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-dev
Re: git.macports.org not syncing since 11 March
$ telnet git.macports.org 9418 Trying 17.251.224.219... Connected to git.macports.org. Escape character is '^]'. ^CConnection closed by foreign host. At 8:54 AM -0700 4/2/14, Shreeraj Karulkar wrote: That is odd, we have one Firewall Rule from the Internet to git.macports.org for git and it was tested successfully. Can anyone run the following command and send me the output. Needs to be done without VPN to any of our internal networks. $ telnet git.macports.org 9418 Shree On Apr 2, 2014, at 8:48 AM, William Siegrist wrote: Shree? -Bill On Apr 2, 2014, at 7:41 AM, David Röthlisberger wrote: FYI the git mirror at git.macports.org isn't syncing with the svn repository since 11 March. There's a 9-day-old ticket with no activity at https://trac.macports.org/ticket/43058 The last commit is: http://svn.macports.org/repository/macports/trunk@117767 Cheers, Dave. ___ macports-dev mailing list macports-dev@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-dev ___ macports-dev mailing list macports-dev@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-dev -- -- Craig Treleaven, CA -- Clearview Consulting (905) 829-2054 ctrelea...@cogeco.ca ___ macports-dev mailing list macports-dev@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-dev
Re: git.macports.org not syncing since 11 March
That is odd, we have one Firewall Rule from the Internet to git.macports.org for git and it was tested successfully. Can anyone run the following command and send me the output. Needs to be done without VPN to any of our internal networks. $ telnet git.macports.org 9418 Shree On Apr 2, 2014, at 8:48 AM, William Siegrist wrote: > Shree? > > -Bill > > > On Apr 2, 2014, at 7:41 AM, David Röthlisberger wrote: > >> FYI the git mirror at git.macports.org isn't syncing with the svn >> repository since 11 March. There's a 9-day-old ticket with no activity >> at https://trac.macports.org/ticket/43058 >> >> The last commit is: >> http://svn.macports.org/repository/macports/trunk@117767 >> >> Cheers, >> Dave. >> >> ___ >> macports-dev mailing list >> macports-dev@lists.macosforge.org >> https://lists.macosforge.org/mailman/listinfo/macports-dev > ___ macports-dev mailing list macports-dev@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-dev
Re: git.macports.org not syncing since 11 March
Shree? -Bill On Apr 2, 2014, at 7:41 AM, David Röthlisberger wrote: > FYI the git mirror at git.macports.org isn't syncing with the svn > repository since 11 March. There's a 9-day-old ticket with no activity > at https://trac.macports.org/ticket/43058 > > The last commit is: > http://svn.macports.org/repository/macports/trunk@117767 > > Cheers, > Dave. > > ___ > macports-dev mailing list > macports-dev@lists.macosforge.org > https://lists.macosforge.org/mailman/listinfo/macports-dev ___ macports-dev mailing list macports-dev@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-dev
git.macports.org not syncing since 11 March
FYI the git mirror at git.macports.org isn't syncing with the svn repository since 11 March. There's a 9-day-old ticket with no activity at https://trac.macports.org/ticket/43058 The last commit is: http://svn.macports.org/repository/macports/trunk@117767 Cheers, Dave. ___ macports-dev mailing list macports-dev@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-dev
Re: [MacPorts] #43156: maven-devel installation completely broken
On 4/2/14, 2:50, MacPorts wrote: […] > maven seems to be using both strategies 1(b) and 2, and it should decide > which of these strategies it wants to follow. I think it wants to follow > the 2nd strategy, since the maven port is replaced by the maven1 port. So > shouldn't maven3 be updated to a newer version (#42737) and maven-devel > replaced by maven3? See also #42114. Yes, this is the way forward in general. The subtlety was that maven-3.1.x changed the API points it exports to be used by other tools in a way that is incompatible with maven-3.0.x, so previous consumers of the maven3 port were broken if I we had updated maven3 to point to maven-3.1.x. Enough time has passed, that most of these consumers of maven3 (or at least the ones that I use), now work with both the maven-3.0.x and maven-3.1.x API. Two ways forward: 1) maven3 goes to maven-3.1.x. MacPorts no longer offers a maven-3.0.x installation 2) A new port 'maven31' gets introduced for maven-3.1.x; We rename 'maven3' as 'maven30' which offers maven-3.0.x. Possibly we use 'maven3' as synonym for 'maven31'. In any event, maven-devel should be retired. -- "A screaming comes across the sky. It has happened before, but there is nothing to compare to it now." ___ macports-dev mailing list macports-dev@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-dev
