ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Otared Kavian <otared@gmail.com>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: Instalation ConTeXt to MAC - newbie problem
Date: Sun, 17 Jan 2016 14:38:18 +0100	[thread overview]
Message-ID: <23516000-490D-45D8-BEAD-1B392CD9702E@gmail.com> (raw)
In-Reply-To: <569B9246.30806@gyza.cz>

[-- Attachment #1: Type: text/plain, Size: 896 bytes --]

Hello Jaroslav,

Here is what I do on my Mac:

1) While in the Finder, create a folder named Context-standalone

2) Put the attached file « first-setup.sh »  in the folder Context-standalone

3) Open Terminal and issue the command

	cd [Path-to-the-folder-Context-standalone]

4) Then in Terminal issue the command

	ls first-setup.sh

you should see something beginning with:

	-rwxr-xr-x  

that is the file has an « x » in its or your rights, that is it is executable.

If this not the case, using the command below make sure it has that right:

	chmod +x first-setup.sh

5) Once this is done, issue the command

	sh first-setup.sh

6) In principle you should end up with all files necessary for Context working in the folder Context-standalone

7) If this is not the case, please report at which step things do not work as expected.

Best regards: OK


[-- Attachment #2: first-setup.sh --]
[-- Type: application/octet-stream, Size: 3525 bytes --]

#!/bin/sh

# Takes the same arguments as mtx-update

# you may change this if you want ...
CONTEXTROOT="$PWD/tex"

# suggested by Tobias Florek to check for rsync
if [ ! -x "`which rsync`" ]; then
	echo "You need to install rsync first."
	exit 1
fi

system=`uname -s`
cpu=`uname -m`

case "$system" in
	# linux
	Linux)
		case "$cpu" in
			i*86) platform="linux" ;;
			x86_64|ia64) platform="linux-64" ;;
			# a little bit of cheating with ppc64 (won't work on Gentoo)
			ppc|ppc64) platform="linux-ppc" ;;
			# we currently support just mipsel, but Debian is lying (reports mips64)
			# we need more hacks to fix the situation, this is just a temporary solution
			mips|mips64|mipsel|mips64el) platform="linux-mipsel" ;;
			# TODO: probably both wrong and incomplete
			armv7l) platform="linux-armhf" ;;
			*) platform="unknown" ;;
		esac ;;
	# Mac OS X
	Darwin)
		case "$cpu" in
			i*86) platform="osx-intel" ;;
			x86_64) platform="osx-64" ;;
			ppc*|powerpc|power*|Power*) platform="osx-ppc" ;;
			*) platform="unknown" ;;
		esac ;;
	# FreeBSD
	FreeBSD|freebsd)
		case "$cpu" in
			i*86) platform="freebsd" ;;
			x86_64) platform="freebsd" ;; # no special binaries are available yet
			amd64) platform="freebsd-amd64" ;;
			*) platform="unknown" ;;
		esac ;;
	# kFreeBSD (debian)
	GNU/kFreeBSD)
		case "$cpu" in
			#i*86) platform="kfreebsd-i386" ;;
			#x86_64|amd64) platform="kfreebsd-amd64" ;;
			*) platform="unknown" ;;
		esac ;;
	# cygwin
	CYGWIN*)
		case "$cpu" in
			i*86) platform="cygwin" ;;
			x86_64|ia64) platform="cygwin" ;;
			*) platform="unknown" ;;
		esac ;;
	# UWIN
	UWIN*)
		case "$cpu" in
			i*86) platform="mswin" ;;
			*) platform="unknown" ;;
		esac ;;
	# SunOS/Solaris
	SunOS)
		case "$cpu" in
			sparc) platform="solaris-sparc" ;;
			i86pc) platform="solaris-intel" ;;
			*) platform="unknown" ;;
		esac ;;
	*) platform="unknown"
esac

# temporary patch for 64-bit Leopard with 32-bit kernel
if test "$platform" = "osx-intel"; then
	# if running Snow Leopard or later
	# better: /usr/bin/sw_vers -productVersion
	if test `uname -r|cut -f1 -d"."` -ge 10 ; then
		# if working on 64-bit hardware
		if test `sysctl -n hw.cpu64bit_capable` = 1; then
			# snowleopard32=TRUE
			platform="osx-64"
		fi
	fi
fi

if test "$platform" = "unknown" ; then
	echo "Error: your system \"$system $cpu\" is not supported yet."
	echo "Please report to the ConTeXt mailing-list (ntg-context@ntg.nl)"
	exit
fi

# if you want to enforce some specific platform
# (when 'uname' doesn't agree with true architecture), uncomment and modify next line:
# platform=linux

# download or rsync the latest scripts first
rsync -rlptv rsync://contextgarden.net/minimals/setup/$platform/bin .

# use native windows binaries on cygwin
if test "$platform" = "cygwin" ; then
	platform=mswin
fi

