Bug 35907
| Summary: | Attempts to build mozilla fail (on current?) | ||
|---|---|---|---|
| Product: | Ports & Packages | Reporter: | Garance A Drosehn <gad> |
| Component: | Individual Port(s) | Assignee: | freebsd-gnome (Nobody) <gnome> |
| Status: | Closed FIXED | ||
| Severity: | Affects Only Me | CC: | gad |
| Priority: | Normal | ||
| Version: | Latest | ||
| Hardware: | Any | ||
| OS: | Any | ||
|
Description
Garance A Drosehn
2002-03-15 00:50:01 UTC
Responsible Changed From-To: freebsd-ports->gnome over to maintainer I recently build Mozilla 0.9.9 on a -CURRENT machine, and it worked fine. Are you still able to reproduce this problem with a recent -CURRENT, and mozilla-0.9.9_3,1? Thanks. Joe On Saturday, April 6, 2002, at 05:59 PM, Joe Marcus Clarke wrote: > I recently build Mozilla 0.9.9 on a -CURRENT machine, and it worked > fine. Are you still able to reproduce this problem with a recent > -CURRENT, and mozilla-0.9.9_3,1? Thanks. In one of my earlier attempts to fix this, I completely removed mozilla and tried to rebuild it. When that didn't work, I ended up with no version of mozilla installed. So, today I cvsup'ed my ports tree to the latest snapshot, and tried to: portupgrade -N mozilla It died with the same error. However, it does seem pretty odd that the error seems consistent to me for nearly a month now, and yet other people are not complaining about it. So, then I did a 'make clean', and removed the distfile for mozilla-0.9.9. I then tried 'cd /usr/ports/www/mozilla ; make', but that also failed with the same error. I still think it's mighty odd that no one else has reported this, so I will try a few more things and see if I can figure out where the problem might be. At this point, my freebsd-current system is a snapshot from March 31st, if that's significant. --- Garance Alistair Drosehn = gad@gilead.acs.rpi.edu Senior Systems Programmer or gad@FreeBSD.org Rensselaer Polytechnic Institute; Troy NY USA On Sat, 2002-04-06 at 23:26, Garance A Drosehn wrote: > On Saturday, April 6, 2002, at 05:59 PM, Joe Marcus Clarke wrote: > > I recently build Mozilla 0.9.9 on a -CURRENT machine, and it worked > > fine. Are you still able to reproduce this problem with a recent > > -CURRENT, and mozilla-0.9.9_3,1? Thanks. > > In one of my earlier attempts to fix this, I completely removed mozilla > and tried to rebuild it. When that didn't work, I ended up with no > version of mozilla installed. So, today I cvsup'ed my ports tree to the > latest snapshot, and tried to: > portupgrade -N mozilla > > It died with the same error. However, it does seem pretty odd that the > error seems consistent to me for nearly a month now, and yet other > people are not complaining about it. So, then I did a 'make clean', and > removed the distfile for mozilla-0.9.9. I then tried 'cd > /usr/ports/www/mozilla ; make', but that also failed with the same error. > > I still think it's mighty odd that no one else has reported this, so I > will try a few more things and see if I can figure out where the problem > might be. At this point, my freebsd-current system is a snapshot from > March 31st, if that's significant. What CFLAGS are you using (i.e. in /etc/make.conf)? I'm using the default CFLAGS of -O -pipe, and I don't see this problem. When I buid on -CURRENT, the directory created is: FreeBSD5.0_cc_DBG.OBJ Joe > > --- > Garance Alistair Drosehn = gad@gilead.acs.rpi.edu > Senior Systems Programmer or gad@FreeBSD.org > Rensselaer Polytechnic Institute; Troy NY USA > > On Sunday, April 7, 2002, at 12:14 AM, Joe Marcus Clarke wrote: > What CFLAGS are you using (i.e. in /etc/make.conf)? I'm using the > default CFLAGS of -O -pipe, and I don't see this problem. When I build > on -CURRENT, the directory created is: > > FreeBSD5.0_cc_DBG.OBJ Hmm. I don't see *any* FreeBSD directory created. I used 'script' to save a copy of the make, and there is no reference to anything with FreeBSD5.0 in it until it tries to run ../../coreconf/nsinstall/FreeBSD5.0_OPT.OBJ/nsinstall which does not exist... My /etc/make.conf isn't too interesting: CFLAGS= -O -pipe NOCLEANDEPENDS=true USA_RESIDENT= YES XFREE86_VERSION=4 KERNCONF=Dual-650P3-LessWit DISTDIR=/usr/cvs/distfiles I am running XFree86-4.2. I was also doing that back when I first noticed this problem, and it is possible that was the first time I tried to rebuild mozilla since switching to XFree86-4.2. Right now that's the only port I have which is slightly out-of-date, so I think I'll rebuild that. If that doesn't work, maybe I'll try a buildworld. --- Garance Alistair Drosehn = gad@gilead.acs.rpi.edu Senior Systems Programmer or gad@FreeBSD.org Rensselaer Polytechnic Institute; Troy NY USA On Sun, 2002-04-07 at 00:58, Garance A Drosehn wrote: > > On Sunday, April 7, 2002, at 12:14 AM, Joe Marcus Clarke wrote: > > What CFLAGS are you using (i.e. in /etc/make.conf)? I'm using the > > default CFLAGS of -O -pipe, and I don't see this problem. When I build > > on -CURRENT, the directory created is: > > > > FreeBSD5.0_cc_DBG.OBJ > > Hmm. I don't see *any* FreeBSD directory created. I used 'script' to > save a copy of the make, and there is no reference to anything with > FreeBSD5.0 in it until it tries to run > ../../coreconf/nsinstall/FreeBSD5.0_OPT.OBJ/nsinstall > which does not exist... > > My /etc/make.conf isn't too interesting: > > CFLAGS= -O -pipe > NOCLEANDEPENDS=true > USA_RESIDENT= YES > XFREE86_VERSION=4 > KERNCONF=Dual-650P3-LessWit > DISTDIR=/usr/cvs/distfiles > > I am running XFree86-4.2. I was also doing that back when I first > noticed this problem, and it is possible that was the first time I tried > to rebuild mozilla since switching to XFree86-4.2. Right now that's the > only port I have which is slightly out-of-date, so I think I'll rebuild > that. If that doesn't work, maybe I'll try a buildworld. Could be. I'm running 4.2.0 as well, but I built -CURRENT after all the binutils crap was sorted out. If you have some old ports that might have been compiled under the old binutils, you may want to upgrade them as well, then try rebuilding mozilla. In any event, keep me posted. Joe > > --- > Garance Alistair Drosehn = gad@gilead.acs.rpi.edu > Senior Systems Programmer or gad@FreeBSD.org > Rensselaer Polytechnic Institute; Troy NY USA > > On Sunday, April 7, 2002, at 01:07 AM, Joe Marcus Clarke wrote: > On Sun, 2002-04-07 at 00:58, Garance A Drosehn wrote: >> I am running XFree86-4.2. I was also doing that back when I first >> noticed this problem, and it is possible that was the first time I >> tried to rebuild mozilla since switching to XFree86-4.2. Right now >> that's the only port I have which is slightly out-of-date, so I think >> I'll rebuild that. If that doesn't work, maybe I'll try a buildworld. > > Could be. I'm running 4.2.0 as well, but I built -CURRENT after all > the binutils crap was sorted out. If you have some old ports that > might have been compiled under the old binutils, you may want to > upgrade them as well, then try rebuilding mozilla. In any event, keep > me posted. Okay, today I did a buildworld/installworld on current. I then did a force-rebuild of zip freetype gmake ORBit jpeg png libmng glib gtk lcms imake netpbm tiff2png gdk-pixbuf jbigkit Which seemed to be everything that mozilla would care about, except for rebuilding all of X11 yet again. I did seem to have some kind of mixup between the jbigkit and netpbm ports, but it looks like that was not relevant. After getting all of those to rebuild right, I still get the same error when I try to build mozilla: ../../coreconf/nsinstall/FreeBSD5.0_OPT.OBJ/nsinstall -R -m 775 FreeBSD/nsinstall /usr/ports/www/mozilla/work/mozilla/dist/bin gmake[4]: ../../coreconf/nsinstall/FreeBSD5.0_OPT.OBJ/nsinstall: Command not found And in my log file, the above is the first time that anything like 'FreeBSD5.*' is seen. I'm still quite willing to believe it's something odd about my freebsd-current system, but I'm running out of ideas of what might correct it. I may have to break down and actually look at the makefiles! --- Garance Alistair Drosehn = gad@gilead.acs.rpi.edu Senior Systems Programmer or gad@FreeBSD.org Rensselaer Polytechnic Institute; Troy NY USA I rebuilt an even larger number of ports on my freebsd-current, and still couldn't build mozilla. I then rebooted into my freebsd-stable machine, just to see if I can build it there (in general I am almost always running on my current system). I cvsup'ed my ports collection, and updated several ports which have nothing to do with mozillia, and that went fine. Then I tried to 'portupgrade -Rr mozilla', and that died complaining about some configuration problem when trying to rebuild ORBit. I force-rebuild my autoconfig ports, and also upgraded to the latest stable via buildworld/installworld. It still fails with a configure error. I tried rebuilding mozilla without doing ORBit, and that died with another configuration error (ie, not the same error that I get trying to build mozilla on my freebsd-current system). At this point, I'm afraid I'm going to say that I'm sick of the whole mess. I don't know what's wrong, but I've spent much more than 24 hours trying to rebuild things in a few dozen different ways, and mozilla just isn't worth that much of my time. Hopefully this problem is specific to my machine, and some day I'll figure out out or happen to rebuild whatever is broken. If you find something which DOES seem connected to the problem I'm seeing, please let me know. thanks. --- Garance Alistair Drosehn = gad@gilead.acs.rpi.edu Senior Systems Programmer or gad@FreeBSD.org Rensselaer Polytechnic Institute; Troy NY USA On Tue, 2002-04-09 at 23:42, Garance A Drosehn wrote: > I rebuilt an even larger number of ports on my freebsd-current, and > still couldn't build mozilla. I then rebooted into my freebsd-stable > machine, just to see if I can build it there (in general I am almost > always running on my current system). I cvsup'ed my ports collection, > and updated several ports which have nothing to do with mozillia, and > that went fine. > > Then I tried to 'portupgrade -Rr mozilla', and that died complaining > about some configuration problem when trying to rebuild ORBit. I > force-rebuild my autoconfig ports, and also upgraded to the latest > stable via buildworld/installworld. It still fails with a configure > error. I tried rebuilding mozilla without doing ORBit, and that died > with another configuration error (ie, not the same error that I get > trying to build mozilla on my freebsd-current system). Chances are your ORBit problem can be fixed by making sure gettext and gettext-old are both installed and up-to-date. > > At this point, I'm afraid I'm going to say that I'm sick of the whole > mess. I don't know what's wrong, but I've spent much more than 24 hours > trying to rebuild things in a few dozen different ways, and mozilla just > isn't worth that much of my time. Hopefully this problem is specific to > my machine, and some day I'll figure out out or happen to rebuild > whatever is broken. If you find something which DOES seem connected to > the problem I'm seeing, please let me know. thanks. I'll keep looking into it. Working in tech support by day gives me an undying need to solve problems ;-}. Thanks for the update. Joe > > --- > Garance Alistair Drosehn = gad@gilead.acs.rpi.edu > Senior Systems Programmer or gad@FreeBSD.org > Rensselaer Polytechnic Institute; Troy NY USA > > On Wednesday, April 10, 2002, at 12:14 AM, Joe Marcus Clarke wrote: > On Tue, 2002-04-09 at 23:42, Garance A Drosehn wrote: >> Then I tried to 'portupgrade -Rr mozilla' [on freebsd-stable], and >> that died complaining about some configuration problem when trying >> to rebuild ORBit. [...] I tried rebuilding mozilla without doing >> ORBit, and that died with another configuration error (ie, not the >> same error that I get trying to build mozilla on my freebsd-current >> system). > > Chances are your ORBit problem can be fixed by making sure gettext > and gettext-old are both installed and up-to-date. I rebuilt both gettext and gettext-old, and then I was able to upgrade to the latest ORBit. Thanks. I then tried mozilla on my freebsd-stable system. It did not get the configuration-time error that I mentioned above, but it did fail once it got to the same coreconf/nsinstall step where it dies when I try to build it on my freebsd-current system. >> If you find something which DOES seem connected to the problem >> I'm seeing, please let me know. thanks. > > I'll keep looking into it. Working in tech support by day gives > me an undying need to solve problems ;-}. Thanks for the update. Thanks for the reply. It was *really* frustrating to see it die at a different spot on my freebsd-stable system! I may look into this again sometime later on, but probably not this week. I really have to concentrate on my tax forms for the rest of this week!! :-) --- Garance Alistair Drosehn = gad@gilead.acs.rpi.edu Senior Systems Programmer or gad@FreeBSD.org Rensselaer Polytechnic Institute; Troy NY USA On Wednesday, April 10, 2002, at 12:14 AM, Joe Marcus Clarke wrote: > On Tue, 2002-04-09 at 23:42, Garance A Drosehn wrote: >> Then I tried to 'portupgrade -Rr mozilla', and that died complaining >> about some configuration problem when trying to rebuild ORBit. > > Chances are your ORBit problem can be fixed by making sure gettext > and gettext-old are both installed and up-to-date. I forgot to mention: on my freebsd-current system, I only had the gettext port. I did not have gettext-old installed. I did install that and rebuilt both of them on my freebsd-current system and tried to build mozilla again, but that did not fix the problem. --- Garance Alistair Drosehn = gad@gilead.acs.rpi.edu Senior Systems Programmer or gad@FreeBSD.org Rensselaer Polytechnic Institute; Troy NY USA On Wednesday, April 10, 2002, at 12:14 AM, Joe Marcus Clarke wrote: > On Tue, 2002-04-09 at 23:42, Garance A Drosehn wrote: >> I don't know what's wrong, but I've spent much more than 24 hours >> trying to rebuild things in a few dozen different ways, and mozilla >> just isn't worth that much of my time. > > I'll keep looking into it. Working in tech support by day gives > me an undying need to solve problems ;-}. Thanks for the update. Well, I'm also driven to get to the bottom of things which "make no sense" to me. If everyone was reporting this problem, then I probably wouldn't have spent any significant time on it myself, because I don't really need mozilla for anything. However, it drove me *nuts* that this was consistently happening to me, and yet no one else. So, I spent yet another day building, rebooting, removing, adding, rearranging, installing, recompiling, and other things. I have now successfully rebuilt mozilla. You are not going to believe what the catalyst is for my problems. I use bash as my shell under root. My .login file checks if /usr/local/bin/bash exists, and if so it switches the login from csh to bash. This probably effects a few other things in my environment (such as my PATH setting). I have not pinned down the EXACT cause of the problem, but if I change my .login file so it does not switch to bash, then I can build mozilla. Mozilla is the only port which needs to be build "from csh" instead of from bash. Now that I seem to have *some* answer for this mystery, maybe I can finally catch up on my sleep! Later I'll figure out whether it's bash per se, or if it's something else in the environment which touches off the problem. If it isn't bash vs csh, then I expect it is a difference in the PATH setting (probably no /usr/local/sbin in PATH when I run under bash). --- Garance Alistair Drosehn = gad@gilead.acs.rpi.edu Senior Systems Programmer or gad@FreeBSD.org Rensselaer Polytechnic Institute; Troy NY USA On Thu, 2002-04-11 at 01:55, Garance A Drosehn wrote: > > On Wednesday, April 10, 2002, at 12:14 AM, Joe Marcus Clarke wrote: > > On Tue, 2002-04-09 at 23:42, Garance A Drosehn wrote: > >> I don't know what's wrong, but I've spent much more than 24 hours > >> trying to rebuild things in a few dozen different ways, and mozilla > >> just isn't worth that much of my time. > > > > I'll keep looking into it. Working in tech support by day gives > > me an undying need to solve problems ;-}. Thanks for the update. > > Well, I'm also driven to get to the bottom of things which "make no > sense" to me. If everyone was reporting this problem, then I probably > wouldn't have spent any significant time on it myself, because I don't > really need mozilla for anything. However, it drove me *nuts* that > this was consistently happening to me, and yet no one else. > > So, I spent yet another day building, rebooting, removing, adding, > rearranging, installing, recompiling, and other things. I have now > successfully rebuilt mozilla. You are not going to believe what the > catalyst is for my problems. > > I use bash as my shell under root. My .login file checks if > /usr/local/bin/bash exists, and if so it switches the login from > csh to bash. This probably effects a few other things in my > environment (such as my PATH setting). I have not pinned down the > EXACT cause of the problem, but if I change my .login file so it > does not switch to bash, then I can build mozilla. Mozilla is the > only port which needs to be build "from csh" instead of from bash. > > Now that I seem to have *some* answer for this mystery, maybe I can > finally catch up on my sleep! Later I'll figure out whether it's > bash per se, or if it's something else in the environment which > touches off the problem. If it isn't bash vs csh, then I expect it > is a difference in the PATH setting (probably no /usr/local/sbin > in PATH when I run under bash). I was just thinking this morning that it might be an environment variable common to both your -stable and -current machines. In any event, I'm glad you're closer to tracking down the issue. Joe > > --- > Garance Alistair Drosehn = gad@gilead.acs.rpi.edu > Senior Systems Programmer or gad@FreeBSD.org > Rensselaer Polytechnic Institute; Troy NY USA > > On Thursday, April 11, 2002, at 12:55 AM, Garance A Drosehn wrote: > Later I'll figure out whether it's bash per se, or if it's something > else in the environment which touches off the problem. My .bashrc file defines an environment variable called PLATFORM (and it has defined it for many years now...). I use the same basic config files and scripts on various versions of six different OS's, and I use this variable to govern how various scripts behave on the different platforms. If I remove that one environment variable, mozilla will build for me under bash. The actual "freebsd port" files do not reference PLATFORM at all, so I seem to be tripping over something in mozilla itself. I did grep thru mozilla source files and found a number of files which use something called PLATFORM. Looking at the logfiles of the two compiles (working and non-working), it looks like some of these references will get the value mozilla builds, and other references get the value defined in my .bashrc. So, it looks like this is not something that needs to be fixed in the freebsd port. I probably should pursue this with the mozilla folks, but for the moment I think I'll just change the name of that variable in my .bashrc & related scripts. Maybe PLATFORM_asSetIn_bAshRc_for_GarancE_ScriPts -- that shouldn't conflict with anything! Apologies for dragging you along on my wild goose chase! Thanks for all the replies. --- Garance Alistair Drosehn = gad@gilead.acs.rpi.edu Senior Systems Programmer or gad@FreeBSD.org Rensselaer Polytechnic Institute; Troy NY USA On Thu, 2002-04-11 at 22:01, Garance A Drosehn wrote: > On Thursday, April 11, 2002, at 12:55 AM, Garance A Drosehn wrote: > > Later I'll figure out whether it's bash per se, or if it's something > > else in the environment which touches off the problem. > > My .bashrc file defines an environment variable called PLATFORM (and it > has defined it for many years now...). I use the same basic config > files and scripts on various versions of six different OS's, and I use > this variable to govern how various scripts behave on the different > platforms. > > If I remove that one environment variable, mozilla will build for me > under bash. The actual "freebsd port" files do not reference PLATFORM > at all, so I seem to be tripping over something in mozilla itself. I > did grep thru mozilla source files and found a number of files which use > something called PLATFORM. > > Looking at the logfiles of the two compiles (working and non-working), > it looks like some of these references will get the value mozilla > builds, and other references get the value defined in my .bashrc. > > So, it looks like this is not something that needs to be fixed in the > freebsd port. I probably should pursue this with the mozilla folks, but > for the moment I think I'll just change the name of that variable in my > .bashrc & related scripts. Maybe > PLATFORM_asSetIn_bAshRc_for_GarancE_ScriPts -- that shouldn't conflict > with anything! > > Apologies for dragging you along on my wild goose chase! > Thanks for all the replies. Not a problem. This will be a very educational PR. I will see what can be done from the FreeBSD port side. Joe > > --- > Garance Alistair Drosehn = gad@gilead.acs.rpi.edu > Senior Systems Programmer or gad@FreeBSD.org > Rensselaer Polytechnic Institute; Troy NY USA > > State Changed
From-To: open->closed
This turned out to be a configuration issue on the submitter's machine.
When the environment variable PLATFORM is set, Mozilla's build tried to
use it for cross-compiling purposes. If it is set to a value that isn't
appropriate for the build, things will fail.
The long and short is to check if you have ${PLATFORM} set to an
undesired value. If so, unset it for the purposes of the Mozilla build.
|
