So for example when I just tried to install bibledit it failed on the dependency gdk-pixbuf2, so I did this:
sudo port clean --all gdk-pixbuf2
sudo port install gdk-pixbuf2 (the port installed successfully this time)
sudo port install bibledit (continue with the normal install procedure)
Mark
On Thu, Feb 14, 2013 at 11:19 AM, Mark Duling
<address@hidden> wrote:
Hi Simon,
You are right that you normally need to install macports with 'sudo'. I couldn't install bibledit with macports either (I'm on 10.7.5 also), but I have access rights to update the port and I noticed it was at 4.5 and 4.6 is out. So I updated the port to use 4.6 and I could install it without problems.
So do a selfupdate (sudo port selfupdate) and hopefully by the time you do the update will have been pushed out. See if that works for you.
Mark
Message: 1
Date: Thu, 14 Feb 2013 10:46:12 +0100
From: Simon Lind?n <address@hidden>
To: address@hidden
Subject: [be] Installing Bibledit on Mac OS X
Message-ID: <address@hidden>
Content-Type: text/plain; charset="iso-8859-1"
Hi!
I'm using OS X 10.7.5 and I've been advised to try out Bibleedit for a new translation we're working on. I've followed the guidelines on the bibledit homepage for installing on 10.6 (there is no guidelines for 10.7) but I can't get the installation to go through. I have virtually no idea of what I'm doing so I'm giving you the full account of what's happened since I can't discern what information is important and what is not.
Installing the dependencies seemed to work well but when I typed "port install bibledit" I got this message: "Error: Insufficient privileges to write to MacPorts install prefix".
So I tried the alternate course of installing it from source. I downloaded the source (both version 4.1 and 4.6) and followed the instructions. When I typed "./configure" I got the following output:
checking for a BSD-compatible install... /usr/bin/install -c
checking whether build environment is sane... yes
checking for a thread-safe mkdir -p... ./install-sh -c -d
checking for gawk... no
checking for mawk... no
checking for nawk... no
checking for awk... awk
checking whether make sets $(MAKE)... yes
checking how to create a ustar tar archive... gnutar
checking for gcc... gcc
checking whether the C compiler works... yes
checking for C compiler default output file name... a.out
checking for suffix of executables...
checking whether we are cross compiling... no
checking for suffix of object files... o
checking whether we are using the GNU C compiler... yes
checking whether gcc accepts -g... yes
checking for gcc option to accept ISO C89... none needed
checking for style of include used by make... GNU
checking dependency style of gcc... gcc3
checking for gcc option to accept ISO C99... -std=gnu99
checking for gcc -std=gnu99 option to accept ISO Standard C... (cached) -std=gnu99
checking how to run the C preprocessor... gcc -std=gnu99 -E
checking for g++... g++
checking whether we are using the GNU C++ compiler... yes
checking whether g++ accepts -g... yes
checking dependency style of g++... gcc3
checking for gcc... (cached) gcc
checking whether we are using the GNU C compiler... (cached) yes
checking whether gcc accepts -g... (cached) yes
checking for gcc option to accept ISO C89... (cached) none needed
checking dependency style of gcc... (cached) gcc3
checking for grep that handles long lines and -e... /usr/bin/grep
checking for egrep... /usr/bin/grep -E
checking for ANSI C header files... yes
checking for pkg-config... /usr/bin/pkg-config
checking pkg-config is at least version 0.9.0... yes
checking for GTK... no
configure: error: Gtk2 development version is needed.
I assumed that gtk2 had not been installed properly so I attempted to do it again.
bash-3.2$ sudo port install gtk2
Password:
---> Computing dependencies for gtk2
---> Cleaning gtk2
---> Updating database of binaries: 100.0%
---> Scanning binaries for linking errors: 100.0%
---> No broken files found.
I then went back to the original plan - letting macports install it. I googled the error above and found that perhaps I should just put in the keyword "sudo" before the installation command. This is the output I was given:
bash-3.2$ sudo port install bibledit
Password:
---> Computing dependencies for bibledit
---> Dependencies to be installed: nspr
---> Fetching archive for nspr
---> Attempting to fetch nspr-4.9.5_0.darwin_11.x86_64.tbz2 from http://lil.fr.packages.macports.org/nspr
---> Attempting to fetch nspr-4.9.5_0.darwin_11.x86_64.tbz2.rmd160 from http://lil.fr.packages.macports.org/nspr
---> Installing nspr @4.9.5_0
---> Activating nspr @4.9.5_0
---> Cleaning nspr
---> Fetching archive for bibledit
---> Attempting to fetch bibledit-4.5_0.darwin_11.x86_64.tbz2 from http://lil.fr.packages.macports.org/bibledit
---> Attempting to fetch bibledit-4.5_0.darwin_11.x86_64.tbz2 from http://mse.uk.packages.macports.org/sites/packages.macports.org/bibledit
---> Attempting to fetch bibledit-4.5_0.darwin_11.x86_64.tbz2 from http://packages.macports.org/bibledit
---> Fetching distfiles for bibledit
---> Attempting to fetch bibledit-gtk-4.5.tar.gz from http://lil.fr.distfiles.macports.org/bibledit
---> Verifying checksum(s) for bibledit
---> Extracting bibledit
---> Configuring bibledit
---> Building bibledit
Error: org.macports.build for port bibledit returned: command execution failed
Please see the log file for port bibledit for details:
/opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_textproc_bibledit/bibledit/main.log
To report a bug, follow the instructions in the guide:
http://guide.macports.org/#project.tickets
Error: Processing of port bibledit failed
I won't attach the whole log but I found one warning message in the end which might be relevant:
:info:build Warning: targets not executed for bibledit: org.macports.activate org.macports.build org.macports.destroot org.macports.install
Sorry for the long post but if anyone has any idea how to help me get this up and running I'd be very grateful. Is there a way to check if the dependencies have not been installed properly? It seemed to work when I did it but I am completely unfamiliar with these terminal outputs. Also, since there was no information about installing on OS X 10.7, does that mean a different route should be taken?
BG,
Simon Lind?n
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.nongnu.org/archive/html/bibledit-general/attachments/20130214/f92ab003/attachment.html>
------------------------------
Message: 2
Date: Thu, 14 Feb 2013 14:57:15 +0200
From: David Gardner <address@hidden>
To: address@hidden
Subject: Re: [be] Installing Bibledit on Mac OS X
Message-ID: <address@hidden>
Content-Type: text/plain; charset=iso-8859-1
On Thu, Feb 14, 2013 at 10:46:12AM +0100, Simon Lind?n wrote:
> configure: error: Gtk2 development version is needed.
>
> I assumed that gtk2 had not been installed properly so I attempted to do it
> again.
Hi
I know nothing about macs (last used one 2 decades ago), but I wonder if
there's a gtk2-dev or gtk2-development availble on for macports that you
need to install first?
I would have thought the build process you tried after would make sure it was
installed though, so Perhaps you should re-try the build-it-yourself
approach now, you might get further.
David
------------------------------
_______________________________________________
Bibledit-general mailing list
address@hidden
https://lists.nongnu.org/mailman/listinfo/bibledit-general
End of Bibledit-general Digest, Vol 53, Issue 1
***********************************************