# download or update the distribution
# you may remove the --context=beta switch if you want to use "current"
# you can use --engine=luatex if you want just mkiv
env PATH="$PWD/bin:$CONTEXTROOT/texmf-$platform/bin:$PATH" \
./bin/mtxrun --script ./bin/mtx-update.lua --force --update --make --context=beta --platform=$platform --texroot="$CONTEXTROOT" $@

echo
echo "When you want to use context, you need to initialize the tree by typing:"
echo
echo "  . $CONTEXTROOT/setuptex"
echo
echo "in your shell or add"
echo "  \"$CONTEXTROOT/texmf-$platform/bin\""
echo "to PATH variable if you want to set it permanently."
echo "This can usually be done in .bashrc, .bash_profile"
echo "(or whatever file is used to initialize your shell)."
echo

[-- Attachment #3: Type: text/plain, Size: 3622 bytes --]





> On 17 Jan 2016, at 14:08, Jaroslav Hajtmar <hajtmar@gyza.cz> wrote:
> 
> Hello Matthias.
> Thank you for the quick response. During installation, no error occurs, even seems that rsync copied without error message first-setup.sh to my %HOME/context directory. When then I look into this directory, then there is no file. Subsequently command sudo sh ./first-setup.sh reports nonexistent file or directory. I tried to install it into your Applications folder too (I have administrative access), but not in this way I have not done.
> 
> (As you say: home directory should be safe and path no occure any problematic characters. My home directory is "hajtmar")
> 
> Thanx Jaroslav
> 
> Dne 17.01.16 v 13:27 Weber, Matthias napsal(a):
>> Hi Jaroslav,
>> 
>> could you explain a bit more what you mean by "the installation will fail”?
>> 
>> What error message do you get at what stage?
>> 
>> You need to make sure that you have write permission to the installation directory; anything inside your home directory should be safe.
>> Also, as a general precaution, make sure the path to your installation directory doesn’t contain unusual characters.
>> 
>> Matthias
>> 
>> 
>>> On Jan 17, 2016, at 7:19 AM, Jaroslav Hajtmar <hajtmar@gyza.cz> wrote:
>>> 
>>> Hello ConTeXist.
>>> I am trying to install a standalone ConTeXt on MacBook. I am doing everything exactly as instructed on contextgarden.net, but the installation will fail. It seems that the problem is with rsync, with copying the installation script first-setup.sh into my Mac. Since I am a longtime Windows user and I'm a newbie on OS X, I'd like to find out what the problem may be. I dont know nothing about OS X, but I suppose that might be a problem with the firewall settings or access rights to the directories which  I use to install ConTeXt etc. Can someone please advise how to perform the installation? There is an option to download the installation package and install ConTeXt differently?
>>> Thanks for replies.
>>> 
>>> Jaroslav Hajtmar
>>> 
>>> ___________________________________________________________________________________
>>> If your question is of interest to others as well, please add an entry to the Wiki!
>>> 
>>> maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
>>> webpage  : http://www.pragma-ade.nl / http://tex.aanhet.net
>>> archive  : http://foundry.supelec.fr/projects/contextrev/
>>> wiki     : http://contextgarden.net
>>> ___________________________________________________________________________________
>> ___________________________________________________________________________________
>> If your question is of interest to others as well, please add an entry to the Wiki!
>> 
>> maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
>> webpage  : http://www.pragma-ade.nl / http://tex.aanhet.net
>> archive  : http://foundry.supelec.fr/projects/contextrev/
>> wiki     : http://contextgarden.net
> 
>> ___________________________________________________________________________________
> 
> ___________________________________________________________________________________
> If your question is of interest to others as well, please add an entry to the Wiki!
> 
> maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
> webpage  : http://www.pragma-ade.nl / http://tex.aanhet.net
> archive  : http://foundry.supelec.fr/projects/contextrev/
> wiki     : http://contextgarden.net
> ___________________________________________________________________________________


[-- Attachment #4: Type: text/plain, Size: 485 bytes --]

___________________________________________________________________________________
If your question is of interest to others as well, please add an entry to the Wiki!

maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage  : http://www.pragma-ade.nl / http://tex.aanhet.net
archive  : http://foundry.supelec.fr/projects/contextrev/
wiki     : http://contextgarden.net
___________________________________________________________________________________

  parent reply	other threads:[~2016-01-17 13:38 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-17 12:19 Jaroslav Hajtmar
2016-01-17 12:27 ` Weber, Matthias
2016-01-17 13:08   ` Jaroslav Hajtmar
2016-01-17 13:20     ` Weber, Matthias
2016-01-17 13:38     ` Otared Kavian [this message]
2016-01-17 15:56       ` Jaroslav Hajtmar
2016-01-17 16:57         ` Otared Kavian
2016-01-17 17:32           ` Jaroslav Hajtmar

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=23516000-490D-45D8-BEAD-1B392CD9702E@gmail.com \
    --to=otared@gmail.com \
    --cc=ntg-context@ntg.nl \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).