am I the only one, wrt gcc44 -- it is failing and I can't build
octave or much else
Kenneth Freidank
kennethcf at earthlink.net
Wed Nov 4 03:01:00 UTC 2009
I believe ports and packages to be 2 separate items. pkg_info has to do with what packages you have installed. The ports system has to
Different mechanisms are available to manage the source tree that t he ports system uses to create packages. I believe each of these
diff directory, an published changes. Yo at any time, even if you don or never install the built port.&nbs your 1st question is that you begin wit followed by updates that you manage.
So far, I have not talked about installing yet.
Once a port has been built, you can install it. Unless you save th built port as a package (the 'make package' command), you will not be
abl command).&n want. command), the packag database is what pkg_in
Some commands in the different mechanisms you have available&n manage your ports source, can be used to help select which pack ages need updating when you install an update to a package.
About your 2nd question, I have no idea. I keep track of how to bu ild a system, keeping copies of config files, then I make backups file or data systems on an ongoing basis.
Re gc44. FreeBSD 7.2 comes with 4.2 already installed. Maybe you installed 4.4 on top of it, something got messed up, or an option must be set for both to co-exist. I don't know, but I would try to k eep with the version that came with the system ( just an unjustified
p binaries
-----Original Message-----
From: Henry Olyer
Sent: Nov 3, 2009 8:21 AM
To: Kenneth Freidank
Cc: freebsd-questions at freebsd.org, Chris Whitehouse
Subject: Re: am I the only one, wrt gcc44 -- it is fa can't build octave or much else
I'm sorry fellows.
You guys have given me great support and apparently I didn't get back
be more careful about this.
Okay -- I was able to get my mouse working.
I made a ServerFlags section in my xorg.conf and suddenly!, my mouse
m
Next, I have wonderful X sessions now.
Next, I am prepared to nuke the /usr/ports area if I am told to do
tha past little nervous it come back.)
Question: Does the rebuild process examine the pkg_info results load up the directory appropriately?. or is it "one size fits all?"
Question: Does anyone have a solution for doing a general machin backup to one file? So that I can back the machine up and later, su bsequently, perform a simple restore. Because I've been using the
mac backups miss o experience. What's possib As for gcc44, I am fairly certain that it's actually broken -- that
th the port it Oh., and in a conversation with an HP technical representative
recentl constituted a " On Mon, Nov 2, 2009 at 11:13 PM, Kenneth Freidank <[1]kennethcf at earthlink.net> wrote:
Here are partial listings of my co to your config files and see if that do 100% sure that everything is required, but i it works. Attached is the xorg.conf file I gene in the directory /etc/X11/. When you have done make sure your user belongs to the group "wheel", then login. start X, give the command:
startx
You should get 3 wi title bar. If you type "exi return, that will end your X session. &nb "fatal error" messages in your console window when X Also, make sure you have installed the nvidia drivers per other postings. You can check if you have the package installed
by pkg_info | grep nvidia
You should see at a minimum:
nidia-driver-185.18.29 NVidia graphics card binary drivers for
hardw You have to build this packages and install it. documented in the NetBSD documents and my other postings f installing FreeBSD on a Compaq Presario CQ60.
File /etc/rc.co linux_enable="YES"
moused_enable="YES"
keyrate="fast" saver="star"
hald_enable="YES"
dbus_enable="YES"
vesa_lo File /boot/loader.conf
nvidia_load="YES"
-----Original Message-----
>From: Henry Olyer <[2]henry.olyer at gmail.com >Sent: Oct 26, 2009 2:53 AM
>To: [3]freebsd-questions at freebsd.org>Cc: Kenneth
<[4]kennethcf at earthlink.net>, Chris Whitehouse
<[5]cwhiteh at onetel.com>
>Su can't build &nbs >
>'everything; is dying i >
>I know, (in all likelihood,) I'll ha do a
>complete re-install. Fine. &n anything to mess
>this area up in t >
>I've just been going to various directories saying, "make
>install clean" and now this... when this
>happened.
>
>So >
>I also want/need doesn't yet let
>me move th now?
>
&g xorg.conf file. > I'm sorry, I just don't know these things...
>
>
&g >
>===> Building for gcc-4.4.2.20091006
&g >gmake[1]: Entering directory `/usr/po >gmake[2]: Entering directory `/usr/ports/ >gmake[3]: Entering directory `/usr/ports/lang >rm -f stage_current
>gmake[3]: Leaving dire >gmake[2]: Leaving directory >gmake[2]: Entering directory `/u >gmake[3]: Entering directory `/usr/p orts/lang/gcc44/work/build/libiberty'
>gmake[4]: Entering
directory>`/usr/ports/lang/gcc44/work/build/libiberty/testsuite'
>gmake[4 >gmake[4]: Leaving directory
> >gmake[3]: Lea `/usr/ports/lang/gcc44/work/build/libiberty'
>gmake[3] `/usr/ports/lang/gcc44/work/build/intl'
>gmake[3 >gmake[3]: Leaving directory `/usr/p orts/lang/gcc44/work/build/intl'
>gmake[3]: Entering directory
> ;`/usr/ports/lang/gcc44/work/build/build-i386-portbld-freebsd7.2/li
biberty' >gmake[4]: Entering directory
>`/usr/ports/lang/gcc44/work/bui ld/build-i386-portbld-freebsd7.2/libiberty/testsuite'
>gmake[4]: Noth >gmake[4]: Leaving directory
>`/usr/p orts/lang/gcc44/work/build/build-i386-portbld-freebsd7.2/libiberty/
testsuit >gmake[3]: Leaving directory
>`/usr/ports/lang/gcc44/work/bu ild/build-i386-portbld-freebsd7.2/libiberty'
>gmake[3]: Entering dire >`/usr/ports/lang/gcc44/work/build/build-i386-portbld-freebsd7. 2/fixincludes'
>gmake[3]: Nothing to be done for `all'.
>gmake[ >`/usr/ports/lang/gcc44/work/build/build-i386-p ortbld-freebsd7.2/fixincludes'
>gmake[3]: Entering directory `/usr/po rts/lang/gcc44/work/build/zlib'
>true "AR_FLAGS=rc" "CC_FOR_BUILD -fkeep-inline-functions"
>"CXXFLAGS=-g -fkeep-i >-fno-strict-aliasing -pipe >ocal/include" "CFLAGS_FOR_TARGET=-g -O2 -fno-strict-alias -pipe
>-I/usr/local/include" "INSTALL=/usr/bin/install -c -o ro wheel"
>"INSTALL_DATA=install -o root -
>g wheel -m 555"
> "LDFLAGS=" "LIB >-O2 -fno-strict-aliasin
>g -pipe -I/usr/local/incl >-fno-strict-aliasing -pipe -I/us >"MAKEINFO=makeinfo --no-split --sp >000 --split-size=5000000 --split-size=5000000" " >"PICFLAG_FOR_TARGET=" "SHELL=/bin/sh" "EXPECT=expe "RUNTEST=runtest"
>"RUNTESTFLAGS=" "exec_prefix=/usr/loca>l"
"infodir=/usr/local/info/gcc44" "libdir=/usr/local/lib/gcc44"< BR>>"prefix=/usr/local"
"tooldir=/usr/local/i386-portbld-freebsd7.2" >"AS=as" "CC=cc" "CXX=c++" "LD=
>/usr/bin/ld >-I/usr/local/includ "DESTDIR=" DO=all
>mu >gmake[3]: Leaving directory `/usr/ports/lang/gcc44/wo rk/build/zlib'
>gmake[3]: Entering directory `/usr/ports/lang/gcc44/w ork/build/libcpp'
>gmake[3]: Nothing to be done for `all'.
>gma `/usr/ports/lang/gcc44/work/build/libcpp'
>g `/usr/ports/lang/gcc44/work/build/libdecnumber' >gmake[3]: Nothing to be done for `all'.
>gmake[3]: Leaving di `/usr/ports/lang/gcc44/work/build/libdecnumber'
>gmake[3]: En `/usr/ports/lang/gcc44/work/build/gcc'
>gmake[3]: Le `/usr/ports/lang/gcc44/work/build/gcc'
References
1. 3D"mailto:kennethcf at earthlink.net"
2. ="mailto:henry.olyer at gmail.com"
3. 3D"mailto:freebsd 4. 3D"mailto:kennethcf at earthlink.net"
5. file://localhost/tmp/3D"mail
More information about the freebsd-questions
mailing list