portupgrade -rf gettext -m BATCH=yes fails at gnomemeeting stage
Jeremy Messenger
mezz7 at cox.net
Sun Feb 8 16:38:34 PST 2004
On Mon, 9 Feb 2004 00:23:06 +0000, Stacey Roberts
<stacey at vickiandstacey.com> wrote:
> Hello Mezz,
>
> ----- Original Message -----
> From: "Jeremy Messenger <mezz7 at cox.net>"
> To: To Stacey Roberts
> Date: Sun, 08 Feb, 2004 21:47 GMT
> Subject: Re: portupgrade -rf gettext -m BATCH=yes fails at gnomemeeting
> stage
>
>> On Sun, 8 Feb 2004 21:25:58 +0000, Stacey Roberts
>> <stacey at vickiandstacey.com> wrote:
>>
>> >Hello Adam,
>> >
>> >----- Original Message -----
>> >From: "Adam Weinberger <adamw at FreeBSD.org>"
>> >To: To Stacey Roberts
>> >Date: Sun, 08 Feb, 2004 17:23 GMT
>> >Subject: Re: portupgrade -rf gettext -m BATCH=yes fails at gnomemeeting
>> >stage
>> >
>> >>>> (02.08.2004 @ 0625 PST): Stacey Roberts said, in 15K: <<
>> >>> Hello Adam,
>> >>>
>> >>> I've just ran the commands that Mezz recommended, with the same
>> >>results, same errors:
>> >>>
>> >>> # portsclean -C
>> >>> Cleaning out /usr/ports/*/*/work...
>> >>> Delete /usr/ports/net/gnomemeeting/work
>> >>> done.
>> >>> Demon# portupgrade -f gnomemeeting\*
>> >>> ---> Upgrading 'gnomemeeting-0.98.5_1' to 'gnomemeeting-0.98.5_2'
>> >>(net/gnomemeeting)
>> >>> ---> Building '/usr/ports/net/gnomemeeting'
>> >>> ===> Cleaning for gnomemeeting-0.98.5_2
>> >>> ===> Vulnerability check disabled
>> >>> ===> Extracting for gnomemeeting-0.98.5_2
>> >>> >> Checksum OK for gnomemeeting-0.98.5.tar.bz2.
>> >>> ===> Patching for gnomemeeting-0.98.5_2
>> >>> ===> Applying FreeBSD patches for gnomemeeting-0.98.5_2
>> >>> ===> gnomemeeting-0.98.5_2 depends on file: /nonexistent - found
>> >>>
>> >>> <snip, snip>
>> >>>
>> >>> checking for PTLib includes...
>> >>> checking for
>> >>/usr/ports/net/gnomemeeting/../../devel/pwlib/work/pwlib/include/ptlib/pprocess.h...
>> >>no
>> >>> configure: error: You need PTLib's header files to build
>> GnomeMeeting
>> >>> ===> Script "configure" failed unexpectedly.
>> >>> Please report the problem to roger at FreeBSD.org [maintainer] and
>> >>attach the
>> >>> "/usr/ports/net/gnomemeeting/work/gnomemeeting-0.98.5/config.log"
>> >>including
>> >>> the output of the failure of your make command. Also, it might be a
>> >>good idea
>> >>> to provide an overview of all packages installed on your system
>> (e.g.
>> >>an `ls
>> >>> /var/db/pkg`).
>> >>> *** Error code 1
>> >>>
>> >>> Stop in /usr/ports/net/gnomemeeting.
>> >>> ** Command failed [exit code 1]: /usr/bin/script -qa
>> >>/tmp/portupgrade63486.0 make
>> >>> ** Fix the problem and try again.
>> >>> ** The following packages were not installed or upgraded (*:skipped
>> /
>> >>!:failed)
>> >>> ! net/gnomemeeting (gnomemeeting-0.98.5_1) (configure
>> >>error)
>> >>> #
>> >>>
>> >>> What would then be the best way forward now?
>> >>>
>> >>> Regards,
>> >>>
>> >>> Stacey
>> >>>> end of "Re: portupgrade -rf gettext -m BATCH=yes fails at
>> >>gnomemeeting stage" from Stacey Roberts <<
>> >>
>> >>Stacey -
>> >>
>> >>If you have a file /nonexistent on your system, delete it.
>> >>
>> >
>> >Err.., I've just noticed that there are two similarly sounding dirs:
>> >~ $ ls /
>> >COPYRIGHT dev kernel.GENERIC nonexistant stand
>> >bin dist kernel.old nonexistent sys
>> >boot etc mnt proc tmp
>> >cdrom home modules root usr
>> >compat kernel modules.old sbin var
>> >stacey at Demon ~ $
>> >
>> >One was produced when I created a machine account (this server acts as
>> >the samba PDC here on my network):
>> >stacey at Demon ~ $ ls -la /nonexistent/
>> >total 20
>> >drwxr-xr-x 2 <snipped>$ <snipped>$ 512 Nov 30 13:30 .
>> >drwxr-xr-x 20 root wheel 512 Dec 6 18:27 ..
>> >-rw-r--r-- 1 <snipped>$ <snipped>$ 771 Nov 30 13:30 .cshrc
>> >-rw-r--r-- 1 <snipped>$ <snipped>$ 255 Nov 30 13:30 .login
>> >-rw-r--r-- 1 <snipped>$ <snipped>$ 165 Nov 30 13:30 .login_conf
>> >-rw------- 1 <snipped>$ <snipped>$ 371 Nov 30 13:30 .mail_aliases
>> >-rw-r--r-- 1 <snipped>$ <snipped>$ 331 Nov 30 13:30 .mailrc
>> >-rw-r--r-- 1 <snipped>$ <snipped>$ 801 Nov 30 13:30 .profile
>> >-rw------- 1 <snipped>$ <snipped>$ 276 Nov 30 13:30 .rhosts
>> >-rw-r--r-- 1 <snipped>$ <snipped>$ 852 Nov 30 13:30 .shrc
>> >stacey at Demon ~ $
>> >
>> >So.., I'm not sure of the meaning behind your thinking that I should
>> >blast this dir
>> >
>> >Do get back to me on this.., I'm very intrigued by this suggestion.
>>
>> Do you think it will work if you add 'NONEXISTENT=/nonexistent1' in the
>> /etc/make.conf, Adam?
>
> For what its worth.., I had a check on other servers here, and
> /nonexistent *does* exist on those systems as well - in fact even on
> workstations. So I can't see why this is a required option for this
> machine.
No, you don't understand. The /nonexistent has to be not exist to make the
gnomemeeting install works. It's why I thought why not to add '1' in the
front for short time only for gnomemeeting's sake.
>> Anyway, I believe the second method in the old archive should work, but
>> only one addidion is that you need to deinstall gnomemeeting or use
>> force
>> overwrite install option.
>
> Exactly *how* do I specify "force overwrite install"?
There are many options... You can do like this: make -DFORCE_PKG_REGISTER
install , be sure to run pkgdb -F after that because it will ask you to
unregister old one.
>> http://lists.freebsd.org/pipermail/freebsd-gnome/2003-September/002924.html
>> :
>> =============================
>> 1) Go to devel/pwlib and do the 'make'
>> 2) Go to net/openh323 and do the 'make'
>> 3) Try it again, do the 'make install' in the net/gnomemeeting
>> =============================
>>
>
> Okay., I've just kicked of "make" in /usr/ports/devel/pwlib. Here's what
> I'll do: -
>
> 1] If pwlib's make completes, I'll move on to openh323 (see [2]). If it
> fails, I'll post the errors back here.
>
> 2] I'll run "make" in /usr/ports/net/openh323. If this completes
> successfully, I'll move onto (see [3]) gnomemeeting. If it fails, I'll
> post errors here.
>
> 3] I'll run /usr/ports/net/gnomemeeting/make install.
>
> I'll post errors I get along the way.., Here's hoping this works..,
> Thanks again., i shouldn't neglect to keep saying that.
Just make sure to not touch the 'make clean' or it will fail. gnomemeeting
required the two work directories of pwlib and openh323 to build, so you
are safe to do the clean after gnomemeeting successed..
Cheers,
Mezz
> Regards,
>
> Stacey
>
>
>> Cheers,
>> Mezz
>>
>> >Regards,
>> >
>> >Stacey
>> >
>> >># Adam
>> >>
>> >>
>> >>--
>> >>Adam Weinberger
>> >>adam at vectors.cx // adamw at FreeBSD.org // adamw at magnesium.net
>> >>http://www.vectors.cx
>>
>>
>> --
>> bsdforums.org 's moderator, mezz.
--
bsdforums.org 's moderator, mezz.
More information about the freebsd-gnome
mailing list