Re: Weird stuff SOLVED
Hi Bernt, Glad to hear you figured it out! Cheers, Greg On Dec 1, 2011, at 8:10 PM, Bernt Hansson b...@bananmonarki.se wrote: 2011-12-02 01:53, Bernt Hansson skrev: At some points one is an idiot! /var/db/ports was pointing at the wrong directory and not the ports directory. Well, well you live to learn. 2011-12-01 17:13, Chris Brennan skrev: On Thu, Dec 1, 2011 at 10:54 AM, Bernt Hanssonb...@bananmonarki.se wrote: 2011-12-01 15:11, Greg Larkin skrev: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 12/1/11 8:37 AM, Bernt Hansson wrote: Hello list! Trying to upgrade 3:d party stuff. Only get errors. What gives? --- Upgrading 'jasper-1.900.1_9' to 'jasper-1.900.1_10' (graphics/jasper) --- Building '/usr/ports/graphics/jasper' === Cleaning for jasper-1.900.1_10 cd /usr/home/bernt/disk8/ports/**graphics/jasper make config; === Cannot create , check permissions *** Error code 1 Stop in /usr/home/bernt/disk8/ports/**graphics/jasper. *** Error code 1 Stop in /usr/home/bernt/disk8/ports/**graphics/jasper. ** Command failed [exit code 1]: /usr/bin/script -qa /tmp/portupgrade2030-**48187-8vcb9-0 env UPGRADE_TOOL=portupgrade UPGRADE_PORT=jasper-1.900.1_9 UPGRADE_PORT_VER=1.900.1_9 make DEPENDS_TARGET=package ** Fix the problem and try again. Permission is 777 Hi Bernt, Reading through /usr/ports/Mk/bsd.port.mk, the check permissions message is emitted when certain directories cannot be created. Are you running the upgrade as the root user? I would be interested in seeing the output of the following command sequence: cd /usr/ports/graphics/jasper make -V SU_CMD make -V UID make -V OPTIONSFILE %su - Password: testbox# cd /usr/ports/graphics/jasper testbox# make -V SU_CMD /usr/bin/su root -c testbox# make -V UID 0 testbox# make -V OPTIONSFILE /var/db/ports/jasper/options Also, what happens if you simply do this: cd /usr/ports/graphics/jasper make config testbox# cd /usr/ports/graphics/jasper make config === Cannot create , check permissions *** Error code 1 Stop in /usr/home/bernt/disk8/ports/**graphics/jasper. I did this also, as root cd /usr/ports (it's a link) mkdir 1 cd /usr/home/bernt/disk8/ports/graphics/jasper mkdir 1 mkdir: 1: File exists Creating files/dirs don't seem to be a problem. /dev/ad0s2g 8.7G 8.3G -322M 104% /usr /dev/ad14.eli 902G 126G 775G 14% /usr/home/bernt/disk8 I'm gonna take a stab in the dark here, paste the result of the following cmd: mount | grep ad14 Just to make sure. testbox# fsck -y -t ufs /dev/ad14.eli ** /dev/ad14.eli ** Last Mounted on /usr/home/bernt/disk8 ** Phase 1 - Check Blocks and Sizes ** Phase 2 - Check Pathnames ** Phase 3 - Check Connectivity ** Phase 4 - Check Reference Counts ** Phase 5 - Check Cyl groups 440342 files, 66312180 used, 406697750 free (144630 frags, 50819140 blocks, 0.0% fragmentation) * FILE SYSTEM IS CLEAN * testbox# mount /dev/ad14.eli /usr/home/bernt/disk8 testbox# mount | grep ad14 /dev/ad14.eli on /usr/home/bernt/disk8 (ufs, local, soft-updates) testbox Possibly, you have a weird mount option being passed to the mountpoint, that is preventing you from building ports at this location. On a side note, why exactly do you need ports on an encrypted gli conainer? It's not a need per se only so I could rule out any space issue. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Weird stuff
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 12/1/11 8:37 AM, Bernt Hansson wrote: Hello list! Trying to upgrade 3:d party stuff. Only get errors. What gives? --- Upgrading 'jasper-1.900.1_9' to 'jasper-1.900.1_10' (graphics/jasper) --- Building '/usr/ports/graphics/jasper' === Cleaning for jasper-1.900.1_10 cd /usr/home/bernt/disk8/ports/graphics/jasper make config; === Cannot create , check permissions *** Error code 1 Stop in /usr/home/bernt/disk8/ports/graphics/jasper. *** Error code 1 Stop in /usr/home/bernt/disk8/ports/graphics/jasper. ** Command failed [exit code 1]: /usr/bin/script -qa /tmp/portupgrade2030-48187-8vcb9-0 env UPGRADE_TOOL=portupgrade UPGRADE_PORT=jasper-1.900.1_9 UPGRADE_PORT_VER=1.900.1_9 make DEPENDS_TARGET=package ** Fix the problem and try again. Permission is 777 Hi Bernt, Reading through /usr/ports/Mk/bsd.port.mk, the check permissions message is emitted when certain directories cannot be created. Are you running the upgrade as the root user? I would be interested in seeing the output of the following command sequence: cd /usr/ports/graphics/jasper make -V SU_CMD make -V UID make -V OPTIONSFILE Also, what happens if you simply do this: cd /usr/ports/graphics/jasper make config Regards, Greg - -- Greg Larkin http://www.FreeBSD.org/ - The Power To Serve http://www.sourcehosting.net/ - Ready. Set. Code. http://twitter.com/cpucycle/ - Follow you, follow me -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.11 (Darwin) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAk7Xiv4ACgkQ0sRouByUApAoAQCgzkRr80OZkz4cIBAJmEGK4tzR rm4An2+qDSo8SiBY7tDDkDJa6Jg+3Lf/ =8t74 -END PGP SIGNATURE- ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Weird stuff
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 12/1/11 10:54 AM, Bernt Hansson wrote: 2011-12-01 15:11, Greg Larkin skrev: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 12/1/11 8:37 AM, Bernt Hansson wrote: Hello list! Trying to upgrade 3:d party stuff. Only get errors. What gives? --- Upgrading 'jasper-1.900.1_9' to 'jasper-1.900.1_10' (graphics/jasper) --- Building '/usr/ports/graphics/jasper' === Cleaning for jasper-1.900.1_10 cd /usr/home/bernt/disk8/ports/graphics/jasper make config; === Cannot create , check permissions *** Error code 1 Stop in /usr/home/bernt/disk8/ports/graphics/jasper. *** Error code 1 Stop in /usr/home/bernt/disk8/ports/graphics/jasper. ** Command failed [exit code 1]: /usr/bin/script -qa /tmp/portupgrade2030-48187-8vcb9-0 env UPGRADE_TOOL=portupgrade UPGRADE_PORT=jasper-1.900.1_9 UPGRADE_PORT_VER=1.900.1_9 make DEPENDS_TARGET=package ** Fix the problem and try again. Permission is 777 Hi Bernt, Reading through /usr/ports/Mk/bsd.port.mk, the check permissions message is emitted when certain directories cannot be created. Are you running the upgrade as the root user? I would be interested in seeing the output of the following command sequence: cd /usr/ports/graphics/jasper make -V SU_CMD make -V UID make -V OPTIONSFILE %su - Password: testbox# cd /usr/ports/graphics/jasper testbox# make -V SU_CMD /usr/bin/su root -c testbox# make -V UID 0 testbox# make -V OPTIONSFILE /var/db/ports/jasper/options Also, what happens if you simply do this: cd /usr/ports/graphics/jasper make config testbox# cd /usr/ports/graphics/jasper make config === Cannot create , check permissions *** Error code 1 Stop in /usr/home/bernt/disk8/ports/graphics/jasper. I did this also, as root cd /usr/ports (it's a link) mkdir 1 cd /usr/home/bernt/disk8/ports/graphics/jasper mkdir 1 mkdir: 1: File exists Creating files/dirs don't seem to be a problem. /dev/ad0s2g 8.7G8.3G -322M 104%/usr /dev/ad14.eli902G126G775G14%/usr/home/bernt/disk8 Does /usr/ports link directly to /usr/home/bernt/disk8/ports/graphics/jasper? I wouldn't expect that's the case, but that's what the transcript above implies. Does this problem happen with other ports as well or just graphics/jasper? Do you have an /etc/make.conf file, and if so, what are the contents? What is the output of the following commands? ls -l /var/db/ports/jasper cat /var/db/ports/jasper/options Regards, Greg -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.11 (Darwin) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAk7Xp9IACgkQ0sRouByUApAwPgCfd00wf5oxpdSWQQoGw9H3DZb1 gosAn27BTLABAckWgIrJwmqhlOkFzAlP =Ymv+ -END PGP SIGNATURE- ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Weird stuff
On Thu, Dec 1, 2011 at 10:54 AM, Bernt Hansson b...@bananmonarki.se wrote: 2011-12-01 15:11, Greg Larkin skrev: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 12/1/11 8:37 AM, Bernt Hansson wrote: Hello list! Trying to upgrade 3:d party stuff. Only get errors. What gives? --- Upgrading 'jasper-1.900.1_9' to 'jasper-1.900.1_10' (graphics/jasper) --- Building '/usr/ports/graphics/jasper' === Cleaning for jasper-1.900.1_10 cd /usr/home/bernt/disk8/ports/**graphics/jasper make config; === Cannot create , check permissions *** Error code 1 Stop in /usr/home/bernt/disk8/ports/**graphics/jasper. *** Error code 1 Stop in /usr/home/bernt/disk8/ports/**graphics/jasper. ** Command failed [exit code 1]: /usr/bin/script -qa /tmp/portupgrade2030-**48187-8vcb9-0 env UPGRADE_TOOL=portupgrade UPGRADE_PORT=jasper-1.900.1_9 UPGRADE_PORT_VER=1.900.1_9 make DEPENDS_TARGET=package ** Fix the problem and try again. Permission is 777 Hi Bernt, Reading through /usr/ports/Mk/bsd.port.mk, the check permissions message is emitted when certain directories cannot be created. Are you running the upgrade as the root user? I would be interested in seeing the output of the following command sequence: cd /usr/ports/graphics/jasper make -V SU_CMD make -V UID make -V OPTIONSFILE %su - Password: testbox# cd /usr/ports/graphics/jasper testbox# make -V SU_CMD /usr/bin/su root -c testbox# make -V UID 0 testbox# make -V OPTIONSFILE /var/db/ports/jasper/options Also, what happens if you simply do this: cd /usr/ports/graphics/jasper make config testbox# cd /usr/ports/graphics/jasper make config === Cannot create , check permissions *** Error code 1 Stop in /usr/home/bernt/disk8/ports/**graphics/jasper. I did this also, as root cd /usr/ports (it's a link) mkdir 1 cd /usr/home/bernt/disk8/ports/**graphics/jasper mkdir 1 mkdir: 1: File exists Creating files/dirs don't seem to be a problem. /dev/ad0s2g 8.7G8.3G -322M 104%/usr /dev/ad14.eli902G126G775G14%/usr/home/bernt/disk8 I'm gonna take a stab in the dark here, paste the result of the following cmd: mount | grep ad14 Possibly, you have a weird mount option being passed to the mountpoint, that is preventing you from building ports at this location. On a side note, why exactly do you need ports on an encrypted gli conainer? -- Chris Brennan A: Yes. Q: Are you sure? A: Because it reverses the logical flow of conversation. Q: Why is top posting frowned upon? http://xkcd.com/84/ | http://xkcd.com/149/ | http://xkcd.com/549/ GPG: D5B20C0C (6741 8EE4 6C7D 11FB 8DA8 9E4A EECD 9A84 D5B2 0C0C) ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Weird stuff
On Thu, 01 Dec 2011 09:11:10 -0500 Greg Larkin wrote: Reading through /usr/ports/Mk/bsd.port.mk, the check permissions message is emitted when certain directories cannot be created. The actual error is: === Cannot create , check permissions Note the space before the comma. I suspect it's trying to create a directory using an undefined name variable. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Weird stuff
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 12/1/11 12:21 PM, RW wrote: On Thu, 01 Dec 2011 09:11:10 -0500 Greg Larkin wrote: Reading through /usr/ports/Mk/bsd.port.mk, the check permissions message is emitted when certain directories cannot be created. The actual error is: === Cannot create , check permissions Note the space before the comma. I suspect it's trying to create a directory using an undefined name variable. Yes, I noticed that and have been trying to figure out why the shell variable optionsdir seems to be empty. I can't see how that's possible yet, but I can't wait to find out! - -g - -- Greg Larkin http://www.FreeBSD.org/ - The Power To Serve http://www.sourcehosting.net/ - Ready. Set. Code. http://twitter.com/cpucycle/ - Follow you, follow me -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.11 (Darwin) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAk7Xw+gACgkQ0sRouByUApDo6QCfaV9YM94ryI3GcAqzhqp3e4+j zoMAoLlXwq3TlB6UUBN3C2VD9iwQtUqv =6eEc -END PGP SIGNATURE- ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Weird stuff
2011-12-01 17:14, Greg Larkin skrev: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 12/1/11 10:54 AM, Bernt Hansson wrote: 2011-12-01 15:11, Greg Larkin skrev: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 12/1/11 8:37 AM, Bernt Hansson wrote: Hello list! Trying to upgrade 3:d party stuff. Only get errors. What gives? ---Upgrading 'jasper-1.900.1_9' to 'jasper-1.900.1_10' (graphics/jasper) ---Building '/usr/ports/graphics/jasper' ===Cleaning for jasper-1.900.1_10 cd /usr/home/bernt/disk8/ports/graphics/jasper make config; === Cannot create , check permissions *** Error code 1 Stop in /usr/home/bernt/disk8/ports/graphics/jasper. *** Error code 1 Stop in /usr/home/bernt/disk8/ports/graphics/jasper. ** Command failed [exit code 1]: /usr/bin/script -qa /tmp/portupgrade2030-48187-8vcb9-0 env UPGRADE_TOOL=portupgrade UPGRADE_PORT=jasper-1.900.1_9 UPGRADE_PORT_VER=1.900.1_9 make DEPENDS_TARGET=package ** Fix the problem and try again. Permission is 777 Hi Bernt, Reading through /usr/ports/Mk/bsd.port.mk, the check permissions message is emitted when certain directories cannot be created. Are you running the upgrade as the root user? I would be interested in seeing the output of the following command sequence: cd /usr/ports/graphics/jasper make -V SU_CMD make -V UID make -V OPTIONSFILE %su - Password: testbox# cd /usr/ports/graphics/jasper testbox# make -V SU_CMD /usr/bin/su root -c testbox# make -V UID 0 testbox# make -V OPTIONSFILE /var/db/ports/jasper/options Also, what happens if you simply do this: cd /usr/ports/graphics/jasper make config testbox# cd /usr/ports/graphics/jasper make config === Cannot create , check permissions *** Error code 1 Stop in /usr/home/bernt/disk8/ports/graphics/jasper. I did this also, as root cd /usr/ports (it's a link) mkdir 1 cd /usr/home/bernt/disk8/ports/graphics/jasper mkdir 1 mkdir: 1: File exists Creating files/dirs don't seem to be a problem. /dev/ad0s2g 8.7G8.3G -322M 104%/usr /dev/ad14.eli902G126G775G14%/usr/home/bernt/disk8 Does /usr/ports link directly to /usr/home/bernt/disk8/ports/graphics/jasper? No, it's a link from /usr/ports to /usr/home/bernt/disk8/ports I wouldn't expect that's the case, but that's what the transcript above implies. Does this problem happen with other ports as well or just graphics/jasper? --- ** Upgrade tasks 10: 0 done, 0 ignored, 0 skipped and 9 failed --- Upgrade of multimedia/vlc started at: Fri, 02 Dec 2011 01:20:54 +0100 --- Upgrading 'vlc-1.1.11_3,3' to 'vlc-1.1.12,3' (multimedia/vlc) OK? [yes] --- Build of multimedia/vlc started at: Fri, 02 Dec 2011 01:20:55 +0100 --- Building '/usr/ports/multimedia/vlc' === Cleaning for vlc-1.1.12,3 cd /usr/home/bernt/disk8/ports/multimedia/vlc make config; === Cannot create , check permissions *** Error code 1 Stop in /usr/home/bernt/disk8/ports/multimedia/vlc. *** Error code 1 Stop in /usr/home/bernt/disk8/ports/multimedia/vlc. ** Command failed [exit code 1]: /usr/bin/script -qa /tmp/portupgrade20111202-3139-oh1rz5-0 env UPGRADE_TOOL=portupgrade UPGRADE_PORT=vlc-1.1.11_3,3 UPGRADE_PORT_VER=1.1.11_3,3 make ** Fix the problem and try again. --- Build of multimedia/vlc ended at: Fri, 02 Dec 2011 01:20:57 +0100 (consumed 00:00:02) --- Upgrade of multimedia/vlc ended at: Fri, 02 Dec 2011 01:20:57 +0100 (consumed 00:00:03) --- ** Upgrade tasks 10: 0 done, 0 ignored, 0 skipped and 10 failed --- Listing the results (+:done / -:ignored / *:skipped / !:failed) ! x11/pixman (pixman-0.22.2)(unknown build error) ! x11/babl (babl-0.1.4) (unknown build error) ! x11/xterm (xterm-276) (unknown build error) ! graphics/jasper (jasper-1.900.1_9)(unknown build error) ! news/pan (pan-0.134) (unknown build error) ! graphics/inkscape (inkscape-0.48.1_3) (unknown build error) ! graphics/gegl (gegl-0.1.6_1) (unknown build error) ! graphics/gimp-app (gimp-app-2.6.11_4,1) (unknown build error) ! multimedia/audacious-plugins (audacious-plugins-2.5.4_1) (unknown build error) ! multimedia/vlc (vlc-1.1.11_3,3) (unknown build error) --- Packages processed: 0 done, 0 ignored, 0 skipped and 10 failed --- Session ended at: Fri, 02 Dec 2011 01:20:57 +0100 (consumed 00:01:30) Do you have an /etc/make.conf file, and if so, what are the contents? # added by use.perl 2011-11-12 09:33:03 PERL_VERSION=5.12.4 What is the output of the following commands? ls -l /var/db/ports/jasper testbox# ls -l /var/db/ports/jasper ls: /var/db/ports/jasper: No such file or directory testbox# cat /var/db/ports/jasper/options testbox# cat /var/db/ports/jasper/options cat: /var/db/ports/jasper/options: No such file or directory testbox# /Bernt ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe,
Re: Weird stuff
2011-12-01 17:13, Chris Brennan skrev: On Thu, Dec 1, 2011 at 10:54 AM, Bernt Hanssonb...@bananmonarki.se wrote: 2011-12-01 15:11, Greg Larkin skrev: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 12/1/11 8:37 AM, Bernt Hansson wrote: Hello list! Trying to upgrade 3:d party stuff. Only get errors. What gives? ---Upgrading 'jasper-1.900.1_9' to 'jasper-1.900.1_10' (graphics/jasper) ---Building '/usr/ports/graphics/jasper' ===Cleaning for jasper-1.900.1_10 cd /usr/home/bernt/disk8/ports/**graphics/jasper make config; === Cannot create , check permissions *** Error code 1 Stop in /usr/home/bernt/disk8/ports/**graphics/jasper. *** Error code 1 Stop in /usr/home/bernt/disk8/ports/**graphics/jasper. ** Command failed [exit code 1]: /usr/bin/script -qa /tmp/portupgrade2030-**48187-8vcb9-0 env UPGRADE_TOOL=portupgrade UPGRADE_PORT=jasper-1.900.1_9 UPGRADE_PORT_VER=1.900.1_9 make DEPENDS_TARGET=package ** Fix the problem and try again. Permission is 777 Hi Bernt, Reading through /usr/ports/Mk/bsd.port.mk, the check permissions message is emitted when certain directories cannot be created. Are you running the upgrade as the root user? I would be interested in seeing the output of the following command sequence: cd /usr/ports/graphics/jasper make -V SU_CMD make -V UID make -V OPTIONSFILE %su - Password: testbox# cd /usr/ports/graphics/jasper testbox# make -V SU_CMD /usr/bin/su root -c testbox# make -V UID 0 testbox# make -V OPTIONSFILE /var/db/ports/jasper/options Also, what happens if you simply do this: cd /usr/ports/graphics/jasper make config testbox# cd /usr/ports/graphics/jasper make config === Cannot create , check permissions *** Error code 1 Stop in /usr/home/bernt/disk8/ports/**graphics/jasper. I did this also, as root cd /usr/ports (it's a link) mkdir 1 cd /usr/home/bernt/disk8/ports/graphics/jasper mkdir 1 mkdir: 1: File exists Creating files/dirs don't seem to be a problem. /dev/ad0s2g 8.7G8.3G -322M 104%/usr /dev/ad14.eli902G126G775G14%/usr/home/bernt/disk8 I'm gonna take a stab in the dark here, paste the result of the following cmd: mount | grep ad14 Just to make sure. testbox# fsck -y -t ufs /dev/ad14.eli ** /dev/ad14.eli ** Last Mounted on /usr/home/bernt/disk8 ** Phase 1 - Check Blocks and Sizes ** Phase 2 - Check Pathnames ** Phase 3 - Check Connectivity ** Phase 4 - Check Reference Counts ** Phase 5 - Check Cyl groups 440342 files, 66312180 used, 406697750 free (144630 frags, 50819140 blocks, 0.0% fragmentation) * FILE SYSTEM IS CLEAN * testbox# mount /dev/ad14.eli /usr/home/bernt/disk8 testbox# mount | grep ad14 /dev/ad14.eli on /usr/home/bernt/disk8 (ufs, local, soft-updates) testbox Possibly, you have a weird mount option being passed to the mountpoint, that is preventing you from building ports at this location. On a side note, why exactly do you need ports on an encrypted gli conainer? It's not a need per se only so I could rule out any space issue. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Weird stuff SOLVED
2011-12-02 01:53, Bernt Hansson skrev: At some points one is an idiot! /var/db/ports was pointing at the wrong directory and not the ports directory. Well, well you live to learn. 2011-12-01 17:13, Chris Brennan skrev: On Thu, Dec 1, 2011 at 10:54 AM, Bernt Hanssonb...@bananmonarki.se wrote: 2011-12-01 15:11, Greg Larkin skrev: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 12/1/11 8:37 AM, Bernt Hansson wrote: Hello list! Trying to upgrade 3:d party stuff. Only get errors. What gives? --- Upgrading 'jasper-1.900.1_9' to 'jasper-1.900.1_10' (graphics/jasper) --- Building '/usr/ports/graphics/jasper' === Cleaning for jasper-1.900.1_10 cd /usr/home/bernt/disk8/ports/**graphics/jasper make config; === Cannot create , check permissions *** Error code 1 Stop in /usr/home/bernt/disk8/ports/**graphics/jasper. *** Error code 1 Stop in /usr/home/bernt/disk8/ports/**graphics/jasper. ** Command failed [exit code 1]: /usr/bin/script -qa /tmp/portupgrade2030-**48187-8vcb9-0 env UPGRADE_TOOL=portupgrade UPGRADE_PORT=jasper-1.900.1_9 UPGRADE_PORT_VER=1.900.1_9 make DEPENDS_TARGET=package ** Fix the problem and try again. Permission is 777 Hi Bernt, Reading through /usr/ports/Mk/bsd.port.mk, the check permissions message is emitted when certain directories cannot be created. Are you running the upgrade as the root user? I would be interested in seeing the output of the following command sequence: cd /usr/ports/graphics/jasper make -V SU_CMD make -V UID make -V OPTIONSFILE %su - Password: testbox# cd /usr/ports/graphics/jasper testbox# make -V SU_CMD /usr/bin/su root -c testbox# make -V UID 0 testbox# make -V OPTIONSFILE /var/db/ports/jasper/options Also, what happens if you simply do this: cd /usr/ports/graphics/jasper make config testbox# cd /usr/ports/graphics/jasper make config === Cannot create , check permissions *** Error code 1 Stop in /usr/home/bernt/disk8/ports/**graphics/jasper. I did this also, as root cd /usr/ports (it's a link) mkdir 1 cd /usr/home/bernt/disk8/ports/graphics/jasper mkdir 1 mkdir: 1: File exists Creating files/dirs don't seem to be a problem. /dev/ad0s2g 8.7G 8.3G -322M 104% /usr /dev/ad14.eli 902G 126G 775G 14% /usr/home/bernt/disk8 I'm gonna take a stab in the dark here, paste the result of the following cmd: mount | grep ad14 Just to make sure. testbox# fsck -y -t ufs /dev/ad14.eli ** /dev/ad14.eli ** Last Mounted on /usr/home/bernt/disk8 ** Phase 1 - Check Blocks and Sizes ** Phase 2 - Check Pathnames ** Phase 3 - Check Connectivity ** Phase 4 - Check Reference Counts ** Phase 5 - Check Cyl groups 440342 files, 66312180 used, 406697750 free (144630 frags, 50819140 blocks, 0.0% fragmentation) * FILE SYSTEM IS CLEAN * testbox# mount /dev/ad14.eli /usr/home/bernt/disk8 testbox# mount | grep ad14 /dev/ad14.eli on /usr/home/bernt/disk8 (ufs, local, soft-updates) testbox Possibly, you have a weird mount option being passed to the mountpoint, that is preventing you from building ports at this location. On a side note, why exactly do you need ports on an encrypted gli conainer? It's not a need per se only so I could rule out any space issue. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: 7.2-RELEASE/amd64 - weird stuff in dmesg
Le 11/09/2009 à 15:03:36+1000, Alex R a écrit Any ideas??? Anyone?? No. But I got this kind of message since 7.0. Do you have «no classic» network ? Regards. JAS -- Albert SHIH SIO batiment 15 Observatoire de Paris Meudon 5 Place Jules Janssen 92195 Meudon Cedex Téléphone : 01 45 07 76 26/06 86 69 95 71 Heure local/Local time: Ven 11 sep 2009 09:21:42 CEST ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: 7.2-RELEASE/amd64 - weird stuff in dmesg
On Thu, 10 Sep 2009 13:03:44 +1000 Alex R a...@mailinglist.ahhyes.net wrote: Hi everyone, I was wondering whether anyone could shed some light on the following messages I am seeing in dmesg: 33aarrpp:: uunnkknnoowwnn hhaarrddwwaarree aaress format (0x) ress format (0x) arp: unakrnpo:w nu nhkanrodwwna rhea raddwdarrees sa dfdorremsast f(o0rxm0a0t0 0()0 x ) arp:3 uanrkpn:o wunn khnaorwdnw ahraer dawdadrree sasd dfroersmsa tf o(r0mxat0 0(00x000)0 0 ) arp: unknown hardware address format (0xarp:0 7u0n0k)n o wn hardware address format (0x0700) aarrpp:: uunnkknnoowwnn hhaarrddwwaarree aarree ffoorrmmaatt ((00xx0077)) -- Any ideas whats with the jumbled/double letters? Is there something wrong with the machine or is it a bug in the OS? I have seen similar symptoms on SMP enabled boxes when shutting down if 2 processes call kprintf() or printf() at the same time, it results in garbled output. Should i turn a blind eye to this? Yes :) It's a known issue that the kernel printf isn't locked so messages get mixed up like that.In 8.0 the PRINTF_BUFR_SIZE option has been added which should fix it. -- Bruce ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: 7.2-RELEASE/amd64 - weird stuff in dmesg
Any ideas??? Anyone?? Alex R wrote: Hi everyone, I was wondering whether anyone could shed some light on the following messages I am seeing in dmesg: 33aarrpp:: uunnkknnoowwnn hhaarrddwwaarree aaress format (0x) ress format (0x) arp: unakrnpo:w nu nhkanrodwwna rhea raddwdarrees sa dfdorremsast f(o0rxm0a0t0 0()0 x ) arp:3 uanrkpn:o wunn khnaorwdnw ahraer dawdadrree sasd dfroersmsa tf o(r0mxat0 0(00x000)0 0 ) arp: unknown hardware address format (0xarp:0 7u0n0k)n o wn hardware address format (0x0700) aarrpp:: uunnkknnoowwnn hhaarrddwwaarree aarree ffoorrmmaatt ((00xx0077)) -- Any ideas whats with the jumbled/double letters? Is there something wrong with the machine or is it a bug in the OS? I have seen similar symptoms on SMP enabled boxes when shutting down if 2 processes call kprintf() or printf() at the same time, it results in garbled output. Should i turn a blind eye to this? ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
7.2-RELEASE/amd64 - weird stuff in dmesg
Hi everyone, I was wondering whether anyone could shed some light on the following messages I am seeing in dmesg: 33aarrpp:: uunnkknnoowwnn hhaarrddwwaarree aaress format (0x) ress format (0x) arp: unakrnpo:w nu nhkanrodwwna rhea raddwdarrees sa dfdorremsast f(o0rxm0a0t0 0()0 x ) arp:3 uanrkpn:o wunn khnaorwdnw ahraer dawdadrree sasd dfroersmsa tf o(r0mxat0 0(00x000)0 0 ) arp: unknown hardware address format (0xarp:0 7u0n0k)n o wn hardware address format (0x0700) aarrpp:: uunnkknnoowwnn hhaarrddwwaarree aarree ffoorrmmaatt ((00xx0077)) -- Any ideas whats with the jumbled/double letters? Is there something wrong with the machine or is it a bug in the OS? I have seen similar symptoms on SMP enabled boxes when shutting down if 2 processes call kprintf() or printf() at the same time, it results in garbled output. Should i turn a blind eye to this? ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Weird stuff after moving to a new MB
Gary Lum [EMAIL PROTECTED] writes: I had FreeBSD 5.1 installed on an older Dual 440BX motherboard which was current with CVS. I replaced the board with a 440GX dual. Basically, I took the HD out of the old system and put into the new since the boards are pretty similar.The system is working but there seems to be some quirks such as the Onboard NIC will not pick up a connection( IT is recognized by the System and uses the same driver (FXP)) and the floppy drive will not read a floppy at anytime (At boot too). I've rebuilt world and kernel and still have the same problems. I'm also noticing now that after reconfiguring X, my mouse is chunky. To be honest, it's chunky in the mouse setup in /stand/sysinstall too. I'm leaning towards a flakey board but have to admit my naivity in that it may be due to not reinstalling from CD. Suggestions, comments? The floppy is one thing -- if it won't work at boot, then FreeBSD probably isn't related to its problems. The NIC may be a different issue; you could try booting from the install CD and see if it works from there. The mouse I'm even less sure about; it sounds like it could be an interrupt problem, but that's a sort of vague guess. Then again, I'm still running 4.x (5.x won't boot at all on my spare machine, thanks to the inclusion of AGP in the default kernels)... ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Weird stuff after moving to a new MB
Yeah, it's kinda weird with the floppy, it'll make the noises like it's trying to start and just sit there, Same thing with the IDE drives. Have tried to boot from CD as well. The FreeBSD will start and get hung after loading uhcio (??) and I'll have to power cycle the system. Windows 2000 install hangs when it tries to start Windows 2000. Sigh.. and it's such a nice board otherwise --- Lowell Gilbert [EMAIL PROTECTED] wrote: Gary Lum [EMAIL PROTECTED] writes: I had FreeBSD 5.1 installed on an older Dual 440BX motherboard which was current with CVS. I replaced the board with a 440GX dual. Basically, I took the HD out of the old system and put into the new since the boards are pretty similar.The system is working but there seems to be some quirks such as the Onboard NIC will not pick up a connection( IT is recognized by the System and uses the same driver (FXP)) and the floppy drive will not read a floppy at anytime (At boot too). I've rebuilt world and kernel and still have the same problems. I'm also noticing now that after reconfiguring X, my mouse is chunky. To be honest, it's chunky in the mouse setup in /stand/sysinstall too. I'm leaning towards a flakey board but have to admit my naivity in that it may be due to not reinstalling from CD. Suggestions, comments? The floppy is one thing -- if it won't work at boot, then FreeBSD probably isn't related to its problems. The NIC may be a different issue; you could try booting from the install CD and see if it works from there. The mouse I'm even less sure about; it sounds like it could be an interrupt problem, but that's a sort of vague guess. Then again, I'm still running 4.x (5.x won't boot at all on my spare machine, thanks to the inclusion of AGP in the default kernels)... __ Do you Yahoo!? Yahoo! Hotjobs: Enter the Signing Bonus Sweepstakes http://hotjobs.sweepstakes.yahoo.com/signingbonus ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Weird stuff after moving to a new MB
Hello everyone, I'm hoping that someone might be able to give me some ideas on what to check to rule out a flakey MB. I had FreeBSD 5.1 installed on an older Dual 440BX motherboard which was current with CVS. I replaced the board with a 440GX dual. Basically, I took the HD out of the old system and put into the new since the boards are pretty similar.The system is working but there seems to be some quirks such as the Onboard NIC will not pick up a connection( IT is recognized by the System and uses the same driver (FXP)) and the floppy drive will not read a floppy at anytime (At boot too). I've rebuilt world and kernel and still have the same problems. I'm also noticing now that after reconfiguring X, my mouse is chunky. To be honest, it's chunky in the mouse setup in /stand/sysinstall too. I'm leaning towards a flakey board but have to admit my naivity in that it may be due to not reinstalling from CD. Suggestions, comments? __ Do you Yahoo!? Yahoo! Hotjobs: Enter the Signing Bonus Sweepstakes http://hotjobs.sweepstakes.yahoo.com/signingbonus ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
