Gentoo Forums
Gentoo Forums
Gentoo Forums
Quick Search: in
@BASH@: bad interpreter
View unanswered posts
View posts from last 24 hours

 
This topic is locked: you cannot edit posts or make replies.    Gentoo Forums Forum Index Gentoo for Mac OS X (Portage for Mac OS X)
View previous topic :: View next topic  
Author Message
jsn.x
n00b
n00b


Joined: 09 Aug 2006
Posts: 18
Location: san francisco bay, usa

PostPosted: Sat Mar 08, 2008 12:48 am    Post subject: @BASH@: bad interpreter Reply with quote

I'm following the install tutorial for OS X, and I've gotten to the point where we install portage the second time. The failure is a little strange:

Code:

 :; env FEATURES="-collision-protect" emerge --oneshot portage
  <...snip.../>
/opt/gentoo/var/tmp/portage/sys-apps/portage-2.2.00.9271/temp/environment: ./bin/emake: @BASH@: bad interpreter: No such file or directory
 * ERROR: sys-apps/portage-2.2.00.9271 failed:
 *   emake failed
 *
 * Call stack:
 *               ebuild.sh:  46: <call src_compile>
 *             environment:2444:     emake || die "emake failed";
 *
 * If you need support, post the topmost build error, and the call stack if relevant.
 * build log: '/opt/gentoo/var/tmp/portage/sys-apps/portage-2.2.00.9271/temp/build.log'
 * ebuild environment: '/opt/gentoo/var/tmp/portage/sys-apps/portage-2.2.00.9271/temp/environment'
 * S: '/opt/gentoo/var/tmp/portage/sys-apps/portage-2.2.00.9271/work/prefix-portage-2.2.00.9271'


This looks like a case where configure has failed to replace @BASH@ with a path to bash. All the scripts in the work dir (/opt/gentoo/var/tmp/portage/sys-apps/portage-2.2.00.9271/work/prefix-portage-2.2.00.9271/bin) have #!@BASH@ at the top of them.
_________________
--
_jsn
Back to top
View user's profile Send private message
jsn.x
n00b
n00b


Joined: 09 Aug 2006
Posts: 18
Location: san francisco bay, usa

PostPosted: Mon Mar 10, 2008 1:52 am    Post subject: Re: @BASH@: bad interpreter Reply with quote

I made it work! Yes! Now I can have Gentoo on my Mac! Yeah!

The magic words:
Code:

for f in $EPREFIX/usr/lib/portage/bin/*
do
    ln -s $f $EPREFIX/usr/bin/
done


The "#!@BASH@: bad interpreter" error is a result of putting ./bin at the end of my path. When bash can't find emake higher up -- in $EPREFIX/usr/bin, for example -- it goes ahead and calls ./bin/emake in the install directory, which of course hasn't had a shell substituted into it yet.

If I remove ./bin from my path, I just get "emake: command not found", so evidently something is not right with the way portage is bootstrapped into place. Is it a bug that the symlinks I mention above are not created automatically?
_________________
--
_jsn
Back to top
View user's profile Send private message
grobian
Developer
Developer


Joined: 31 May 2006
Posts: 64

PostPosted: Thu Mar 27, 2008 9:01 am    Post subject: Reply with quote

did you perhaps forget to set your path as instructed at the top of the bootstrap guide?
_________________
Gentoo on a different level
Back to top
View user's profile Send private message
Display posts from previous:   
This topic is locked: you cannot edit posts or make replies.    Gentoo Forums Forum Index Gentoo for Mac OS X (Portage for Mac OS X) All times are GMT
Page 1 of 1

 
Jump to:  
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum