Re: make buildworld powers down system

[doug]

On Fri, 2 Dec 2011, Polytropon wrote:


On Fri, 2 Dec 2011 03:28:09 -0500, Mehmet Erol Sanliturk wrote:

On Fri, Dec 2, 2011 at 3:05 AM, Polytropon  wrote:


On Fri, 2 Dec 2011 02:06:26 -0500 (EST), d...@safeport.com wrote:

The screen does go into standby and I am not
sure what is controling that, nothing in KDE or Xorg that I set, perhaps

a

sysctl setting but I did not see one in the acpi section.


This might be a dafault option. You can override it in
your /etc/X11/xorg.conf by setting

   Option "DPMS" "false"

in the section "Monitor" where you define the values
for your monitor. I had a similar experience with an
21" CRT Eizo F980 going to sleep unintendedly. :-)

--
Polytropon
Magdeburg, Germany
Happy FreeBSD user since 4.0
Andra moi ennepe, Mousa, ...


Another way may be inserting the following lines into ~/.xinitrc :

xset s off
xset -dpms


Correct, I also have those in my ~/.xinitrc together
with the xorg.conf setting above. With both settings,
screens shouldn't blank anymore.


Alas my problem is/was not with screen blanking. I do have have slightly 
upgraded 8.2. If I do not have a failing disk, I am left with something that 
carried across 2 boots. The only change I made was in the BIOS to make the 
function keys not require the  key to be a function key.

___
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: make buildworld powers down system

[Polytropon]

On Fri, 2 Dec 2011 03:28:09 -0500, Mehmet Erol Sanliturk wrote:
> On Fri, Dec 2, 2011 at 3:05 AM, Polytropon  wrote:
> 
> > On Fri, 2 Dec 2011 02:06:26 -0500 (EST), d...@safeport.com wrote:
> > > The screen does go into standby and I am not
> > > sure what is controling that, nothing in KDE or Xorg that I set, perhaps
> > a
> > > sysctl setting but I did not see one in the acpi section.
> >
> > This might be a dafault option. You can override it in
> > your /etc/X11/xorg.conf by setting
> >
> >Option "DPMS" "false"
> >
> > in the section "Monitor" where you define the values
> > for your monitor. I had a similar experience with an
> > 21" CRT Eizo F980 going to sleep unintendedly. :-)
> >
> > --
> > Polytropon
> > Magdeburg, Germany
> > Happy FreeBSD user since 4.0
> > Andra moi ennepe, Mousa, ...
> >
> 
> 
> 
> 
> Another way may be inserting the following lines into ~/.xinitrc :
> 
> xset s off
> xset -dpms

Correct, I also have those in my ~/.xinitrc together
with the xorg.conf setting above. With both settings,
screens shouldn't blank anymore.


-- 
Polytropon
Magdeburg, Germany
Happy FreeBSD user since 4.0
Andra moi ennepe, Mousa, ...
___
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: make buildworld powers down system

[Mehmet Erol Sanliturk]

On Fri, Dec 2, 2011 at 3:05 AM, Polytropon  wrote:

> On Fri, 2 Dec 2011 02:06:26 -0500 (EST), d...@safeport.com wrote:
> > The screen does go into standby and I am not
> > sure what is controling that, nothing in KDE or Xorg that I set, perhaps
> a
> > sysctl setting but I did not see one in the acpi section.
>
> This might be a dafault option. You can override it in
> your /etc/X11/xorg.conf by setting
>
>Option "DPMS" "false"
>
> in the section "Monitor" where you define the values
> for your monitor. I had a similar experience with an
> 21" CRT Eizo F980 going to sleep unintendedly. :-)
>
> --
> Polytropon
> Magdeburg, Germany
> Happy FreeBSD user since 4.0
> Andra moi ennepe, Mousa, ...
>




Another way may be inserting the following lines into ~/.xinitrc :

xset s off
xset -dpms

before the statement

exec  ... desktop_manager


such as

exec /usr/local/bin/gnome-session

etc.


OR ( every time when required )

in a terminal window of the desktop manager , enter the above xset commands
, which will be effective only up to exit from the X or shutdown of the
computer .


Thank you very much .

Mehmet Erol Sanliturk
___
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: make buildworld powers down system

[Polytropon]

On Fri, 2 Dec 2011 02:06:26 -0500 (EST), d...@safeport.com wrote:
> The screen does go into standby and I am not 
> sure what is controling that, nothing in KDE or Xorg that I set, perhaps a 
> sysctl setting but I did not see one in the acpi section.

This might be a dafault option. You can override it in
your /etc/X11/xorg.conf by setting

Option "DPMS" "false"

in the section "Monitor" where you define the values
for your monitor. I had a similar experience with an
21" CRT Eizo F980 going to sleep unintendedly. :-)

-- 
Polytropon
Magdeburg, Germany
Happy FreeBSD user since 4.0
Andra moi ennepe, Mousa, ...
___
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: make buildworld powers down system

[doug]

On Thu, 1 Dec 2011, Robert Bonomi wrote:


From owner-freebsd-questi...@freebsd.org  Thu Dec  1 01:16:21 2011
Date: Thu, 1 Dec 2011 02:14:04 -0500 (EST)
From: doug 
To: freebsd-questions@freebsd.org
Cc:
Subject: make buildworld powers down system

Three times in a row. It seems to be repeatable. At the end what should my next
debugging step be?

I ran the buildworld using script, the last lines in the make:

cc -O2 -pipe  -D_XOPEN_SOURCE_EXTENDED -DENABLE_WIDEC -I.
-I/usr/obj/usr/src/lib/ncurses/ncursesw/../ncursesw
-I/usr/src/lib/ncurses/ncursesw/../ncursesw
-I/usr/src/lib/ncurses/ncursesw/../ncurses
-I/usr/src/lib/ncurses/ncursesw/../../../contrib/ncurses/include
-I/usr/src/lib/ncurses/ncursesw/../../../contrib/ncurses/ncurses -Wall -DNDEBUG
-DHAVE_CONFIG_H -DFREEBSD_NATIVE -DTERMIOS -std=gnu99 -fstack-protector  -c
/usr/src/lib/ncurses/ncursesw/../../../contrib/ncurses/ncurses/base/lib_beep.c
cc -O2 -pipe  -D_XOPEN_SOURCE_EXTENDED -DENABLE_WIDEC -I.
-I/usr/obj/usr/src/lib/ncurses/ncursesw/../ncursesw
-I/usr/src/lib/ncurses/ncursesw/../ncursesw
-I/usr/src/lib/ncurses/ncursesw/../ncurses
-I/usr/src/lib/ncurses/ncursesw/../../../contrib/ncurses/include
-I/usr/src/lib/ncurses/ncursesw/../../../contrib/ncurses/ncurses -Wall -DNDEBUG
-DHAVE_CONFIG_H -DFREEBSD_NATIVE -DTERMIOS -std=gnu99 -fstack-protector  -c
/usr/src/lib/ncurses/ncursesw/../../../contrib/ncurses/ncurses/base/lib_bkgd.c
cc -O2 -pipe  -D_XOPEN_SOURCE_EXTENDED -DENABLE_WIDEC -I.
-I/usr/obj/usr/src/lib/ncurses/ncursesw/../ncursesw
-I/usr/src/lib/ncurses/ncursesw/../ncursesw
-I/usr/src/lib/ncurses/ncursesw/../ncurses
-I/usr/src/lib/ncurses/ncursesw/../../../contrib/ncurses/include
-I/usr/src/lib/ncurses/ncursesw/../../../contrib/ncurses/ncurses -Wall -DNDEBUG
-DHAVE_CONFIG_H -DFREEBSD_NATIVE -DTERMIOS -std=gnu99 -fstack-protector  -c
/usr/src/lib/ncurses/ncursesw/../../../contrib/ncurses/ncurses/base/lib_box.c
cc -O2 -pipe  -D_XOPEN_SOURCE_EXTENDED -DENABLE_WIDEC -I.
-I/usr/obj/usr/src/lib/ncurses/ncursesw/../ncursesw
-I/usr/src/lib/ncurses/ncursesw/../ncursesw
-I/usr/src/lib/ncurses/ncursesw/../ncurses
-I/usr/src/lib/ncurses/ncursesw/../../../contrib/ncurses/include
-I/usr/src/lib/ncurses/ncursesw/../../../contrib/ncurses/ncurses -Wall
-DNDE^@^@^@^@^@^@^@

this after about 30 minutes of running. There are no errors in the logs



First, look for *something* that would cause the machine to
sleep/suspend/hibernate/shutdown after a period of "inactivity"

It _could_ be a BIOS setting, it could be 'power mangement' software
settings.

It is also -possible- that this is a *THERMAL* issue -- that the 30+
minutes of heavy CPU utilization is triggering an overtemperature
shutdown.  Make sure all fans are working properly, and that CPU
heat-sinks are dust-free.



Thanks for your suggestions. I have ruled out hardware. I did change a BIOS 
setting to make the function keys be functions without the fn key (this is a 
Dell laptop). The only other thing I changed was to run a script to record the 
time and some of the hw.acpi sysctl values. As I now have the upgrade installed 
I will try the buildworld again. The screen does go into standby and I am not 
sure what is controling that, nothing in KDE or Xorg that I set, perhaps a 
sysctl setting but I did not see one in the acpi section.

___
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: make buildworld powers down system

[Robert Bonomi]

> From owner-freebsd-questi...@freebsd.org  Thu Dec  1 01:16:21 2011
> Date: Thu, 1 Dec 2011 02:14:04 -0500 (EST)
> From: doug 
> To: freebsd-questions@freebsd.org
> Cc: 
> Subject: make buildworld powers down system
>
> Three times in a row. It seems to be repeatable. At the end what should my 
> next 
> debugging step be?
>
> I ran the buildworld using script, the last lines in the make:
>
> cc -O2 -pipe  -D_XOPEN_SOURCE_EXTENDED -DENABLE_WIDEC -I. 
> -I/usr/obj/usr/src/lib/ncurses/ncursesw/../ncursesw 
> -I/usr/src/lib/ncurses/ncursesw/../ncursesw 
> -I/usr/src/lib/ncurses/ncursesw/../ncurses 
> -I/usr/src/lib/ncurses/ncursesw/../../../contrib/ncurses/include 
> -I/usr/src/lib/ncurses/ncursesw/../../../contrib/ncurses/ncurses -Wall 
> -DNDEBUG 
> -DHAVE_CONFIG_H -DFREEBSD_NATIVE -DTERMIOS -std=gnu99 -fstack-protector  -c 
> /usr/src/lib/ncurses/ncursesw/../../../contrib/ncurses/ncurses/base/lib_beep.c
> cc -O2 -pipe  -D_XOPEN_SOURCE_EXTENDED -DENABLE_WIDEC -I. 
> -I/usr/obj/usr/src/lib/ncurses/ncursesw/../ncursesw 
> -I/usr/src/lib/ncurses/ncursesw/../ncursesw 
> -I/usr/src/lib/ncurses/ncursesw/../ncurses 
> -I/usr/src/lib/ncurses/ncursesw/../../../contrib/ncurses/include 
> -I/usr/src/lib/ncurses/ncursesw/../../../contrib/ncurses/ncurses -Wall 
> -DNDEBUG 
> -DHAVE_CONFIG_H -DFREEBSD_NATIVE -DTERMIOS -std=gnu99 -fstack-protector  -c 
> /usr/src/lib/ncurses/ncursesw/../../../contrib/ncurses/ncurses/base/lib_bkgd.c
> cc -O2 -pipe  -D_XOPEN_SOURCE_EXTENDED -DENABLE_WIDEC -I. 
> -I/usr/obj/usr/src/lib/ncurses/ncursesw/../ncursesw 
> -I/usr/src/lib/ncurses/ncursesw/../ncursesw 
> -I/usr/src/lib/ncurses/ncursesw/../ncurses 
> -I/usr/src/lib/ncurses/ncursesw/../../../contrib/ncurses/include 
> -I/usr/src/lib/ncurses/ncursesw/../../../contrib/ncurses/ncurses -Wall 
> -DNDEBUG 
> -DHAVE_CONFIG_H -DFREEBSD_NATIVE -DTERMIOS -std=gnu99 -fstack-protector  -c 
> /usr/src/lib/ncurses/ncursesw/../../../contrib/ncurses/ncurses/base/lib_box.c
> cc -O2 -pipe  -D_XOPEN_SOURCE_EXTENDED -DENABLE_WIDEC -I. 
> -I/usr/obj/usr/src/lib/ncurses/ncursesw/../ncursesw 
> -I/usr/src/lib/ncurses/ncursesw/../ncursesw 
> -I/usr/src/lib/ncurses/ncursesw/../ncurses 
> -I/usr/src/lib/ncurses/ncursesw/../../../contrib/ncurses/include 
> -I/usr/src/lib/ncurses/ncursesw/../../../contrib/ncurses/ncurses -Wall 
> -DNDE^@^@^@^@^@^@^@
>
> this after about 30 minutes of running. There are no errors in the logs
>

First, look for *something* that would cause the machine to 
sleep/suspend/hibernate/shutdown after a period of "inactivity"

It _could_ be a BIOS setting, it could be 'power mangement' software
settings.

It is also -possible- that this is a *THERMAL* issue -- that the 30+
minutes of heavy CPU utilization is triggering an overtemperature 
shutdown.  Make sure all fans are working properly, and that CPU 
heat-sinks are dust-free.
___
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: Make buildworld don't run

[Bill Tillman]

From: Michael Powell 
To: freebsd-questions@freebsd.org
Sent: Wednesday, November 2, 2011 4:00 PM
Subject: Re: Make buildworld don't run


Zantgo wrote:

> I write "make buildworld", this is the answer:
> 
> #make buildworld
> make: don't know how to make buildworld. Stop

Since this works just fine for all those who have learned how to use FreeBSD 
I can only assume this indicates you do not know what you are doing.

> PS: I use FreeBSD 9.0 RC1, and I try to follow current

This is a poor choice for anyone new to FreeBSD. There are mainly 3 branches 
of FreeBSD to consider: -CURRENT is for developers and other contributors 
working on the next version of FreeBSD, -STABLE is somewhat in the middle in 
that it will have patches for problems that have been fixed in current and 
merged back to earlier release versions of code, and RELEASE. There is also 
a SECURITY branch where only security patches are updated to RELEASE.

Since it is obvious you do not know what you are doing the best place for 
you to begin is RELEASE. Install and begin using a RELEASE version as a 
learning tool. This means version 8.2! The Handbook may have pieces which 
are old and could stand updating, but largely it is _THE_ reference you 
should be working your way through as you proceed to learn FreeBSD. The 
greatest bulk of what you need to learn is in there. It comes in versions 
other than English too:

http://www.freebsd.org/doc/es_ES.ISO8859-1/books/handbook/index.html

If your only exposure to date with computers has been with Windows and you 
are looking to expand your reach, you will first find that the *Nix world is 
heavy on reading documentation and trying to figure stuff out for yourself 
first, before splattering help channels with every little thing that comes 
along. Once you have made some intial effort you will find that you are in a 
better position to provide better details on how we can help you. We cannot 
help you with the effort you need to make in learning the basics, and these 
basics are all contained in the documentation. 

I will make no effort to address your error. First of all, you should not be 
starting in FreeBSD with a release candidate and following -CURRENT. Your 
error is the result of trying to jump over learning what you need to know.

-Mike




___
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"


Is it just me or does someone need to choke this guy. We all had to start
somewhere and granted this guy's question was a newbie one, but please
get off your soapbox. It's amazing how you make no effort to help this
person yet you have the time to make alot of effort to ridicule. Your entire
response could have been as simple as:

cd /usr/src

I work with people all the time who complain that they have no time to
help you yet they have all the time in the world to send a lame e-mail 
complaining about how they have no time to help you.

Lighten up ... life is too short,
___
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: Make buildworld don't run

[Michael Powell]

Zantgo wrote:
 
> 
> El 02-11-2011, a las 17:00, Michael Powell 
> escribió:
> 
>> If your only exposure to date with computers has been with Windows and
>> you are looking to expand your reach, you will first find that the *Nix
>> world is heavy on reading documentation and trying to figure stuff out
>> for yourself first, before splattering help channels with every little
>> thing that comes along. Once you have made some intial effort you will
>> find that you are in a better position to provide better details on how
>> we can help you. We cannot help you with the effort you need to make in
>> learning the basics, and these basics are all contained in the
>> documentation.
>> 
>> I will make no effort to address your error. First of all, you should not
>> be starting in FreeBSD with a release candidate and following -CURRENT.
>> Your error is the result of trying to jump over learning what you need to
>> know
> 
> Now this worked for me and at one time thought to hold steady, but I
> thought that opened many dependencies, and need more current packages so
> take care not release

Nope. Make buildworld is how you begin a source-based upgrade to the 
operating system. This is completely different and separate from anything 
package related. You are completely on the wrong track with this. Study the 
Handbook some more and this may become apparent.

When you refresh your ports tree (which handles dependency tracking whether 
you are installing from ports or using packages) you will always be looking 
at the latest ports/packages. This is true no matter which branch of the OS 
you are using. Install RELEASE, refresh your ports tree, and you will still 
have all the 'most current packages'. You do *NOT* need to be running -
CURRENT in order to have the 'most current packages'!

This still reiterates the need for you to read and study the documentation. 
All of this information is present in the documentation.

-Mike



___
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: Make buildworld don't run

[Zantgo]

El 02-11-2011, a las 17:00, Michael Powell  escribió:

> If your only exposure to date with computers has been with Windows and you 
> are looking to expand your reach, you will first find that the *Nix world is 
> heavy on reading documentation and trying to figure stuff out for yourself 
> first, before splattering help channels with every little thing that comes 
> along. Once you have made some intial effort you will find that you are in a 
> better position to provide better details on how we can help you. We cannot 
> help you with the effort you need to make in learning the basics, and these 
> basics are all contained in the documentation. 
> 
> I will make no effort to address your error. First of all, you should not be 
> starting in FreeBSD with a release candidate and following -CURRENT. Your 
> error is the result of trying to jump over learning what you need to know

Now this worked for me and at one time thought to hold steady, but I thought 
that opened many dependencies, and need more current packages so take care not 
release

___
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: Make buildworld don't run

[Michael Powell]

Zantgo wrote:

> I write "make buildworld", this is the answer:
> 
> #make buildworld
> make: don't know how to make buildworld. Stop

Since this works just fine for all those who have learned how to use FreeBSD 
I can only assume this indicates you do not know what you are doing.
 
> PS: I use FreeBSD 9.0 RC1, and I try to follow current

This is a poor choice for anyone new to FreeBSD. There are mainly 3 branches 
of FreeBSD to consider: -CURRENT is for developers and other contributors 
working on the next version of FreeBSD, -STABLE is somewhat in the middle in 
that it will have patches for problems that have been fixed in current and 
merged back to earlier release versions of code, and RELEASE. There is also 
a SECURITY branch where only security patches are updated to RELEASE.

Since it is obvious you do not know what you are doing the best place for 
you to begin is RELEASE. Install and begin using a RELEASE version as a 
learning tool. This means version 8.2! The Handbook may have pieces which 
are old and could stand updating, but largely it is _THE_ reference you 
should be working your way through as you proceed to learn FreeBSD. The 
greatest bulk of what you need to learn is in there. It comes in versions 
other than English too:

http://www.freebsd.org/doc/es_ES.ISO8859-1/books/handbook/index.html

If your only exposure to date with computers has been with Windows and you 
are looking to expand your reach, you will first find that the *Nix world is 
heavy on reading documentation and trying to figure stuff out for yourself 
first, before splattering help channels with every little thing that comes 
along. Once you have made some intial effort you will find that you are in a 
better position to provide better details on how we can help you. We cannot 
help you with the effort you need to make in learning the basics, and these 
basics are all contained in the documentation. 

I will make no effort to address your error. First of all, you should not be 
starting in FreeBSD with a release candidate and following -CURRENT. Your 
error is the result of trying to jump over learning what you need to know.

-Mike




___
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: Make buildworld don't run

[Zantgo]

El 02-11-2011, a las 16:33, Jerry McAllister  escribió:

> On Wed, Nov 02, 2011 at 03:45:39PM -0300, Zantgo wrote:
> 
>> I write "make buildworld", this is the answer:
>> 
>> #make buildworld
>> make: don't know how to make buildworld. Stop
>> 
>> PS: I use FreeBSD 9.0 RC1, and I try to follow current
> 
> What user/permissions did you have?
> Which directory were you in?
> 
> I think you need to be root and in /usr/src
> 
> I could be wrong.
> 
> jerry

Yeah!!, I just had to be in / usr / src, thank you very much!.

PS: as the directory name that comes after typing "cd" as root or user?
> 
>> 
>> Zantgo
>> ___
>> 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: Make buildworld don't run

[Jerry McAllister]

On Wed, Nov 02, 2011 at 03:45:39PM -0300, Zantgo wrote:

> I write "make buildworld", this is the answer:
> 
> #make buildworld
> make: don't know how to make buildworld. Stop
> 
> PS: I use FreeBSD 9.0 RC1, and I try to follow current

What user/permissions did you have?
Which directory were you in?

I think you need to be root and in /usr/src

I could be wrong.

jerry

> 
> Zantgo
> ___
> 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: Make buildworld don't run

[Adam Vande More]

On Wed, Nov 2, 2011 at 1:45 PM, Zantgo  wrote:

> I write "make buildworld", this is the answer:
>
> #make buildworld
> make: don't know how to make buildworld. Stop
>

http://www.freebsd.org/doc/handbook/makeworld.html

-- 
Adam Vande More
___
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: make buildworld errors

[Magnus Sandberg]

Hi,

Can it be related to an issue from 2009? I have the same problem when 
compiling with WITHOUT_KVM and WITH_INET6 (implicit as WITHOUT_INET6 is not 
defined).

See the folling links
http://lists.freebsd.org/pipermail/freebsd-current/2009-November/013020.html
http://lists.freebsd.org/pipermail/freebsd-current/attachments/20091101/4084
8244/ifmcstat.obj

Regards,

// Mem



 - On 1st of January 2011 Manolis Kiagias wrote: -

Subject: Re: make buildworld errors
From: Manolis Kiagias
Date: Sat, 01 Jan 2011 00:35:37 -0800

On 01/01/2011 9:54 ?.?., Mike wrote:
>
> Trying to buildworld but it keeps failing. I finally deleted /usr/src
> and recopyed from a cd then cvsup using standard-supfile. Tried
> limiting how much ram freebsd uses and only using one stick of ram.
> All attempts have failed at the same place.  Would using the GENERIC
> kernel make a difference?
>

You shouldn't have any trouble building world using a custom kernel.
Try rm -rf /usr/obj/* before starting the build. This usually solves th


___
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: make buildworld errors

[Manolis Kiagias]

On 01/01/2011 9:54 ?.?., Mike wrote:
>
> Trying to buildworld but it keeps failing. I finally deleted /usr/src
> and recopyed from a cd then cvsup using standard-supfile. Tried
> limiting how much ram freebsd uses and only using one stick of ram.
> All attempts have failed at the same place.  Would using the GENERIC
> kernel make a difference?
>

You shouldn't have any trouble building world using a custom kernel.
Try rm -rf /usr/obj/* before starting the build. This usually solves th
___
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: make buildworld runs out of space

[Giorgos Keramidas]

On Wed, 17 Mar 2010 17:38:06 -0700 (PDT), Bill Tillman  
wrote:
> I have built two machines with 8.0-STABLE-201002-amd64. When I updated
> the sources and ran make buildworld process it would fail claiming
> that / was full.
>
> It seems to be running into the problem when the make installkernel
> portion of my script was running. Both machines were built using the
> default of 512M for /. I rebuilt the machines with 1G / and all was
> well. But one shouldn't have to do this as 512M for / should be
> adequate.

Yes it's adequate for *one* kernel.  But it's often too limited for a
couple of kernels (e.g. /boot/kernel.old and /boot/kernel).

My /boot has two kernels now, and they are build with debugging symbols
so they take a bit more space, but the following is a sample du run:

$ du -hsx /boot/kernel* /boot
136M/boot/kernel
136M/boot/kernel.old
273M/boot
$

With 273 MB for kernels, there has to be adequate space for the *rest*
of the root filesystem files too.  With 512 MB you are very close to
having "just enough" space, but it's not certain if e.g. your /tmp
already contains a few dozen MB of temporary files.

As you found out, 1 GB of root filesystem space is ok for now :-)

___
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: make buildworld runs out of space

[Jason Garrett]

On Wed, Mar 17, 2010 at 20:08, Polytropon  wrote:
> On Wed, 17 Mar 2010 17:38:06 -0700 (PDT), Bill Tillman  
> wrote:
>> I rebuilt the machines with 1G / and all was well. But one
>> shouldn't have to do this as 512M for / should be adequate.
>
> It's not only the new kernel - a backup of the previous
> existing kernel is kept in /boot (and so on /). If you
> suppress this, all should be fine, but maybe dangerous
> in case your new kernel doesn't boot as intended.
>
> In this case, the subject "make buildworld runs out of
> space" may lead to a misunderstanding; according to what
> you stated, "make installkernel" was the operation
> causing the out of space problem.
>
>
>
> --
> Polytropon
> Magdeburg, Germany
> Happy FreeBSD user since 4.0
> Andra moi ennepe, Mousa, ...
> ___
> 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"
>

Just a note, the default 512mb is never enough room, especially since
hard drive space is negligible these days.

I always use 4G for /
___
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: make buildworld runs out of space

[Polytropon]

On Wed, 17 Mar 2010 17:38:06 -0700 (PDT), Bill Tillman  
wrote:
> I rebuilt the machines with 1G / and all was well. But one
> shouldn't have to do this as 512M for / should be adequate.

It's not only the new kernel - a backup of the previous
existing kernel is kept in /boot (and so on /). If you
suppress this, all should be fine, but maybe dangerous
in case your new kernel doesn't boot as intended.

In this case, the subject "make buildworld runs out of
space" may lead to a misunderstanding; according to what
you stated, "make installkernel" was the operation
causing the out of space problem.



-- 
Polytropon
Magdeburg, Germany
Happy FreeBSD user since 4.0
Andra moi ennepe, Mousa, ...
___
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: Make buildworld

[Josh Carroll]

> I did some testing, at least for me, I get the most improvements when the 
> number
> of cores or processors equals the -j number.  You can make it higher, even
> double it, withoout hurting things, but 95% of the improvements come from
> matching the number of processes to the number of available CPUs (and that' by
> my own testing, not theory).

I've found that on my Q6600 (quad core) system, the optimal is 8
though the improvements after 5 were minimal. It depends if the jobs
are I/O bound or not and the scheduler. Although even with ffmpeg, the
optimal number of threads with this quad core system is 8. On my
previous system with a dual-core chip with the same hardware, the
"magic number" was 4 (again, 2x the number of cores). This was with
the ULE scheduler, I'm not sure if the same holds true for the 4BSD
scheduler or not.

And as you said, it's important to use make without -j if the build
fails before reporting bugs, since there are no guarantees that world
will build properly with multiple jobs.

Josh
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: Make buildworld

[Chuck Robey]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Brian wrote:
> Jos Chrispijn wrote:
>> Can someone tell me the difference between 'make -j2 buildworld' and
>> 'make -j4 buildworld' ?
>>
>> Thanks,
>> Jos
>> ___
>> freebsd-questions@freebsd.org mailing list
>> http://lists.freebsd.org/mailman/listinfo/freebsd-questions
>> To unsubscribe, send any mail to
>> "[EMAIL PROTECTED]"
> fyi, the below is from /usr/src/UPDATING:
> 
> COMMON ITEMS:
> 
>General Notes
>-
>Avoid using make -j when upgrading.  From time to time in the
>past there have been problems using -j with buildworld and/or
>installworld.  This is especially true when upgrading between
>"distant" versions (eg one that cross a major release boundary
>or several minor releases, or when several months have passed
>on the -current branch).

I really don't think that's a fault of make(1), it's a fault of the Makefiles,
which have to be written very carefully so that having multiple parallel
processes going might screw up building.  Yes, it has done that in the past, but
it's an occaisonal thing, not a regular thing, because there's a good number of
folks who build there kernels with something like -j4.  I often do.  One just
has to be really awake when you hit a problem, or when reporting a build
error... rebuild without the -jN.

I did some testing, at least for me, I get the most improvements when the number
of cores or processors equals the -j number.  You can make it higher, even
double it, withoout hurting things, but 95% of the improvements come from
matching the number of processes to the number of available CPUs (and that' by
my own testing, not theory).

Still, if you aren't willing to do your won troubleshooting, best to avoid using
- -j anything.  It's very  easy to screw up.
-BEGIN PGP SIGNATURE-
Version: GnuPG v2.0.4 (FreeBSD)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFITI8Uz62J6PPcoOkRAvc0AKCihT7rT4VrDI/6ve1BXfWjXwrsHgCdE4qr
F1uwEvIAQt8qNrQADQZbkvI=
=g9B0
-END PGP SIGNATURE-
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: Make buildworld

[Brian]

Jos Chrispijn wrote:
Can someone tell me the difference between 'make -j2 buildworld' and 
'make -j4 buildworld' ?


Thanks,
Jos
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to 
"[EMAIL PROTECTED]"

fyi, the below is from /usr/src/UPDATING:

COMMON ITEMS:

   General Notes
   -
   Avoid using make -j when upgrading.  From time to time in the
   past there have been problems using -j with buildworld and/or
   installworld.  This is especially true when upgrading between
   "distant" versions (eg one that cross a major release boundary
   or several minor releases, or when several months have passed
   on the -current branch).
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

RE: Make buildworld

[Tobias Hoellrich]

$ man make
...
-j max_jobs
  Specify the maximum number of jobs that make may have running at
  any one time.  Turns compatibility mode off, unless the -B flag
  is also specified. 

HTH - Tobias

> -Original Message-
> From: [EMAIL PROTECTED] 
> [mailto:[EMAIL PROTECTED] On Behalf Of Jos 
> Chrispijn
> Sent: Sunday, June 08, 2008 7:50 AM
> To: freebsd-questions@freebsd.org
> Subject: Make buildworld
> 
> Can someone tell me the difference between 'make -j2 buildworld' and 
> 'make -j4 buildworld' ?
> 
> Thanks,
> Jos
> ___
> freebsd-questions@freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-questions
> To unsubscribe, send any mail to 
> "[EMAIL PROTECTED]"
> 
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: make buildworld

[Josh Carroll]

On Sun, May 4, 2008 at 10:03 AM, Aguiar Magalhaes <[EMAIL PROTECTED]> wrote:
> Hi list,
>
>  How can i fix the error below ?
>
>  Thanks,
>
>  Aguiar
>
>
>  # make buildworld
>
>  - - - - - - - - - - - - - - - - - - - - -
>  cc -O2 -fno-strict-aliasing -pipe  -I/usr/src/lib/libc/include 
> -I/usr/src/lib/li
>  bc/../../include -I/usr/src/lib/libc/i386 -D__DBINTERFACE_PRIVATE 
> -I/usr/src/lib
>  /libc/../../contrib/gdtoa -DINET6 -I/usr/obj/usr/src/lib/libc 
> -I/usr/src/lib/lib
>  c/resolv -DPOSIX_MISTAKE -I/usr/src/lib/libc/locale -DBROKEN_DES -DPORTMAP 
> -DDES
>  _BUILTIN -I/usr/src/lib/libc/rpc -DYP -DNS_CACHING -DSYMBOL_VERSIONING 
> -Wsystem-
>  headers -Wall -Wno-format-y2k -Wno-uninitialized -Wno-pointer-sign -c 
> /usr/src/l
>  ib/libc/stdlib/strtoul.c
>  In file included from /usr/src/lib/libc/stdlib/strtoul.c:39:
>  /usr/src/lib/libc/../../include/stdlib.h:98: internal compiler error: 
> Segmentati
>  on fault: 11

Typically, a segfault from gcc indicates failing hardware, the most
likely culprit being the RAM. Test the RAM with memtest86
(http://memtest86.com/download.html) to rule it out.

Josh
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: make buildworld 6.x on 7.x?

[Rakhesh Sasidharan]

Kris Kennaway wrote:


Rakhesh Sasidharan wrote:

Hi,

Is it possible to do a ''make buildworld buildkernel'' of the FreeBSD 6.x 
series sources on a FreeBSD 7.x machine and then install them onto a 
FreeBSD 6.x machine?


Yes, I did this a few minutes ago in fact :)  No special procedures are 
necessary, world builds are already suitably isolated from the host system 
for this to work.


Awesome! Infact, I didn't think it would be possible. Like you have 
separate port packages for the 6.x and 7.x trees, I thought FreeBSD 6.x 
compiled on a FreeBSD 7.x system won't run. But I was obviously wrong. 
Guess its different for the base OS eh ...?


Going by the same logic, is it possible that tomm I can download the 
sources for an OS like say, NetBSD, buildworld for it on my FreeBSD 
machine, and then install on a NetBSD machine?


Thanks,
Rakhesh

---
http://rakhesh.net/
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: make buildworld 6.x on 7.x?

[Kris Kennaway]

Rakhesh Sasidharan wrote:

Hi,

Is it possible to do a ''make buildworld buildkernel'' of the FreeBSD 
6.x series sources on a FreeBSD 7.x machine and then install them onto a 
FreeBSD 6.x machine?


Yes, I did this a few minutes ago in fact :)  No special procedures are 
necessary, world builds are already suitably isolated from the host 
system for this to work.


Kris

___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: make buildworld fails

[Philip M. Gollucci]

Jamie Avery wrote:
> put KERNCONF=/kernelname/ into /etc/make.conf.  However, when I make
> buildkernel, I get the following error
7.x+ src.conf, below make.conf

grep KERNCONF /etc/make.conf /etc/src.conf
/etc/src.conf:KERNCONF?=  RIDERWAY

NO /s neccessary.



-- 

Philip M. Gollucci ([EMAIL PROTECTED])
o:703.549.2050x206
Senior System Admin - Riderway, Inc.
http://riderway.com / http://ridecharge.com
1024D/EC88A0BF 0DE5 C55C 6BF3 B235 2DAB  B89E 1324 9B4F EC88 A0BF

Work like you don't need the money,
love like you'll never get hurt,
and dance like nobody's watching.

___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: make buildworld (6-STABLE) -> stop in /usr/src/gnu/usr.bin/gdb/gdbserver

[Venkatesh K]

Hi,

I think you did not see an earlier thread started by me started by me.
I am also facing similar problem and you will find more details if you
go through the thread. It seems gdb Makefile is the culprit.

Right now I have commented out build of gdbserver and "buildworld" is
running. Let's wait and see if someone fixes this in source tree.

Thanks,

Venkatesh K

On Dec 4, 2007 10:35 PM, Ewald Jenisch <[EMAIL PROTECTED]> wrote:
> Hi,
>
> After cvsup-ing one of my 6-STABLE machines, cleaning up /usr/obj I
> started the usual build process with "make buildworld". However after
> some minutes it died with the following messages:
>
> ===> gnu/usr.bin/gdb/kgdb (cleandir)
> rm -f i386fbsd-tdep-fixed.c nm.h tm.h xm.h kgdb main.o kthr.o trgt.o 
> trgt_i386.o kgdb.1.gz kgdb.1.cat.gz
> rm -f .depend GPATH GRTAGS GSYMS GTAGS
> ===> gnu/usr.bin/gdb/gdbserver (cleandir)
> cd: can't cd to /usr/src/gnu/usr.bin/gdb/gdbserver
> *** Error code 2
>
> Stop in /usr/src/gnu/usr.bin/gdb.
> *** Error code 1
>
> Stop in /usr/src/gnu/usr.bin.
> *** Error code 1
>
> Stop in /usr/src/gnu.
> *** Error code 1
>
> Stop in /usr/src.
> *** Error code 1
>
> Stop in /usr/src.
> *** Error code 1
>
> Stop in /usr/src.
>
>
> In order to completely start from scratch I removed /usr/src/*,
> /usr/obj/*, cvsup-ed again some hours later but again make buildworld
> ended with the same error.
>
> Has anybody else seen this error?
>
> TIA for any clue,
> -ewald
>
>
> ___
> freebsd-questions@freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-questions
> To unsubscribe, send any mail to "[EMAIL PROTECTED]"
>



-- 
Venkatesh. K
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: make buildworld ....gcc bug

[Dag-Erling Smørgrav]

James <[EMAIL PROTECTED]> writes:
> On Wed, 2007-11-07 at 23:01 +0200, tethys ocean wrote:
>> When I am rebuilding world  FreeBSD 6.2 I have take error that is
>> shown below. What can I do!?
> The current version of gcc for FreeBSD is 4.2.

Not in RELENG_6.

DES
-- 
Dag-Erling Smørgrav - [EMAIL PROTECTED]
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: make buildworld ....gcc bug

[RW]

On Wed, 07 Nov 2007 14:42:58 -0700
James <[EMAIL PROTECTED]> wrote:

> On Wed, 2007-11-07 at 23:01 +0200, tethys ocean wrote:
> 
> > When I am rebuilding world  FreeBSD 6.2 I have take error that is
> > shown below. What can I do!?
> > 
> > [EMAIL PROTECTED] /usr/src]#  make buildworld
> > 
> > 
> > [EMAIL PROTECTED] gcc -v
> > Using built-in specs.
> > Configured with: FreeBSD/i386 system compiler
> > Thread model: posix
> > gcc version 3.4.6 [FreeBSD] 20060305
> 
> The current version of gcc for FreeBSD is 4.2. Sync your ports tree,
> follow the advice in UPDATING and update, and try again.


That has no relevance to a buildworld. gcc 3.4.6 is the correct version
for FreeBSD 6.2.
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: make buildworld ....gcc bug

[Roland Smith]

On Wed, Nov 07, 2007 at 11:01:21PM +0200, tethys ocean wrote:
> When I am rebuilding world  FreeBSD 6.2 I have take error that is
> shown below. What can I do!?
> 
> [EMAIL PROTECTED] /usr/src]#  make buildworld

> In function `yylex':
> /usr/src/gnu/usr.bin/binutils/ld/../../../../contrib/binutils/ld/ldlex.l:579:
> internal compiler error: Segmentation fault: 11

Check your hardware, especially your memory. See http://www.bitwizard.nl/sig11/

Roland
-- 
R.F.Smith   http://www.xs4all.nl/~rsmith/
[plain text _non-HTML_ PGP/GnuPG encrypted/signed email much appreciated]
pgp: 1A2B 477F 9970 BA3C 2914  B7CE 1277 EFB0 C321 A725 (KeyID: C321A725)


pgpyz076I8bDV.pgp
Description: PGP signature

Re: make buildworld ....gcc bug

[James]

On Wed, 2007-11-07 at 23:01 +0200, tethys ocean wrote:

> When I am rebuilding world  FreeBSD 6.2 I have take error that is
> shown below. What can I do!?
> 
> [EMAIL PROTECTED] /usr/src]#  make buildworld
> 
> 
> [EMAIL PROTECTED] gcc -v
> Using built-in specs.
> Configured with: FreeBSD/i386 system compiler
> Thread model: posix
> gcc version 3.4.6 [FreeBSD] 20060305

The current version of gcc for FreeBSD is 4.2. Sync your ports tree,
follow the advice in UPDATING and update, and try again.

If you're using pkg_add, sub in the appropriate commands.

James



> [EMAIL PROTECTED]
> 
> 
> /usr/src/gnu/usr.bin/binutils/ld/../../../../contrib/binutils/ld/ldemul.h:155:
> warning: "struct option" declared inside parameter list
> cc -O2 -fno-strict-aliasing -pipe -I.
> -I/usr/src/gnu/usr.bin/binutils/ld -I/usr/src
> /gnu/usr.bin/binutils/ld/../libbfd
> -I/usr/obj/usr/src/tmp/usr/src/gnu/usr.bin/binut
> ils/ld/../libbfd
> -I/usr/src/gnu/usr.bin/binutils/ld/../../../../contrib/binutils/in
> clude -DTARGET=\"i386-obrien-freebsd\"
> -DDEFAULT_EMULATION=\"elf_i386_fbsd\" -DSCRI
> PTDIR=\"/usr/obj/usr/src/tmp/usr/libdata\"
> -DBFD_VERSION_STRING=\""2.15 [FreeBSD] 2
> 004-05-23"\" -DBINDIR=\"/usr/bin\"
> -DTARGET_SYSTEM_ROOT=\"/usr/obj/usr/src/tmp\" -D
> TOOLBINDIR=\"/usr/obj/usr/src/tmp//usr/bin/libexec\" -D_GNU_SOURCE
> -I/usr/src/gnu/u
> sr.bin/binutils/ld/../../../../contrib/binutils/ld
> -I/usr/src/gnu/usr.bin/binutils/
> ld/../../../../contrib/binutils/bfd
> -I/usr/obj/usr/src/tmp/legacy/usr/include -c ldlex.c
> /usr/src/gnu/usr.bin/binutils/ld/../../../../contrib/binutils/ld/ldlex.l:
> In function `yylex':
> /usr/src/gnu/usr.bin/binutils/ld/../../../../contrib/binutils/ld/ldlex.l:579:
> internal compiler error: Segmentation fault: 11
> Please submit a full bug report,
> with preprocessed source if appropriate.
> See http://gcc.gnu.org/bugs.html> for instructions.
> *** Error code 1
> 
> Stop in /usr/src/gnu/usr.bin/binutils/ld.
> *** Error code 1
> 
> Stop in /usr/src/gnu/usr.bin/binutils.
> *** Error code 1
> 
> Stop in /usr/src.
> *** Error code 1
> 
> Stop in /usr/src.
> *** Error code 1
> 
> Stop in /usr/src.
> [EMAIL PROTECTED] /usr/src]#
> ___
> [EMAIL PROTECTED] mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-current
> To unsubscribe, send any mail to "[EMAIL PROTECTED]"
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: make buildworld fails on 6.2-STABLE

[JD Bronson]

At 08:19 PM 7/27/2007 +1200, Jonathan Chen wrote:

On Thu, Jul 26, 2007 at 11:12:26AM -0500, J.D. Bronson wrote:
> so I deleted /usr/src
> redownloaded from a different mirror and tried
> make buildworld again...
>
> It still failed -but this time at a different point:

Standard behaviour of failing hardware - most likely memory.


yes. I removed/cleaned/replaced the RAM and it built.
Not sure if the issue will return or not :)

-JD  


___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: make buildworld fails on 6.2-STABLE

[Jonathan Chen]

On Thu, Jul 26, 2007 at 11:12:26AM -0500, J.D. Bronson wrote:
> so I deleted /usr/src
> redownloaded from a different mirror and tried
> make buildworld again...
> 
> It still failed -but this time at a different point:

Standard behaviour of failing hardware - most likely memory.
-- 
Jonathan Chen <[EMAIL PROTECTED]>
--
  Experience is a hard teacher
   because she gives the test first, the lesson afterwards
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: make buildworld fails on 6.2-STABLE

[J.D. Bronson]

so I deleted /usr/src
redownloaded from a different mirror and tried
make buildworld again...

It still failed -but this time at a different point:


mkdep -f .depend -a-DIN_GCC -DHAVE_CONFIG_H -DPREFIX=\"/usr\" 
-I/usr/obj/usr/src/gnu/usr.bin/cc/cc/../cc_tools 
-I/usr/src/gnu/usr.bin/cc/cc/../cc_tools 
-I/usr/src/gnu/usr.bin/cc/cc/../../../../contrib/gcc 
-I/usr/src/gnu/usr.bin/cc/cc/../../../../contrib/gcc/config 
-DDEFAULT_TARGET_VERSION=\"3.4.6\" -DDEFAULT_TARGET_MACHINE=\"\" 
/usr/src/gnu/usr.bin/cc/cc/../../../../contrib/gcc/gcc.c 
/usr/src/gnu/usr.bin/cc/cc/../../../../contrib/gcc/gccspec.c
echo cc: /usr/obj/usr/src/tmp/usr/lib/libc.a 
/usr/obj/usr/src/gnu/usr.bin/cc/cc/../cc_int/libcc_int.a >> .depend

===> gnu/usr.bin/cc/cc1 (depend)
sed -e "/^@@ifobjc.*/,/^@@end_ifobjc.*/d"  -e "/^@@ifc.*/d" -e 
"/^@@end_ifc.*/d" 
/usr/src/gnu/usr.bin/cc/cc1/../../../../contrib/gcc/c-parse.in > c-parse.y

yacc -d c-parse.y
yacc: e - line 1811 of "c-parse.y", syntax error
{ if ($1 == error_}ark_node)
   ^
*** Error code 1

Stop in /usr/src/gnu/usr.bin/cc/cc1.
*** Error code 1

___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: make buildworld fails on 6.2-STABLE

[J.D. Bronson]

At 09:16 AM 07/26/2007, Heiko Wundram (Beenic) wrote:

Am Donnerstag 26 Juli 2007 15:54:36 schrieb J.D. Bronson:
> internal compiler error: Segmentation fault: 11
> Please submit a full bug report,
> with preprocessed source if appropriate.
> See http://gcc.gnu.org/bugs.html> for instructions.

Most probably a (physical) memory error.

As the message says, this has pretty much nothing to do with the upping of
world, but is an "internal" compiler error, which I've only seen on
development snapshots of gcc (improbable that these are distributed with
STABLE), or flaky memory (which is much more likely the cause).

--


thanks - ironically I have never had ANY issue building world on this 
machine until today. I have deleted /usr/src and re cvs'd from a diff 
mirror as a test.


-JD 


___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: make buildworld fails on 6.2-STABLE

[Heiko Wundram (Beenic)]

Am Donnerstag 26 Juli 2007 15:54:36 schrieb J.D. Bronson:
> internal compiler error: Segmentation fault: 11
> Please submit a full bug report,
> with preprocessed source if appropriate.
> See http://gcc.gnu.org/bugs.html> for instructions.

Most probably a (physical) memory error.

As the message says, this has pretty much nothing to do with the upping of 
world, but is an "internal" compiler error, which I've only seen on 
development snapshots of gcc (improbable that these are distributed with 
STABLE), or flaky memory (which is much more likely the cause).

-- 
Heiko Wundram
Product & Application Development
-
Office Germany - EXPO PARK HANNOVER
 
Beenic Networks GmbH
Mailänder Straße 2
30539 Hannover
 
Fon+49 511 / 590 935 - 15
Fax+49 511 / 590 935 - 29
Mail   [EMAIL PROTECTED]


Beenic Networks GmbH
-
Sitz der Gesellschaft: Hannover
Geschäftsführer: Jorge Delgado
Registernummer: HRB 61869
Registergericht: Amtsgericht Hannover
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: make Buildworld fails...why?

[Josh Paetzel]

Mark Stout wrote:
> Hello,
> 
> I've been trying to upgrade a 5.4-RELEASE to 6.2-RELEASE and having a bit of
> a problem.
> 
> Downloaded and untar's the source files for base, catpages, dict, doc,
> games, info, manpages, proflibs, and src directories per INSTALL.TXT in the
> releases/.../src directory after backing up my local /etc and /usr/local/etc
> directories.
> 
> I've tweaked the GENERIC kernel config file and renamed is RADIUS2
> 
> While in /usr/src I did a 'make buildworld'.
> 
>   I do okay until I get to "stage 2.3: build tools".  There I get to the
> following error when compiling make_hash.  Can anyone help me determine why
> this is failing?  Were my upgrade procedures
> 
> Thank you,
> Mark Stout
> VPM Global Internet Services, Inc.
> 530-626-4218 x205 Office
> 530-626-7182 Fax
> 530-554-9295 VoIP
> 916-240-2850 Cell
> www.vpm.com

Generally speaking the best supported upgrade path across major
version numbers is from the last release of the older version to the
first of the newer, which in your case would mean upgrading from 5.4
-> 5.5 -> 6.0 -> 6.2

Is there any particular reason you aren't using cvsup/csup to update
your source tree?

-- 
Thanks,

Josh Paetzel
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: make buildworld error

[Giorgos Keramidas]

On 2007-03-20 00:21, Dino Vliet <[EMAIL PROTECTED]> wrote:
> Hi folks,
> 
> on my pc ,
> 
> CPU: VIA C3 Samuel 2 (796.10-MHz 686-class CPU)
>   Origin = "CentaurHauls"  Id = 0x673  Stepping = 3
>   Features=0x803035
> real memory  = 503250944 (479 MB)
> avail memory = 483028992 (460 MB)
> 
> I get the following error after I issue a make buildworld:
> 
> ===> sbin/geom/class/eli (all)
> cc -fpic -DPIC -O2 -fno-strict-aliasing -pipe  
> -I/usr/src/sbin/geom/class/eli/../../../../sys 
> -I/usr/src/sbin/geom/class/eli/../.. -Wsystem-headers -Werror -Wall 
> -Wno-format-y2k -W -Wno-unused-parameter -Wstrict-prototypes 
> -Wmissing-prototypes -Wpointer-arith -Wno-uninitialized -c 
> /usr/src/sbin/geom/class/eli/../../../../sys/geom/eli/g_eli_crypto.c -o 
> g_eli_crypto.So
> cc -fpic -DPIC -O2 -fno-strict-aliasing -pipe  
> -I/usr/src/sbin/geom/class/eli/../../../../sys 
> -I/usr/src/sbin/geom/class/eli/../.. -Wsystem-headers -Werror -Wall 
> -Wno-format-y2k -W -Wno-unused-parameter -Wstrict-prototypes 
> -Wmissing-prototypes -Wpointer-arith -Wno-uninitialized -c 
> /usr/src/sbin/geom/class/eli/../../../../sys/geom/eli/g_eli_key.c -o 
> g_eli_key.So
> cc -fpic -DPIC -O2 -fno-strict-aliasing -pipe  
> -I/usr/src/sbin/geom/class/eli/../../../../sys 
> -I/usr/src/sbin/geom/class/eli/../.. -Wsystem-headers -Werror -Wall 
> -Wno-format-y2k -W -Wno-unused-parameter -Wstrict-prototypes 
> -Wmissing-prototypes -Wpointer-arith -Wno-uninitialized -c 
> /usr/src/sbin/geom/class/eli/../../../../sys/geom/eli/pkcs5v2.c -o pkcs5v2.So
> cc -fpic -DPIC -O2 -fno-strict-aliasing -pipe  
> -I/usr/src/sbin/geom/class/eli/../../../../sys 
> -I/usr/src/sbin/geom/class/eli/../.. -Wsystem-headers -Werror -Wall 
> -Wno-format-y2k -W -Wno-unused-parameter -Wstrict-prototypes 
> -Wmissing-prototypes -Wpointer-arith -Wno-uninitialized -c 
> /usr/src/sbin/geom/class/eli/../../../../sys/crypto/sha2/sha2.c -o sha2.So
> /usr/src/sbin/geom/class/eli/../../../../sys/crypto/sha2/sha2.c:641: error: 
> syntax error before '*' token
> /usr/src/sbin/geom/class/eli/../../../../sys/crypto/sha2/sha2.c:644: error: 
> syntax error before '&' token
> /usr/src/sbin/geom/class/eli/../../../../sys/crypto/sha2/sha2.c:645: error: 
> syntax error before '&' token
> /usr/src/sbin/geom/class/eli/../../../../sys/crypto/sha2/sha2.c:645: warning: 
> type defaults to `int' in declaration of `context'
> /usr/src/sbin/geom/class/eli/../../../../sys/crypto/sha2/sha2.c:645: warning: 
> type defaults to `int' in declaration of `data'
> /usr/src/sbin/geom/class/eli/../../../../sys/crypto/sha2/sha2.c:645: error: 
> syntax error before ')' token
> *** Error code 1

Which version of the FreeBSD src/ tree are you building?

How are you updating your /usr/src tree?

If you are using CVSup, it is possible thatyou were "lucky" enough to
run CVSup and caught a commit "half updated".  Can you try re-running
CVSup and see if this updates the relevant bits to a buildable state?

- Giorgos

___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

RE: Make buildworld fail due to sendmail/sasl installation.

[Jesse Geddis]

Well my last copying the header files all over the place apparently helped
because now I'm down to the linker not being able to find the libraries.
Suggestions?

===> libexec/mail.local
cc -O -pipe  -I/usr/src/libexec/mail.local/../../contrib/sendmail/include
-I. -I/usr/local/include/sasl -DSASL=2  -c
/usr/src/libexec/mail.local/../../contrib/sendmail/mail.local/mail.local.c
cc -O -pipe  -I/usr/src/libexec/mail.local/../../contrib/sendmail/include
-I. -I/usr/local/include/sasl -DSASL=2   -L/usr/local/lib/sasl2 -o
mail.local mail.local.o
/usr/obj/usr/src/libexec/mail.local/../../lib/libsm/libsm.a -lsasl2
/usr/obj/usr/src/sparc64/usr/bin/ld: cannot find -lsasl2
*** Error code 1

Stop in /usr/src/libexec/mail.local.
*** Error code 1

Stop in /usr/src/libexec.
*** Error code 1

Stop in /usr/src.
*** Error code 1

Stop in /usr/src.
*** Error code 1

-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Jesse Geddis
Sent: Sunday, October 08, 2006 4:36 PM
To: freebsd-questions@freebsd.org
Subject: Make buildworld fail due to sendmail/sasl installation.

Ever since I installed the package sendmail+tls+sasl2-8.13.8 I
haven't been able to make buildworld on my system. I get file not found
errors for some sasl header files. I'll attach the pertinent portion of the
failure below. Seems simple enough, however, I haven't been able to get
around it. It calls for the sasl files in the correct directory
ns1:/usr/local/include/sasl# ls
hmac-md5.h  md5global.h sasl.h  saslutil.h
md5.h   prop.h  saslplug.h
The files are there. Still nothing. I've tried copying them to various
places to get around it to no avail
/usr/src/contrib/sendmail/src
/usr/src/contrib/sendmail/src/sasl
/usr/src/contrib/sendmail/libmilter
/usr/src/contrib/sendmail/libmilter/sasl
/usr/local/include

Not sure what to do with this, seems to me it would probably make things
easier on a lot of folks if sendmail was treated similar to how perl is on
freebsd these days, where it isn't integral. Not using the integral sendmail
has been a bit of a nightmare. Thanks so much for any help

Jesse

mkdep -f .depend -a-I/usr/src/lib/libmilter/../../contrib/sendmail/src
-I/usr/src/lib/libmilter/../../contrib/sendmail/include -I. -DNOT_SENDMAIL
-Dsm_snprintf=snprintf -D_THREAD_SAFE -DNETINET6 -I/usr/local/include/sasl
-DSASL=2 /usr/src/lib/libmilter/../../contrib/sendmail/libmilter/main.c
/usr/src/lib/libmilter/../../contrib/sendmail/libmilter/engine.c
/usr/src/lib/libmilter/../../contrib/sendmail/libmilter/listener.c
/usr/src/lib/libmilter/../../contrib/sendmail/libmilter/handler.c
/usr/src/lib/libmilter/../../contrib/sendmail/libmilter/comm.c
/usr/src/lib/libmilter/../../contrib/sendmail/libmilter/smfi.c
/usr/src/lib/libmilter/../../contrib/sendmail/libmilter/signal.c
/usr/src/lib/libmilter/../../contrib/sendmail/libmilter/sm_gethost.c
/usr/src/lib/libmilter/../../contrib/sendmail/libsm/errstring.c
/usr/src/lib/libmilter/../../contrib/sendmail/libsm/strl.c
In file included from
/usr/src/lib/libmilter/../../contrib/sendmail/libmilter/libmilter.h:31,
 from
/usr/src/lib/libmilter/../../contrib/sendmail/libmilter/main.c:15:
/usr/src/lib/libmilter/../../contrib/sendmail/src/sendmail.h:134:25:
sasl/sasl.h: No such file or directory
/usr/src/lib/libmilter/../../contrib/sendmail/src/sendmail.h:135:29:
sasl/saslutil.h: No such file or directory
In file included from
/usr/src/lib/libmilter/../../contrib/sendmail/libmilter/libmilter.h:31,
 from
/usr/src/lib/libmilter/../../contrib/sendmail/libmilter/engine.c:14:
/usr/src/lib/libmilter/../../contrib/sendmail/src/sendmail.h:134:25:
sasl/sasl.h: No such file or directory
/usr/src/lib/libmilter/../../contrib/sendmail/src/sendmail.h:135:29:
sasl/saslutil.h: No such file or directory
In file included from
/usr/src/lib/libmilter/../../contrib/sendmail/libmilter/libmilter.h:31,
 from
/usr/src/lib/libmilter/../../contrib/sendmail/libmilter/listener.c:18:
/usr/src/lib/libmilter/../../contrib/sendmail/src/sendmail.h:134:25:
sasl/sasl.h: No such file or directory
/usr/src/lib/libmilter/../../contrib/sendmail/src/sendmail.h:135:29:
sasl/saslutil.h: No such file or directory
In file included from
/usr/src/lib/libmilter/../../contrib/sendmail/libmilter/libmilter.h:31,
 from
/usr/src/lib/libmilter/../../contrib/sendmail/libmilter/handler.c:14:
/usr/src/lib/libmilter/../../contrib/sendmail/src/sendmail.h:134:25:
sasl/sasl.h: No such file or directory
/usr/src/lib/libmilter/../../contrib/sendmail/src/sendmail.h:135:29:
sasl/saslutil.h: No such file or directory
In file included from
/usr/src/lib/libmilter/../../contrib/sendmail/libmilter/libmilter.h:31,
 from
/usr/src/lib/libmilter/../../contrib/sendmail/libmilter/comm.c:14:
/usr/src/lib/libmilter/../../contrib/sendmail/src/sendmail.h:134:25:
sasl/sasl.h: No such file or directory
/usr/src/lib/libmilter/../../contrib/sendmail/src/sendmail.h

Re: make buildworld errors

[Lowell Gilbert]

"Jacob Jennings" <[EMAIL PROTECTED]> writes:

> Hello, I am attempting to update my FreeBSD 6.0 installation's source
> tree directly after the install. I have cvsup'ed "src-all" and run
> "make buildworld" in /usr/src. However, this command fails in a
> different spot each time with a segmentation fault. Once the error
> message was "Internal compiler error: Segmentation fault: 11" and
> another time it was "Segmentation fault: (core dumped): Error 139",
> and I simply cannot find a solution to this on google or freebsd
> forums. I read that it may be linked to bad memory, but I installed
> memtest and ran it with no complaints therefrom. What could possibly
> be the problem?

If you try the same compile procedure and get *different* failures
each time, it's almost certainly some kind of bad hardware.  Memory is
the most likely but not the only possibility.

See the 'Why do my programs occasionally die with "Signal 11" errors?'
entry in the FreeBSD FAQ.
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: make buildworld errors

[Andy Greenwood]

memtest is a good start, but isn't definate. I would recommend running
memtest86, which you can get at http://www.memtest86.com/, overnight
or longer and see if it comes up with anything. I had some wierd
problems with compilling and this let me know that one of my sticks
was bad. replaced them and everything works like a champ now.

On 6/19/06, Jacob Jennings <[EMAIL PROTECTED]> wrote:

Hello, I am attempting to update my FreeBSD 6.0 installation's source
tree directly after the install. I have cvsup'ed "src-all" and run
"make buildworld" in /usr/src. However, this command fails in a
different spot each time with a segmentation fault. Once the error
message was "Internal compiler error: Segmentation fault: 11" and
another time it was "Segmentation fault: (core dumped): Error 139",
and I simply cannot find a solution to this on google or freebsd
forums. I read that it may be linked to bad memory, but I installed
memtest and ran it with no complaints therefrom. What could possibly
be the problem?
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"


___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: [SOLVED] Re: make buildworld fails with CPUTYPE set

[Pietro Cerutti]

On 5/9/06, RW <[EMAIL PROTECTED]> wrote:

On Tuesday 09 May 2006 22:21, Pietro Cerutti wrote:
> On 5/9/06, Pietro Cerutti <[EMAIL PROTECTED]> wrote:
> > CPUTYPE=pentium3[m]
>
> I solved the problem by putting pentium3 instead of pentium3[m].
>
> So why it's stated "pentium3[m]" in line 35 of
> /usr/src/share/examples/etc/make.conf ?

[] is usually shorthand for an optional variant

i.e.  pentium3[m] means pentium3 or pentium3m


Thanx Erick and RW.
I knew the notation, but I didn't realize it was used there

--
Pietro Cerutti
<[EMAIL PROTECTED]>
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: [SOLVED] Re: make buildworld fails with CPUTYPE set

[RW]

On Tuesday 09 May 2006 22:21, Pietro Cerutti wrote:
> On 5/9/06, Pietro Cerutti <[EMAIL PROTECTED]> wrote:
> > CPUTYPE=pentium3[m]
>
> I solved the problem by putting pentium3 instead of pentium3[m].
>
> So why it's stated "pentium3[m]" in line 35 of
> /usr/src/share/examples/etc/make.conf ?

[] is usually shorthand for an optional variant

i.e.  pentium3[m] means pentium3 or pentium3m
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: [SOLVED] Re: make buildworld fails with CPUTYPE set

[Erik Trulsson]

On Tue, May 09, 2006 at 11:21:52PM +0200, Pietro Cerutti wrote:
> On 5/9/06, Pietro Cerutti <[EMAIL PROTECTED]> wrote:
> >CPUTYPE=pentium3[m]
> 
> I solved the problem by putting pentium3 instead of pentium3[m].
> 
> So why it's stated "pentium3[m]" in line 35 of
> /usr/src/share/examples/etc/make.conf ?
> 
> #   (Intel CPUs) nocona pentium4[m] prescott pentium3[m] pentium-m
> #pentium2 pentiumpro pentium-mmx pentium i486 i386
> 

It is just a shorthand for 'pentium3 pentium3m'.
The [xxx] syntax is often used in used in Unix documentation to denote
an optional part of a command line (or similar.)  In this case it is the
letter 'm' which can be added or not.



-- 

Erik Trulsson
[EMAIL PROTECTED]
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

[SOLVED] Re: make buildworld fails with CPUTYPE set

[Pietro Cerutti]

On 5/9/06, Pietro Cerutti <[EMAIL PROTECTED]> wrote:

CPUTYPE=pentium3[m]


I solved the problem by putting pentium3 instead of pentium3[m].

So why it's stated "pentium3[m]" in line 35 of
/usr/src/share/examples/etc/make.conf ?

#   (Intel CPUs) nocona pentium4[m] prescott pentium3[m] pentium-m
#pentium2 pentiumpro pentium-mmx pentium i486 i386

Thanx,



--
Pietro Cerutti
<[EMAIL PROTECTED]>


--
Pietro Cerutti
<[EMAIL PROTECTED]>
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: make buildworld fails

[László Nagy]

Here's what I would try.  Upgrade to RELENG_4 via the cvsup/buildworld 
process,

read Bruce Mah's 4.11-5.X Migration Guide, and be sure and include
"mergemaster -p" in your buildworld cycle.


Can you tell me where is that migration guide? When I google for it, I 
only get posts about that guide. But where is the guide itself?


Another problem: I only have remote access to that machine. Is it 
possible to upgrade to 5.X without booting into single user mode?
Yes, theoretically, I shouldn't do that but I'm in Hungary and the 
computer is in the US...

Thanks,

 Laszlo

 
___

freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: make buildworld fails

[Kevin Kinsey]

gandalf wrote:



 Hello,

I have this file /etc/sup.sys:

*default host=cvsup.hu.FreeBSD.org
*default base=/usr
*default prefix=/usr
*default release=cvs tag=RELENG_6
*default delete use-rel-suffix
*default compress
src-all


Then I traverse to /usr and execute this command:

cvsup /etc/sup.sys

After successful checkout, I do

cd /usr/src
make buildworld

This is what I get:

--
>>> Building an up-to-date make(1)
--
rm -f .depend
mkdep -f .depend -a-I/usr/src/usr.bin/make 
-DMAKE_VERSION=\"5200408120\" -D__FBSDID=__RCSID 
-DDEFSHELLNAME=\"sh\"  /usr/src/usr.bin/make/arch.c 
/usr/src/usr.bin/make/buf.c /usr/src/usr.bin/make/cond.c 
/usr/src/usr.bin/make/dir.c /usr/src/usr.bin/make/for.c 
/usr/src/usr.bin/make/hash.c /usr/src/usr.bin/make/hash_tables.c 
/usr/src/usr.bin/make/job.c /usr/src/usr.bin/make/lst.c 
/usr/src/usr.bin/make/main.c /usr/src/usr.bin/make/make.c 
/usr/src/usr.bin/make/parse.c /usr/src/usr.bin/make/proc.c 
/usr/src/usr.bin/make/shell.c /usr/src/usr.bin/make/str.c 
/usr/src/usr.bin/make/suff.c /usr/src/usr.bin/make/targ.c 
/usr/src/usr.bin/make/util.c /usr/src/usr.bin/make/var.c

In file included from /usr/src/usr.bin/make/arch.c:107:
/usr/src/usr.bin/make/globals.h:49: stdint.h: No such file or directory
In file included from /usr/src/usr.bin/make/cond.c:59:
/usr/src/usr.bin/make/globals.h:49: stdint.h: No such file or directory
In file included from /usr/src/usr.bin/make/dir.c:97:
/usr/src/usr.bin/make/globals.h:49: stdint.h: No such file or directory
In file included from /usr/src/usr.bin/make/for.c:55:
/usr/src/usr.bin/make/globals.h:49: stdint.h: No such file or directory
In file included from /usr/src/usr.bin/make/job.c:131:
/usr/src/usr.bin/make/globals.h:49: stdint.h: No such file or directory
In file included from /usr/src/usr.bin/make/main.c:84:
/usr/src/usr.bin/make/globals.h:49: stdint.h: No such file or directory
In file included from /usr/src/usr.bin/make/make.c:80:
/usr/src/usr.bin/make/globals.h:49: stdint.h: No such file or directory
In file included from /usr/src/usr.bin/make/parse.c:86:
/usr/src/usr.bin/make/globals.h:49: stdint.h: No such file or directory
In file included from /usr/src/usr.bin/make/str.c:49:
/usr/src/usr.bin/make/globals.h:49: stdint.h: No such file or directory
In file included from /usr/src/usr.bin/make/suff.c:102:
/usr/src/usr.bin/make/globals.h:49: stdint.h: No such file or directory
In file included from /usr/src/usr.bin/make/targ.c:84:
/usr/src/usr.bin/make/globals.h:49: stdint.h: No such file or directory
In file included from /usr/src/usr.bin/make/util.c:59:
/usr/src/usr.bin/make/globals.h:49: stdint.h: No such file or directory
In file included from /usr/src/usr.bin/make/var.c:96:
/usr/src/usr.bin/make/globals.h:49: stdint.h: No such file or directory
mkdep: compile failed
*** Error code 1

Stop in /usr/src/usr.bin/make.
*** Error code 1

Stop in /usr/src.
*** Error code 1

Stop in /usr/src.


What am I doing wrong?



Possibly, and I say possibly, and this isn't to be taken personally:
diving in before depth of the water. ;-)

At the very least, you should have run "mergemaster -p" before
make buildworld as this is a giant step (e.g. 4.8->4.11)..  Did you?

Probably the issue is simply the huge distance in time/development
between 4.8 and 6.0.  See below.


Additional questions:

- Can I upgrade from 4.8 to 6.0 in one step? Or should I upgrade to 
5.4 first?



Probably not.  A fresh install would have a benefit: you could re-format
your disks as UFS2.  However, some people have been able to get from 4.11 to
5.X with cvsup/buildworld, and the 5.X -> 6.X jump is "a piece of 
cake".  You

just have to do the jump from 4 to 5 carefully, and from a much more recent
4.X codebase than 4.8 .

- I have a .so file for 4.8. I do not have the sources, will it work 
on 6.0?




Dunno.  Probably not natively, but maybe; there is, of course, the 
COMPAT_FREEBSD4

stuff, too.


Thanks,

  Laszlo



Here's what I would try.  Upgrade to RELENG_4 via the cvsup/buildworld 
process,

read Bruce Mah's 4.11-5.X Migration Guide, and be sure and include
"mergemaster -p" in your buildworld cycle.

HTH,

Kevin Kinsey

--
In the next world, you're on your own.


___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: make buildworld

[Giorgos Keramidas]

On 2005-12-26 23:49, Doug Hardie <[EMAIL PROTECTED]> wrote:
> I am upgrading a server to 6.0 and encountered an error in make
> buildworld.  However, I don't know what the error was as I piped
> stdout to a file, but not stderr.

I usually keep them both, with something like:

# cd /usr/src/
# cvs -q up -APd | logfile.cvs
# make buildworld buildkernel 2>&1 | tee logfile.build

> It was fairly near the end so I really hate to restart from the
> beginning again.  The master server is a fairly slow machine.

Then, someone could argue that the problem is not a build that's
failing, but the fact that you're using a slow machine as the build
server :-/

I'm afraid there's no way to recover data that has scrolled off the
scrollback buffer of syscons or screen(1), when the same data wasn't
saved in a file.

> When something like this happens, is there a way to restart the make
> where it died?

You can try using -DNO_CLEAN, but this will do a fair bit of work too.

> Is there an easy way to build the specific module that failed to get
> the complete errors?  In this case the module was /usr/libexec/telnet.
> I went to /usr/src/ libexec/telnet and did a make.

Then the error was somewhere else.  Were you using make -j XXX with a
non-default XXX number?

___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: make buildworld

[Björn König]

Doug Hardie schrieb:
I am upgrading a server to 6.0 and encountered an error in make  
buildworld.  However, I don't know what the error was as I piped  stdout 
to a file, but not stderr.  It was fairly near the end so I  really hate 
to restart from the beginning again.  The master server  is a fairly 
slow machine.  When  something like this happens, is  there a way to 
restart the make where it died?  Is there an easy way  to build the 
specific module that failed to get the complete errors?   In this case 
the module was /usr/libexec/telnet.  I went to /usr/src/ libexec/telnet 
and did a make.  It completed without any problems.   So, I ended up 
restarting the make from the top again, but would like  to know for 
future situations.  Thanks.


Try "make -DNO_CLEAN buildworld" next time. This prevents the build 
script from deleting object files in /usr/obj.


Regards
Björn
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: make buildworld failure

[Andreas Rudisch]

On Tue, 2005-12-13 at 09:54 -0600, Dan Ross wrote:
> I am trying to build a new kernel with smp.  I started with make clean 
> and got no errors.
> I then type make buildworld from /usr/src directory

> suggestions?

1. You do not need to recompile world if you only want to build a new
kernel with smp support.

2. read:
http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/makeworld.html
especially chapter 20.4.10 and 20.4.16.6.

Andreas

-- 
GnuPG key  : 0x2A573565  |  http://cyb.websimplex.de/pubkey.asc
Fingerprint: 925D 2089 0BF9 8DE5 9166  33BB F0FD CD37 2A57 3565


signature.asc
Description: This is a digitally signed message part

Re: make buildworld fails from 5.4->6.0

[Anthony Philipp]

On Mon, Dec 05, 2005 at 08:12:50AM -1000, 
Robert Marella <[EMAIL PROTECTED]> wrote:
> Hello Anthony
> 
> Did you remove everything under the /usr/obj directory before make
> buildworld?
> 
> Good luck
> Robert

I now have, and that fixed the problem. Thanks for you help!

Anthony
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: make buildworld fails from 5.4->6.0

[Robert Marella]

On Mon, 5 Dec 2005 03:11:46 -0600
Anthony Philipp <[EMAIL PROTECTED]> wrote:

> Hello,
> 
> I am trying to upgrade from 5.4 to 6.0. I ran cvsup and tried a make
> buildworld, but it failed. So I checked out the handbook and noticed
> that it mentioned I should run a mergemaster -p first. So I did that
> and I still failed. Here are the last few lines:
> 
> : undefined reference to `Buf_AddByte'
> var.o(.text+0x2b5e): In function `Var_Dump':
> : undefined reference to `Buf_Data'
> var.o(.text+0x2ba2): In function `Var_Dump':
> : undefined reference to `Buf_Data'
> var.o(.text+0x2c31): In function `Var_Print':
> : undefined reference to `Buf_Peel'
> *** Error code 1
> 
> Stop in /usr/src/usr.bin/make.
> *** Error code 1
> 
> Stop in /usr/src.
> *** Error code 1
> 
> Stop in /usr/src.
> 
> I've searched the archives and couldn't find anything relating to
> this, but hopefully someone knows the answer. Also I have have done
> minor version changes before, but never a major one, so maybe I am
> just missing a key step.
> 
> Thanks in advance!
> 
> Anthony Philipp
Hello Anthony

Did you remove everything under the /usr/obj directory before make
buildworld?

Good luck
Robert
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: make buildworld fails from 5.4->6.0

[Benjamin Sobotta]

On Monday 05 December 2005 09:51, Anthony Philipp wrote:
> On Mon, Dec 05, 2005 at 10:41:15AM +,
>
> Benjamin Sobotta <[EMAIL PROTECTED]> wrote:
> > Hey!
> >
> > You might want to have a look at
> >
> > http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/makeworld.html
> >
> > especially subsection
> >
> > 20.4.16.6. What do I do if something goes wrong
>
> I will try this and get back do you. Thanks for the tip.
>
> > Further, I believe that you run mergemaster -p before make installworld.
> > Not buildworld, after all I believe buildworld has to finish so you know
> > what to merge in the first place. So if buildworld fails, that has
> > nothing to do with mergemaster.
>
> I had looked at the handbook and saw this:
>
> Note: There are a few rare cases when an extra run of mergemaster -p is
> needed before the buildworld step. These are described in UPDATING. In
> general, though, you can safely omit this step if you are not updating
> across one or more major FreeBSD versions.
>
> This is the only reason I tried it.
>
> Thanks for the response!
>
> Anthony

Interesting! I didn't know that.

Thank you!

>
> > On Monday 05 December 2005 09:11, Anthony Philipp wrote:
> > > Hello,
> > >
> > > I am trying to upgrade from 5.4 to 6.0. I ran cvsup and tried a make
> > > buildworld, but it failed. So I checked out the handbook and noticed
> > > that it mentioned I should run a mergemaster -p first. So I did that
> > >
> > > and I still failed. Here are the last few lines:
> > > : undefined reference to `Buf_AddByte'
> > >
> > > var.o(.text+0x2b5e): In function `Var_Dump':
> > > : undefined reference to `Buf_Data'
> > >
> > > var.o(.text+0x2ba2): In function `Var_Dump':
> > > : undefined reference to `Buf_Data'
> > >
> > > var.o(.text+0x2c31): In function `Var_Print':
> > > : undefined reference to `Buf_Peel'
> > >
> > > *** Error code 1
> > >
> > > Stop in /usr/src/usr.bin/make.
> > > *** Error code 1
> > >
> > > Stop in /usr/src.
> > > *** Error code 1
> > >
> > > Stop in /usr/src.
> > >
> > > I've searched the archives and couldn't find anything relating to
> > > this, but hopefully someone knows the answer. Also I have have done
> > > minor version changes before, but never a major one, so maybe I am
> > > just missing a key step.
> > >
> > > Thanks in advance!
> > >
> > > Anthony Philipp
> > > ___
> > > freebsd-questions@freebsd.org mailing list
> > > http://lists.freebsd.org/mailman/listinfo/freebsd-questions
> > > To unsubscribe, send any mail to
> > > "[EMAIL PROTECTED]"
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: make buildworld fails from 5.4->6.0

[Anthony Philipp]

On Mon, Dec 05, 2005 at 10:41:15AM +, 
Benjamin Sobotta <[EMAIL PROTECTED]> wrote:

> Hey!
> 
> You might want to have a look at
> 
> http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/makeworld.html
> 
> especially subsection 
> 
> 20.4.16.6. What do I do if something goes wrong
> 

I will try this and get back do you. Thanks for the tip.

> Further, I believe that you run mergemaster -p before make installworld. Not 
> buildworld, after all I believe buildworld has to finish so you know what to 
> merge in the first place. So if buildworld fails, that has nothing to do with 
> mergemaster.

I had looked at the handbook and saw this:

Note: There are a few rare cases when an extra run of mergemaster -p is needed
before the buildworld step. These are described in UPDATING. In general,
though, you can safely omit this step if you are not updating across one or
more major FreeBSD versions.

This is the only reason I tried it.

Thanks for the response!

Anthony

> On Monday 05 December 2005 09:11, Anthony Philipp wrote:
> > Hello,
> >
> > I am trying to upgrade from 5.4 to 6.0. I ran cvsup and tried a make
> > buildworld, but it failed. So I checked out the handbook and noticed
> > that it mentioned I should run a mergemaster -p first. So I did that
> >
> > and I still failed. Here are the last few lines:
> > : undefined reference to `Buf_AddByte'
> >
> > var.o(.text+0x2b5e): In function `Var_Dump':
> > : undefined reference to `Buf_Data'
> >
> > var.o(.text+0x2ba2): In function `Var_Dump':
> > : undefined reference to `Buf_Data'
> >
> > var.o(.text+0x2c31): In function `Var_Print':
> > : undefined reference to `Buf_Peel'
> >
> > *** Error code 1
> >
> > Stop in /usr/src/usr.bin/make.
> > *** Error code 1
> >
> > Stop in /usr/src.
> > *** Error code 1
> >
> > Stop in /usr/src.
> >
> > I've searched the archives and couldn't find anything relating to
> > this, but hopefully someone knows the answer. Also I have have done
> > minor version changes before, but never a major one, so maybe I am
> > just missing a key step.
> >
> > Thanks in advance!
> >
> > Anthony Philipp
> > ___
> > freebsd-questions@freebsd.org mailing list
> > http://lists.freebsd.org/mailman/listinfo/freebsd-questions
> > To unsubscribe, send any mail to
> > "[EMAIL PROTECTED]"
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: make buildworld fails from 5.4->6.0

[Benjamin Sobotta]

Hey!

You might want to have a look at

http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/makeworld.html

especially subsection 

20.4.16.6. What do I do if something goes wrong

Further, I believe that you run mergemaster -p before make installworld. Not 
buildworld, after all I believe buildworld has to finish so you know what to 
merge in the first place. So if buildworld fails, that has nothing to do with 
mergemaster.

HTH,

Ben

On Monday 05 December 2005 09:11, Anthony Philipp wrote:
> Hello,
>
> I am trying to upgrade from 5.4 to 6.0. I ran cvsup and tried a make
> buildworld, but it failed. So I checked out the handbook and noticed
> that it mentioned I should run a mergemaster -p first. So I did that
>
> and I still failed. Here are the last few lines:
> : undefined reference to `Buf_AddByte'
>
> var.o(.text+0x2b5e): In function `Var_Dump':
> : undefined reference to `Buf_Data'
>
> var.o(.text+0x2ba2): In function `Var_Dump':
> : undefined reference to `Buf_Data'
>
> var.o(.text+0x2c31): In function `Var_Print':
> : undefined reference to `Buf_Peel'
>
> *** Error code 1
>
> Stop in /usr/src/usr.bin/make.
> *** Error code 1
>
> Stop in /usr/src.
> *** Error code 1
>
> Stop in /usr/src.
>
> I've searched the archives and couldn't find anything relating to
> this, but hopefully someone knows the answer. Also I have have done
> minor version changes before, but never a major one, so maybe I am
> just missing a key step.
>
> Thanks in advance!
>
> Anthony Philipp
> ___
> freebsd-questions@freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-questions
> To unsubscribe, send any mail to
> "[EMAIL PROTECTED]"
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: make buildworld run twice as fast

[Kris Kennaway]

On Thu, Dec 01, 2005 at 01:19:41PM -0800, Jose Borquez wrote:
> I recently rebuilt my FreeBSD system from sources and it took around 2 
> hours on an old PIII 800MHz pc to run "make buildworld".  If I include 
> the -j option to run multiple processes as once such as "make -j2 
> buildworld" does that mean it would finish in half the time?

No, that would only be true if you were using less than 50% of your
resources (e.g. CPU) - for example, if your system has 2 CPUs.
Otherwise, on a single CPU machine you are already using close to 100%
of CPU, but you may still achieve a few percent speed-up since
e.g. one compiler process can be running while another process is
blocked waiting for disk I/O.  However, this is balanced against
increased kernel overhead and memory use.

Kris

pgpPU9y8CQdw7.pgp
Description: PGP signature

Re: make buildworld fails on step 1.2 and questions

[Garrett Cooper]

On Sep 20, 2005, at 7:01 PM, Chris wrote:



A few things - If you are using CURRENT (anything) you have posted to
the wrong list - try FreeBSD-CURRENT.


K.


If your a newb (as you seem to be), you should be using either
5.4-RELEASE or 4.11-RELEASE


Meh. I just want to get my hands dirty a bit and learn more  
about FreeBSD to the point where I feel confident about the OS inside  
out.



If you want to use the patch branch of 5.4, your cvs tag will be:
*default release=cvs tag=RELENG_5_4

If you want the 4.11 patch branch:
*default release=cvs tag=RELENG_4_11

I have been using FreeBSD since 2.2.8 - and only recently have I felt
comfy enough to use CURRENT.

For you - admirable, yes - foolish, you betcha. Stick to something  
solid

until you know what you're doing...


Still, one must make mistakes in order to learn. Besides, my  
important data is on a separate partition just in case anything goes  
awry, and I do have a LiveCD on hand.


Thank you though, I do appreciate it.
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: make buildworld fails on step 1.2 and questions

[Chris]

Garrett Cooper wrote:
> Hello,
> I'm building my OS from source from the first time, and I  realize
> that I must have missed a step in configuring it properly. I  just hate
> treading through a lot of documentation when there isn't a  really nice
> search feature involved, so if someone can give me the  steps they
> used-or even better-the section in a handbook or FAQ on  how to do the
> buildworld properly, I would appreciate it.
> Also, I was wondering if there was any specific syntax I should  use
> for specifying the version of FreeBSD that I want to use, ie 6.0-
> CURRENT vs 7.0-CURRENT (because I think that 7.0 has just come out,  but
> I may be wrong because I haven't been keeping completely up to  date).
> All that I have done so far is CVSUP'ed my files into /usr and 
> that's about it. I am not sure where to go from here.
> I greatly appreciate any and all help provided to me.
> Thanks,
> -Garrett
> 
> Command I use for building the system:
> 
> [EMAIL PROTECTED] cd /usr/src/ && make update && make buildworld &&  make
> kernel
> 
> Here is the error that comes up:

... Snip

A few things - If you are using CURRENT (anything) you have posted to
the wrong list - try FreeBSD-CURRENT.

If your a newb (as you seem to be), you should be using either
5.4-RELEASE or 4.11-RELEASE

If you want to use the patch branch of 5.4, your cvs tag will be:
*default release=cvs tag=RELENG_5_4

If you want the 4.11 patch branch:
*default release=cvs tag=RELENG_4_11

I have been using FreeBSD since 2.2.8 - and only recently have I felt
comfy enough to use CURRENT.

For you - admirable, yes - foolish, you betcha. Stick to something solid
until you know what you're doing...

-- 
Best regards,
Chris

1) You can't win
2) You can't break even
3) You can't even quit the game
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

RE: make buildworld + make buildkernel

[Bob]

 Thanks Giorgos, 
I figured as much, but wasn't sure, thanks again,
Bob

-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Giorgos Keramidas
Sent: Tuesday, September 13, 2005 10:41 AM
To: Middaugh, Bob
Cc: freebsd-questions@freebsd.org
Subject: Re: make buildworld + make buildkernel

On 2005-09-13 10:32, "Middaugh, Bob" <[EMAIL PROTECTED]>
wrote:
> I was in the process of doing make buildworld, make buildkernel, etc...
> Make buildworld complete, but before I could do make buildkernel, 
> etc... my machine shutdown - power outtage.  My question is, do I have 
> to redo make buildworld before I do make buildkernel or can I just 
> turn my machine on and start with make buildkernel and go from there, 
> eventually installing the kernel and doing make buildworld.

If you are certain that the "buildworld" step has finished, no you don't
have to rerun it.  Just start from where you left off:

# cd /usr/src
# make buildkernel

and you should be fine.

___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: make buildworld + make buildkernel

[Giorgos Keramidas]

On 2005-09-13 10:32, "Middaugh, Bob" <[EMAIL PROTECTED]> wrote:
> I was in the process of doing make buildworld, make buildkernel, etc...
> Make buildworld complete, but before I could do make buildkernel, etc... my
> machine shutdown - power outtage.  My question is, do I have to redo make
> buildworld before I do make buildkernel or can I just turn my machine on and
> start with make buildkernel and go from there, eventually installing the
> kernel and doing make buildworld.

If you are certain that the "buildworld" step has finished, no you don't
have to rerun it.  Just start from where you left off:

# cd /usr/src
# make buildkernel

and you should be fine.

___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

[solved] Re: make buildworld breaks in ncurses

[Mac Mason]

On Tue, Aug 30, 2005 at 09:10:29PM -0700, Mac Mason wrote:
> While running a make buildworld on a system that was cvsup'd to
> RELENG_5_4 about an hour ago, it breaks on 
> 
>  [snip]/contrib/ncurses/ncurses/tinfo/make_keys.c
> 
> with
> 
>   /usr/obj/usr/src/sys/i386/usr/bin/ld: cannot find -lc
> 
> What's going on here? I deleted both /usr/obj and /usr/src and
> re-cvs-up'd before running make buildworld, so the build should be
> clean.

As it turns out, when you buy a new motherboard, the hardware clock is
set wrong.

And make depends very heavily on timestamps.

Fixing that solved the problem nicely.

--Mac



pgpM3TrDcM8R8.pgp
Description: PGP signature

Re: make buildworld fails in openssl/colldef [SOLVED]

[Alex Zbyslaw]

Marius Korsmo wrote:

That does not look like an *old* version, it looks like a completely 
different file.  Did you install anything not from ports that might 
have overwritten it?  Did you try and install a port into a target 
hierarchy that /usr/local?  (The same copyright header as the real 
5.4 one exists in err.h from 4.11).


Operating system bugs are rare compared to user errors, I'm afraid.

--Alex


As far as I can remember, I have not installed anything that didn't 
come from
the ports collection. I have only used the ports, and always installed 
them to

the default directory.

I did not mean that this was a OS bug, and it would be really strange 
if it was
since I can't find any other person that has had the same problem. 
There must
be an application that overwrote my err.h. I've tried to provoke this 
error
again, but I can't. I tried to install all the ports on another server 
(until i
ran out of space), but the error did not occur. But with that said, 
there was 20
ports I didn't have enough space to install, so the problem might lie 
there.


I might be the problem as well, maybe I did something I shouldn't have 
done. But
I can't really see what that should be :) Anyway, the solution is here 
and I
hope it can help other people that end up with the same problem (if 
that ever

happens).


Then put it down as a mystery :-)

If you are worried about it happening again, then just mail yourself the 
head of the file every day from cron.  If it does change, at least 
you'll know better when it happened and might be better able to figure 
out what caused it.


You could also force re-installation of your current ports on the same 
machine, but that might be more time than you care to spend.


--Alex

PS I suppose the clever way would be to head the file, egrep for 
Copyright then egrep -v the correct date (2003) since that will be empty 
when the file is correct.  So you should be able to arrange for the mail 
to arrive only when there is a problem (which might be never again!).


___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: make buildworld fails in openssl/colldef [SOLVED]

[Marius Korsmo]

Quoting Alex Zbyslaw <[EMAIL PROTECTED]>:


Marius Korsmo wrote:

It took two weeks to fix this problem, and therefore I do have a few 
questions.


The error turned out to be in err.h. The file located in /usr/include was
totally different from the one located in /usr/src/include.

< /*-
<  * Copyright (c) 1993
<  *The Regents of the University of California.  All rights reserved.
---


/* crypto/err/err.h */
/* Copyright (C) 1995-1998 Eric Young ([EMAIL PROTECTED])
* All rights reserved.



You can see the entire diff at http://pastebin.com/322918

My question is: I deleted /usr/src, and I cvsup'ed everything. When 
I do a make

buildworld, why does not the new err.h get copied from /usr/src/include to
/usr/include? This would have solved my problem two weeks ago :)


build = recompile things
install = put them where they belong in the filesystem

buildworld doesn't install the file because it's not supposed to.


Does err.h get copied only when you do a make installworld?


I would expect so.  Why don't you try it?

Another question, why on earth did I have an old version of err.h? I 
was running

5.4 RELEASE, and it was installed from an ISO downloaded at FreeBSD.org

That does not look like an *old* version, it looks like a completely 
different file.  Did you install anything not from ports that might 
have overwritten it?  Did you try and install a port into a target 
hierarchy that /usr/local?  (The same copyright header as the real 
5.4 one exists in err.h from 4.11).


Operating system bugs are rare compared to user errors, I'm afraid.

--Alex



As far as I can remember, I have not installed anything that didn't come from
the ports collection. I have only used the ports, and always installed them to
the default directory.

I did not mean that this was a OS bug, and it would be really strange 
if it was

since I can't find any other person that has had the same problem. There must
be an application that overwrote my err.h. I've tried to provoke this error
again, but I can't. I tried to install all the ports on another server 
(until i
ran out of space), but the error did not occur. But with that said, 
there was 20

ports I didn't have enough space to install, so the problem might lie there.

I might be the problem as well, maybe I did something I shouldn't have 
done. But

I can't really see what that should be :) Anyway, the solution is here and I
hope it can help other people that end up with the same problem (if that ever
happens).

Marius




This message was sent using IMP, the Internet Messaging Program.

___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

RE: make buildworld error

[Norbert Koch]

> I keep getting the following on a 4.9 system when trying to move to 
> 4.11.
> 
> rm -f sa main.o pdb.o usrdb.o sa.8.gz sa.8.cat.gz
> rm -f .depend GPATH GRTAGS GSYMS GTAGS
> ===> usr.sbin/setkey
> ".depend", line 1: Need an operator
> ".depend", line 2: Need an operator
> ".depend", line 3: Need an operator
> ".depend", line 4: Need an operator
> ".depend", line 6: Need an operator
> ".depend", line 7: Need an operator
> ".depend", line 8: Need an operator
> ".depend", line 9: Need an operator
> ".depend", line 10: Need an operator
> ".depend", line 11: Need an operator
> ".depend", line 12: Need an operator
> ".depend", line 13: Need an operator
> ".depend", line 14: Need an operator
> ".depend", line 15: Need an operator
> ".depend", line 16: Need an operator
> ".depend", line 17: Need an operator
> ".depend", line 18: Need an operator
> ".depend", line 19: Need an operator
> ".depend", line 20: Need an operator
> ".depend", line 21: Need an operator
> ".depend", line 22: Need an operator
> make: fatal errors encountered -- cannot continue
> 
> Anyone offer some advice?  I've tried updating my source again - I even 
> went as far as nuking my /usr/src directory and re-fetching it.

Are you trying to use gmake instead of the original bsd make?
'make -v' should give you 'make: no target to make'
If you use gmake, you see something like

GNU Make 3.80
Copyright (C) 2002  Free Software Foundation, Inc.
This is free software; see the source for copying conditions.
There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A
PARTICULAR PURPOSE.


Norbert
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: make buildworld fails in openssl/colldef [SOLVED]

[Alex Zbyslaw]

Marius Korsmo wrote:


It took two weeks to fix this problem, and therefore I do have a few questions.

The error turned out to be in err.h. The file located in /usr/include was
totally different from the one located in /usr/src/include.

< /*-
<  * Copyright (c) 1993
<  *The Regents of the University of California.  All rights reserved.
---
 


/* crypto/err/err.h */
/* Copyright (C) 1995-1998 Eric Young ([EMAIL PROTECTED])
* All rights reserved.
   



You can see the entire diff at http://pastebin.com/322918

My question is: I deleted /usr/src, and I cvsup'ed everything. When I do a make
buildworld, why does not the new err.h get copied from /usr/src/include to
/usr/include? This would have solved my problem two weeks ago :)
 


build = recompile things
install = put them where they belong in the filesystem

buildworld doesn't install the file because it's not supposed to.


Does err.h get copied only when you do a make installworld?
 


I would expect so.  Why don't you try it?


Another question, why on earth did I have an old version of err.h? I was running
5.4 RELEASE, and it was installed from an ISO downloaded at FreeBSD.org
 

That does not look like an *old* version, it looks like a completely 
different file.  Did you install anything not from ports that might have 
overwritten it?  Did you try and install a port into a target hierarchy 
that /usr/local?  (The same copyright header as the real 5.4 one exists 
in err.h from 4.11).


Operating system bugs are rare compared to user errors, I'm afraid.

--Alex

___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: make buildworld fails

[Valerio Daelli]

Yes.  You're using unsupported optimizations.

Please read very carefully the comments above CFLAGS in

/usr/share/examples/etc/make.conf

- Giorgos



Thanks a lot! I'll use a safer optimization.


Valeiro


___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: make buildworld fails

[Giorgos Keramidas]

On 2005-06-22 14:38, Valerio Daelli <[EMAIL PROTECTED]> wrote:
>
> Then I started to make buildworld. But it fails with this error:
> __
>
> cc -O3 -mtune=pentium4 -march=pentium4 -pipe -funroll-loops -ffast-math
> -march=pentium4 -I/usr/src/lib/libc/include
> -I/usr/src/lib/libc/../../include -I/usr/src/lib/libc/i386
> -D__DBINTERFACE_PRIVATE -I/usr/src/lib/libc/../../contrib/gdtoa -DINET6
> -I/usr/obj/usr/src/lib/libc -DPOSIX_MISTAKE -I/usr/src/lib/libc/locale
> -DBROKEN_DES -DPORTMAP -DDES_BUILTIN -I/usr/src/lib/libc/rpc -DYP -DHESIOD
> -Wsystem-headers -Werror -Wall -Wno-format-y2k -Wno-uninitialized -c
> /usr/src/lib/libc/net/res_debug.c
> In file included from /usr/src/lib/libc/net/res_debug.c:786:
> /usr/src/lib/libc/net/res_debug.c: In function `__loc_aton':
> /usr/src/lib/libc/net/res_debug.c:576: warning: passing arg 1 of
> `precsize_aton' from incompatible pointer type
> In file included from /usr/src/lib/libc/net/res_debug.c:797:
> /usr/src/lib/libc/net/res_debug.c:576: warning: passing arg 1 of
> `precsize_aton' from incompatible pointer type
> In file included from /usr/src/lib/libc/net/res_debug.c:808:
> /usr/src/lib/libc/net/res_debug.c:576: warning: passing arg 1 of
> `precsize_aton' from incompatible pointer type
>
> __
>
> Any idea what's happened?

Yes.  You're using unsupported optimizations.

Please read very carefully the comments above CFLAGS in

/usr/share/examples/etc/make.conf

- Giorgos

___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: make buildworld errors

[Alex Zbyslaw]

Charles Swiger wrote:
Actually, if the compile crashes out at different points, that's 
almost a sure sign of a hardware issue, most probably overheating.  If 
you were just running the system as a network router before, that 
involves so little load that you wouldn't stress anything, but 
building world is a good stress test and marginal cooling will show 
symptoms like what you've described.

I've seen something similar on a Linux box when it was the memory at 
fault.  But definitely hardware!

--Alex
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: Make buildworld and UPDATING

[Erik Trulsson]

On Fri, Mar 18, 2005 at 09:11:27AM -0600, CHris Rich wrote:
> While reading updating I see this:
> 
> 20050227:
> The default "world" build no longer supports running on an
> 80386 CPU.  In order to build a world for an 80386 CPU, one
> needs to set CPUTYPE=i386 in /etc/make.conf.
> 
> does this mean that 80486's and above don't need to set it?

Correct. If you are using a '486 or later you do not *have* to set
CPUTYPE to anything.  If you wish to optimize for your particular CPU
you could set CPUTYPE to reflect the CPU you are actually using, but it
is not necessary other than for a real 80386.


> or do all
> x86's need to set this value?
> 
> It seems to me that only 386 should need to set it but before I start
> updating I want to be sure..




-- 

Erik Trulsson
[EMAIL PROTECTED]
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: make buildworld errors

[Charles Swiger]

On Mar 17, 2005, at 4:43 PM, luke wrote:
this is the 3rd place it's stopped, and like i said, if i repeat the
make buildworld command it will go a little further and stop again.
i'm going to start using time make buildworld and see if there is a
pattern here. this machine has been acting as a slackware gateway for
a little over a year with no hardware change, so i don't think it's
hardware related.
Actually, if the compile crashes out at different points, that's almost 
a sure sign of a hardware issue, most probably overheating.  If you 
were just running the system as a network router before, that involves 
so little load that you wouldn't stress anything, but building world is 
a good stress test and marginal cooling will show symptoms like what 
you've described.

--
-Chuck
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: make buildworld errors

[Kent Stewart]

On Thursday 17 March 2005 01:43 pm, luke wrote:
> i just cvsup'd to release_5_3 and i'm making buildworld but it keeps
> erroring out.
>  if i do make buildworld again, chaning nothing, it goes a little
> further and errors
>  again. i've done this a few times. here's my /etc/make.conf

These are usually hardware errors. Some k6's were famous for 
overheating.

Kent

>
> %more /etc/make.conf
> CPUTYPE=k6-2
> CFLAGS= -O -pipe
> COPTFLAGS= -O -pipe
> NO_FORTRAN= true
> NO_I4B= true
> NO_LPR= true
> NO_X= true
> NOGAMES= true
> NOPROFILE= true
> USA_RESIDENT= yes
>
> %uname -a
> FreeBSD gw.internal.net 5.3-RELEASE FreeBSD 5.3-RELEASE #0: Fri Nov 
> 5 04:19:18 UTC 2004
> [EMAIL PROTECTED]:/usr/obj/usr/src/sys/GENERIC  i386
>
>
> and here's output from the latest time it's stopped. any help is
> appreciated.
>
> cc -O -pipe -I. -DIN_GCC -DHAVE_CONFIG_H -DPREFIX=\"/usr\"
> -I/usr/obj/usr/src/gnu/usr.bin/cc/cc_tools/../cc_tools
> -I/usr/src/gnu/usr.bin/cc/cc_tools/../cc_tools
> -I/usr/src/gnu/usr.bin/cc/cc_tools/../../../../contrib/gcc
> -I/usr/src/gnu/usr.bin/cc/cc_tools/../../../../contrib/gcc/config
> -DGENERATOR_FILE  -I/usr/obj/usr/src/i386/legacy/usr/include -c
> /usr/src/gnu/usr.bin/cc/cc_tools/../../../../contrib/gcc/choose-temp.
>c In file included from
> /usr/src/gnu/usr.bin/cc/cc_tools/../../../../contrib/gcc/choose-temp.
>c:26: /usr/include/stdio.h: In function `__sputc':
> /usr/include/stdio.h:399: internal compiler error: Segmentation fault
> Please submit a full bug report,
> with preprocessed source if appropriate.
> See http://gcc.gnu.org/bugs.html> for instructions.
> *** Error code 1
>
> Stop in /usr/src/gnu/usr.bin/cc/cc_tools.
> *** Error code 1
>
> Stop in /usr/src.
> *** Error code 1
>
> Stop in /usr/src.
> *** Error code 1
>
> Stop in /usr/src.
> gw#
>
> this is the 3rd place it's stopped, and like i said, if i repeat the
> make buildworld command it will go a little further and stop again.
> i'm going to start using time make buildworld and see if there is a
> pattern here. this machine has been acting as a slackware gateway for
> a little over a year with no hardware change, so i don't think it's
> hardware related.
> ___
> freebsd-questions@freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-questions
> To unsubscribe, send any mail to
> "[EMAIL PROTECTED]"

-- 
Kent Stewart
Richland, WA

http://users.owt.com/kstewart/index.html
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: make buildworld

[pete wright]

On Fri, 11 Mar 2005 22:40:48 +0100 (CET), richard clairboy
<[EMAIL PROTECTED]> wrote:
> I face w/ problem when i execute make buildworld after
> i've synced my source from the CVS current 5.3
> release.
> 

What is the problem you are getting, if possible I'd post the error
message to the list.

-p



-- 
~~o0OO0o~~
Pete Wright
www.nycbug.org
NYC's *BSD User Group
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: Make buildworld and reboot

[Kent Stewart]

On Tuesday 08 March 2005 12:31 pm, Bnonn wrote:
> Hi everyone.
>
> I recently let a make buildworld run overnight following updating
> source, and came back in the morning to find that the process had
> completed successfully, but that my keyboard had gone completely
> dead. I don't know why this happened, but it might have something to
> do with having a USB keyboard. Anyway, I couldn't run make
> installworld following this since the keyboard was no-go, so I was
> forced to hard-reboot.

If that is happening, then I would suspect you have hardware problems. 
The reasoning is that buildworld does not change your local environment 
and couldn't cause a hang. Everything that it builds goes 
into /usr/obj.

Now, Murphy likes to embarass me but that is my current $0.02 :).

Kent

>
> Not knowing a great deal about what make buildworld really does, I'm
> not sure if the changes it effects are persistent through a reboot.
> Do I need to run make buildworld again before running make
> installworld? I've skimmed the manpages on make, but they seem
> directed to the sort of people who want to create makefiles, rather
> than just run them, and I thought I could probably get the quick and
> dirty answer here without having to resort to three days of study :)
>
> Your help is appreciated
>
> Bnonn
>
> ___
> freebsd-questions@freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-questions
> To unsubscribe, send any mail to
> "[EMAIL PROTECTED]"

-- 
Kent Stewart
Richland, WA

http://users.owt.com/kstewart/index.html
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: make buildworld

[Kris Kennaway]

On Tue, Mar 01, 2005 at 03:28:15AM -0700, RYAN vAN GINNEKEN wrote:

> I am trying to make buildworld for freebsd 5.3 stable and have done
> a complete cvsup and keep getting the following error messages.
> Please help

If you want to track -stable you should read the -stable mailing list.
This problem was introduced earlier today, reported several times, and
fixed an hour or so ago.

Kris


pgpdGKXMY8fJ6.pgp
Description: PGP signature

Re: make buildworld broke

[Kris Kennaway]

On Tue, Feb 08, 2005 at 02:18:58PM -0500, lists wrote:
> I had a box crash and I got it up again. I lost some information  in / and
> /etc.
> After some reconstructing, it seems to be running fine and all the services
> are working. I wanted to do
> a buildworld just to update anything I might have missed. When I try, I
> always get a stop error. How can
> I get my buildworld back, I dont want to take the box offline for long. I
> also need to add another proc to it,
> which means I need to add smp support, which I can't currently do. What is
> the best course of action for me from
> here? Am I overlooking something simple?
> FreeBSD  5.2.1-RELEASE FreeBSD 5.2.1-RELEASE #0:

What is the exact error you receive?

Kris


pgpz6QViPlCvT.pgp
Description: PGP signature

Re: make buildworld error

[Gert Cuykens]

On Sat, 29 Jan 2005 14:45:52 -0600, Donald J. O'Neill
<[EMAIL PROTECTED]> wrote:
> On Saturday 29 January 2005 01:49 pm, Gert Cuykens wrote:
> > On Sun, 30 Jan 2005 01:11:32 +0530, Subhro <[EMAIL PROTECTED]>
> wrote:
> > > The correct way would be CPUTYPE=k8 as all "Hammers" are basically
> > > having K8 cores. This is also revealed in dmesg.
> >
> > my dmesg
> > CPU: AMD Athlon(tm) 64 FX-53 Processor (2400.01-MHz K8-class CPU)
> >   Origin = "AuthenticAMD"  Id = 0xf5a  Stepping = 10
> > Features=0x78bfbff >GE,MCA,CMOV,PAT,PSE36,CLFLUSH,MMX,FXSR,SSE,SSE2>
> 
> Gert,
> 
> Take the advice of Subhro, this should cut playing around time down.
> Ignore the two examples I gave, unless you want to see what happens.
> 
> Don
> 
> --
> Donald J. O'Neill
> [EMAIL PROTECTED]
> 
> I'm not totally useless,
> I can be used as a bad example.
> 

k8 seems to work thx guy's :)
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: make buildworld error

[Donald J. O'Neill]

On Saturday 29 January 2005 01:49 pm, Gert Cuykens wrote:
> On Sun, 30 Jan 2005 01:11:32 +0530, Subhro <[EMAIL PROTECTED]> 
wrote:
> > The correct way would be CPUTYPE=k8 as all "Hammers" are basically
> > having K8 cores. This is also revealed in dmesg.
>
> my dmesg
> CPU: AMD Athlon(tm) 64 FX-53 Processor (2400.01-MHz K8-class CPU)
>   Origin = "AuthenticAMD"  Id = 0xf5a  Stepping = 10
> Features=0x78bfbffGE,MCA,CMOV,PAT,PSE36,CLFLUSH,MMX,FXSR,SSE,SSE2>

Gert,

Take the advice of Subhro, this should cut playing around time down.
Ignore the two examples I gave, unless you want to see what happens.

Don

-- 
Donald J. O'Neill
[EMAIL PROTECTED]

I'm not totally useless,
I can be used as a bad example.
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: make buildworld error

[Gert Cuykens]

On Sun, 30 Jan 2005 01:11:32 +0530, Subhro <[EMAIL PROTECTED]> wrote:
> The correct way would be CPUTYPE=k8 as all "Hammers" are basically having K8
> cores. This is also revealed in dmesg.

my dmesg
CPU: AMD Athlon(tm) 64 FX-53 Processor (2400.01-MHz K8-class CPU)
  Origin = "AuthenticAMD"  Id = 0xf5a  Stepping = 10  
Features=0x78bfbff
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

RE: make buildworld error

[Subhro]

> -Original Message-
> From: [EMAIL PROTECTED] [mailto:owner-freebsd-
> [EMAIL PROTECTED] On Behalf Of Donald J. O'Neill
> Sent: Sunday, January 30, 2005 0:57
> To: Gert Cuykens
> Cc: freebsd-questions@freebsd.org
> Subject: Re: make buildworld error
> 


> You see the bottom 4 lines? I see a "bad  value (amd64) for -march=
> switch" and a "bad (amd64) for -mtune= switch" . Try changing you
> make.conf file to use "CPUTYPE=?hammer", if that works go on to the
> next step. If it fails, see if you've got a similar error message.

The correct way would be CPUTYPE=k8 as all "Hammers" are basically having K8
cores. This is also revealed in dmesg.



Regards
S.
Indian Institute of Information Technology
Subhro Sankha Kar
Block AQ-13/1, Sector V
Salt Lake City
PIN 700091
India


smime.p7s
Description: S/MIME cryptographic signature

Re: make buildworld error

[Gert Cuykens]

On Sat, 29 Jan 2005 20:37:59 +0100, Gert Cuykens <[EMAIL PROTECTED]> wrote:
> On Sat, 29 Jan 2005 20:33:12 +0100, Gert Cuykens <[EMAIL PROTECTED]> wrote:
> > On Sat, 29 Jan 2005 13:27:15 -0600, Donald J. O'Neill
> > <[EMAIL PROTECTED]> wrote:
> > > On Saturday 29 January 2005 07:55 am, Gert Cuykens wrote:
> > > > On Sat, 29 Jan 2005 11:17:59 +0100, Peter Harmsen
> > > <[EMAIL PROTECTED]> wrote:
> > > > > Seems to me you specified amd64 in /etc/makeconf.
> > > > > If i remember correctly from some posts ago this is obsolete.
> > > > > You can however switch to 32-bit mode by specifying athlon-xp.
> > > > > Otherwise everything should be auto detected by gcc.
> > > >
> > > > why is this obsolete it always worked that way ?
> > >
> > > Gert,
> > >
> > > I had not seen this post until now, and I'm not sure about the question
> > > your asking about.
> > >
> > > It seems to me, he is saying that using "CPUTYPE=?amd64" in your
> > > make.conf is obsolete.
> > >
> > > Your error message would seem to confirm ths
> > >
> > > cc -O -pipe -march=amd64 -DIN_GCC -DHAVE_LD_EH_FRAME_HDR
> > > -finhibit-size-directive -fno-inline-functions  -fno-exceptions
> > > -fno-zero-initialized-in-bss  -fno-omit-frame-pointer
> > > -fno-unit-at-a-time -I/usr/src/gnu/lib/csu/../../../contrib/gcc/config
> > > -I/usr/src/gnu/lib/csu/../../../contrib/gcc -I.
> > > -I/usr/src/gnu/lib/csu/../../usr.bin/cc/cc_tools  -g0 -DCRT_BEGIN  -c
> > > -o crtbegin.o /usr/src/gnu/lib/csu/../../../contrib/gcc/crtstuff.c
> > > /usr/src/gnu/lib/csu/../../../contrib/gcc/crtstuff.c:1: error: bad
> > > value (amd64) for -march= switch
> > > /usr/src/gnu/lib/csu/../../../contrib/gcc/crtstuff.c:1: error: bad
> > > value (amd64) for -mtune= switch
> > > *** Error code 1
> > >
> > > You see the bottom 4 lines? I see a "bad  value (amd64) for -march=
> > > switch" and a "bad (amd64) for -mtune= switch" . Try changing you
> > > make.conf file to use "CPUTYPE=?hammer", if that works go on to the
> > > next step. If it fails, see if you've got a similar error message.
> > >
> > > Try removing "CPUTYPE=?< whaterver you now > from your make.conf file.
> > > This is probably the way that will work.
> > >
> > > Please, send me this information, I need to know!
> > > What is the supfile you're using?
> > > Have you done a recent cvsup?
> > > Did you dump the refuse file? Please do so if you haven't already, it
> > > takes care of a lot of cvsup problems.
> > > Have you ever done a successful buildworld sequence on the computer?
> > >
> > > Don
> > >
> > > --
> > > Donald J. O'Neill
> > > [EMAIL PROTECTED]
> > >
> > > I'm not totally useless,
> > > I can be used as a bad example.
> > >
> >
> > yep i did it a few times before i could build world and kernel without
> > any troubles.
> > the world i am now using is done that way
> >
> > 7rxI# uname -a
> > FreeBSD 7rxI 5.3-STABLE FreeBSD 5.3-STABLE #0: Tue Nov 30 11:49:43 CET
> > 2004 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/gert  amd64
> > 7rxI#
> >
> 
> it stoped working after a cvsup i will remove the refuse file and do
> some test with the make.conf
> 

###
# supfile #
##

*default tag=RELENG_5
*default host=cvsup15.FreeBSD.org
*default prefix=/usr
*default base=/usr
*default release=cvs
*default delete use-rel-suffix
src-all
ports-all tag=.
doc-all
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: make buildworld error

[Gert Cuykens]

On Sat, 29 Jan 2005 20:33:12 +0100, Gert Cuykens <[EMAIL PROTECTED]> wrote:
> On Sat, 29 Jan 2005 13:27:15 -0600, Donald J. O'Neill
> <[EMAIL PROTECTED]> wrote:
> > On Saturday 29 January 2005 07:55 am, Gert Cuykens wrote:
> > > On Sat, 29 Jan 2005 11:17:59 +0100, Peter Harmsen
> > <[EMAIL PROTECTED]> wrote:
> > > > Seems to me you specified amd64 in /etc/makeconf.
> > > > If i remember correctly from some posts ago this is obsolete.
> > > > You can however switch to 32-bit mode by specifying athlon-xp.
> > > > Otherwise everything should be auto detected by gcc.
> > >
> > > why is this obsolete it always worked that way ?
> >
> > Gert,
> >
> > I had not seen this post until now, and I'm not sure about the question
> > your asking about.
> >
> > It seems to me, he is saying that using "CPUTYPE=?amd64" in your
> > make.conf is obsolete.
> >
> > Your error message would seem to confirm ths
> >
> > cc -O -pipe -march=amd64 -DIN_GCC -DHAVE_LD_EH_FRAME_HDR
> > -finhibit-size-directive -fno-inline-functions  -fno-exceptions
> > -fno-zero-initialized-in-bss  -fno-omit-frame-pointer
> > -fno-unit-at-a-time -I/usr/src/gnu/lib/csu/../../../contrib/gcc/config
> > -I/usr/src/gnu/lib/csu/../../../contrib/gcc -I.
> > -I/usr/src/gnu/lib/csu/../../usr.bin/cc/cc_tools  -g0 -DCRT_BEGIN  -c
> > -o crtbegin.o /usr/src/gnu/lib/csu/../../../contrib/gcc/crtstuff.c
> > /usr/src/gnu/lib/csu/../../../contrib/gcc/crtstuff.c:1: error: bad
> > value (amd64) for -march= switch
> > /usr/src/gnu/lib/csu/../../../contrib/gcc/crtstuff.c:1: error: bad
> > value (amd64) for -mtune= switch
> > *** Error code 1
> >
> > You see the bottom 4 lines? I see a "bad  value (amd64) for -march=
> > switch" and a "bad (amd64) for -mtune= switch" . Try changing you
> > make.conf file to use "CPUTYPE=?hammer", if that works go on to the
> > next step. If it fails, see if you've got a similar error message.
> >
> > Try removing "CPUTYPE=?< whaterver you now > from your make.conf file.
> > This is probably the way that will work.
> >
> > Please, send me this information, I need to know!
> > What is the supfile you're using?
> > Have you done a recent cvsup?
> > Did you dump the refuse file? Please do so if you haven't already, it
> > takes care of a lot of cvsup problems.
> > Have you ever done a successful buildworld sequence on the computer?
> >
> > Don
> >
> > --
> > Donald J. O'Neill
> > [EMAIL PROTECTED]
> >
> > I'm not totally useless,
> > I can be used as a bad example.
> >
> 
> yep i did it a few times before i could build world and kernel without
> any troubles.
> the world i am now using is done that way
> 
> 7rxI# uname -a
> FreeBSD 7rxI 5.3-STABLE FreeBSD 5.3-STABLE #0: Tue Nov 30 11:49:43 CET
> 2004 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/gert  amd64
> 7rxI#
> 

it stoped working after a cvsup i will remove the refuse file and do
some test with the make.conf
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: make buildworld error

[Gert Cuykens]

On Sat, 29 Jan 2005 13:27:15 -0600, Donald J. O'Neill
<[EMAIL PROTECTED]> wrote:
> On Saturday 29 January 2005 07:55 am, Gert Cuykens wrote:
> > On Sat, 29 Jan 2005 11:17:59 +0100, Peter Harmsen
> <[EMAIL PROTECTED]> wrote:
> > > Seems to me you specified amd64 in /etc/makeconf.
> > > If i remember correctly from some posts ago this is obsolete.
> > > You can however switch to 32-bit mode by specifying athlon-xp.
> > > Otherwise everything should be auto detected by gcc.
> >
> > why is this obsolete it always worked that way ?
> 
> Gert,
> 
> I had not seen this post until now, and I'm not sure about the question
> your asking about.
> 
> It seems to me, he is saying that using "CPUTYPE=?amd64" in your
> make.conf is obsolete.
> 
> Your error message would seem to confirm ths
> 
> cc -O -pipe -march=amd64 -DIN_GCC -DHAVE_LD_EH_FRAME_HDR
> -finhibit-size-directive -fno-inline-functions  -fno-exceptions
> -fno-zero-initialized-in-bss  -fno-omit-frame-pointer
> -fno-unit-at-a-time -I/usr/src/gnu/lib/csu/../../../contrib/gcc/config
> -I/usr/src/gnu/lib/csu/../../../contrib/gcc -I.
> -I/usr/src/gnu/lib/csu/../../usr.bin/cc/cc_tools  -g0 -DCRT_BEGIN  -c
> -o crtbegin.o /usr/src/gnu/lib/csu/../../../contrib/gcc/crtstuff.c
> /usr/src/gnu/lib/csu/../../../contrib/gcc/crtstuff.c:1: error: bad
> value (amd64) for -march= switch
> /usr/src/gnu/lib/csu/../../../contrib/gcc/crtstuff.c:1: error: bad
> value (amd64) for -mtune= switch
> *** Error code 1
> 
> You see the bottom 4 lines? I see a "bad  value (amd64) for -march=
> switch" and a "bad (amd64) for -mtune= switch" . Try changing you
> make.conf file to use "CPUTYPE=?hammer", if that works go on to the
> next step. If it fails, see if you've got a similar error message.
> 
> Try removing "CPUTYPE=?< whaterver you now > from your make.conf file.
> This is probably the way that will work.
> 
> Please, send me this information, I need to know!
> What is the supfile you're using?
> Have you done a recent cvsup?
> Did you dump the refuse file? Please do so if you haven't already, it
> takes care of a lot of cvsup problems.
> Have you ever done a successful buildworld sequence on the computer?
> 
> Don
> 
> --
> Donald J. O'Neill
> [EMAIL PROTECTED]
> 
> I'm not totally useless,
> I can be used as a bad example.
> 

yep i did it a few times before i could build world and kernel without
any troubles.
the world i am now using is done that way

7rxI# uname -a
FreeBSD 7rxI 5.3-STABLE FreeBSD 5.3-STABLE #0: Tue Nov 30 11:49:43 CET
2004 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/gert  amd64
7rxI#
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: make buildworld error

[Donald J. O'Neill]

On Saturday 29 January 2005 07:55 am, Gert Cuykens wrote:
> On Sat, 29 Jan 2005 11:17:59 +0100, Peter Harmsen 
<[EMAIL PROTECTED]> wrote:
> > Seems to me you specified amd64 in /etc/makeconf.
> > If i remember correctly from some posts ago this is obsolete.
> > You can however switch to 32-bit mode by specifying athlon-xp.
> > Otherwise everything should be auto detected by gcc.
>
> why is this obsolete it always worked that way ?

Gert,

I had not seen this post until now, and I'm not sure about the question 
your asking about. 

It seems to me, he is saying that using "CPUTYPE=?amd64" in your 
make.conf is obsolete.

Your error message would seem to confirm ths

cc -O -pipe -march=amd64 -DIN_GCC -DHAVE_LD_EH_FRAME_HDR
-finhibit-size-directive -fno-inline-functions  -fno-exceptions
-fno-zero-initialized-in-bss  -fno-omit-frame-pointer
-fno-unit-at-a-time -I/usr/src/gnu/lib/csu/../../../contrib/gcc/config
-I/usr/src/gnu/lib/csu/../../../contrib/gcc -I. 
-I/usr/src/gnu/lib/csu/../../usr.bin/cc/cc_tools  -g0 -DCRT_BEGIN  -c
-o crtbegin.o /usr/src/gnu/lib/csu/../../../contrib/gcc/crtstuff.c
/usr/src/gnu/lib/csu/../../../contrib/gcc/crtstuff.c:1: error: bad
value (amd64) for -march= switch
/usr/src/gnu/lib/csu/../../../contrib/gcc/crtstuff.c:1: error: bad
value (amd64) for -mtune= switch
*** Error code 1

You see the bottom 4 lines? I see a "bad  value (amd64) for -march= 
switch" and a "bad (amd64) for -mtune= switch" . Try changing you 
make.conf file to use "CPUTYPE=?hammer", if that works go on to the 
next step. If it fails, see if you've got a similar error message.

Try removing "CPUTYPE=?< whaterver you now > from your make.conf file. 
This is probably the way that will work.

Please, send me this information, I need to know!
What is the supfile you're using?
Have you done a recent cvsup?
Did you dump the refuse file? Please do so if you haven't already, it 
takes care of a lot of cvsup problems.
Have you ever done a successful buildworld sequence on the computer?

Don

-- 
Donald J. O'Neill
[EMAIL PROTECTED]

I'm not totally useless,
I can be used as a bad example.
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: make buildworld error

[Gert Cuykens]

On Sat, 29 Jan 2005 11:17:59 +0100, Peter Harmsen <[EMAIL PROTECTED]> wrote:
>
> Seems to me you specified amd64 in /etc/makeconf.
> If i remember correctly from some posts ago this is obsolete.
> You can however switch to 32-bit mode by specifying athlon-xp.
> Otherwise everything should be auto detected by gcc.

why is this obsolete it always worked that way ?
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: make buildworld error

[Gert Cuykens]

On Sat, 29 Jan 2005 05:40:25 -0600, Donald J. O'Neill
<[EMAIL PROTECTED]> wrote:

> What do you have in your /usr/src/sys/amd64/conf/config file, show me
> about the first 30 lines of it.

config is the kernel config right ?
i only did make cleanworld and make buildworld wasnt compiling the
kernel yet. I got the error while building world.


# /usr/src/sys/amd64/conf/gert #
###

machine amd64
cpu HAMMER
ident   GERT   

options SCHED_4BSD  # ?
options INET# InterNETworking
options INET6   # IPv6 communications protocols
options FFS # Berkeley Fast Filesystem
options SOFTUPDATES # Enable FFS soft updates support
options UFS_ACL # Support for access control lists
options UFS_DIRHASH # Improve performance on big directories
options MD_ROOT # MD is a potential root device
options NFSCLIENT   # Network Filesystem Client
options NFSSERVER   # Network Filesystem Server
options NFS_ROOT# NFS usable as /, requires NFSCLIENT
options NTFS# NT File System
options MSDOSFS # MSDOS Filesystem
options CD9660  # ISO 9660 Filesystem
options PROCFS  # Process filesystem (requires PSEUDOFS)
options PSEUDOFS# Pseudo-filesystem framework
options GEOM_GPT# GUID Partition Tables.
options COMPAT_IA32 # Compatible with i386 binaries
options COMPAT_FREEBSD4 # Compatible with FreeBSD4
options SCSI_DELAY=15000# Delay (in ms) before probing SCSI
options KTRACE  # ktrace(1) support
options SYSVSHM # SYSV-style shared memory
options SYSVMSG # SYSV-style message queues
options SYSVSEM # SYSV-style semaphores
options _KPOSIX_PRIORITY_SCHEDULING # Posix P1003_1B real-time extensions
options KBD_INSTALL_CDEV# install a CDEV entry in /dev
options AHC_REG_PRETTY_PRINT# Print register bitfields in debug
output.  Adds ~128k to driver.
options AHD_REG_PRETTY_PRINT# Print register bitfields in debug
output.  Adds ~215k to driver.
options ADAPTIVE_GIANT  # Giant mutex is adaptive.
options NO_MIXED_MODE   # SK8N
options ATA_STATIC_ID   # Static device numbering
options UDF # DJO 

device  atpic   # 8259A compatability
device  acpi# Bus support
device  isa # Bus support
device  pci # Bus support
device  fdc # Floppy drives
device  ata # ATA and ATAPI devices
device  atadisk # ATA disk drives
device  ataraid # ATA RAID drives
device  atapicd # ATAPI CDROM drives
device  atapifd # ATAPI floppy drives
device  atapist # ATAPI tape drives
device  scbus   # SCSI bus (required for SCSI)
device  ch  # SCSI media changers
device  da  # Direct Access (disks)
device  sa  # Sequential Access (tape etc)
device  cd  # CD
device  pass# Passthrough device (direct SCSI access)
device  ses # SCSI Environmental Services (and SAF-TE)
device  atkbdc  # AT keyboard controller
device  atkbd   # AT keyboard
device  psm # PS/2 mouse
device  vga # VGA video card driver
device  splash  # Splash screen and screen saver support
device  sc  # syscons is the default console
driver, resembling an SCO console
device  cbb # cardbus (yenta) bridge
device  pccard  # PC Card (16-bit) bus
device  cardbus # CardBus (32-bit) bus
device  sio # 8250, 16[45]50 based serial ports
device  ppc # Parallel port
device  ppbus   # Parallel port bus (required)
device  lpt # Printer
device  plip# TCP/IP over parallel
device  ppi # Parallel port interface device
device  miibus  # RealTek 8129/8139
device  rl  # RealTek 8129/8139
device  loop# Network loopback
device  mem # Memory and kernel memory devices
device  io  # I/O device
device  random  # Entropy device
device  ether   # Ethernet support
device  sl 

Re: make buildworld error

[Donald J. O'Neill]

On Saturday 29 January 2005 02:56 am, Gert Cuykens wrote:
> ...
> cd /usr/src/etc; make buildincludes; make installincludes
> ===> etc/sendmail
> ===> etc/sendmail
>
> --
>
> >>> stage 4.2: building libraries
>
> --
> cd /usr/src;  MAKEOBJDIRPREFIX=/usr/obj  MACHINE_ARCH=amd64
> MACHINE=amd64  CPUTYPE=amd64

< snip >

> -I/usr/src/gnu/lib/csu/../../../contrib/gcc -I.
> -I/usr/src/gnu/lib/csu/../../usr.bin/cc/cc_tools  -g0 -DCRT_BEGIN  -c
> -o crtbegin.o /usr/src/gnu/lib/csu/../../../contrib/gcc/crtstuff.c
> /usr/src/gnu/lib/csu/../../../contrib/gcc/crtstuff.c:1: error: bad
> value (amd64) for -march= switch
> /usr/src/gnu/lib/csu/../../../contrib/gcc/crtstuff.c:1: error: bad
> value (amd64) for -mtune= switch
> *** Error code 1
>
> Stop in /usr/src/gnu/lib/csu.
> *** Error code 1
>
> Stop in /usr/src.
> *** Error code 1
>
> Stop in /usr/src.
> *** Error code 1
>
> Stop in /usr/src.
> *** Error code 1
>
> Stop in /usr/src.
> 7rxI#
>
> how do i fix this ?
> ___
Gert

What do you have in your /usr/src/sys/amd64/conf/config file, show me 
about the first 30 lines of it.

show me your /etc/make.conf file.

Don
-- 
Donald J. O'Neill
[EMAIL PROTECTED]

I'm not totally useless,
I can be used as a bad example.
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: make buildworld 5.3.0

[Lane]

On Sunday 26 December 2004 23:24, jason henson wrote:
> > Finally, start from where you started:
> >
> > cd /usr/src
> > make buildworld
> > make installworld
> > ... etc
> >
> > Make sure you read /usr/src/UPDATING (all the way through) before you
> > restart
> > "make buildworld"
> >
> > good luck!
> > ___
>
> Maybe he doesn't need to read it all the way through?
>
> 2315:
>   4.0 RELEASE shipped.  Please see the 4.0 UPDATING file for how
>   to upgrade to 4.0 from 3.x.
>
> I would recommned ready cooments through Nov after seeing his system
> build date.
>
> Output of uname -a
> FreeBSD sdhawley.eatel.net 5.3-RELEASE FreeBSD 5.3-RELEASE #0: Fri Nov
> 5
> 04:19:18 UTC 2004
>
> Also I would remove /usr/obj to be safe.  It's in the handbook under
> staying current.
>
>
> ___
> freebsd-questions@freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-questions
> To unsubscribe, send any mail to
> "[EMAIL PROTECTED]"
Nah!  Everyone should read UPDATING, and they should read it all the way 
through.  No harm ever resulted from reading it all the way through.  And 
none of the time spent is wasted.

Funny thing is that "COMMON ITEMS" is the very next topic below the 2315 
topic that you cite.  EVERYONE should read COMMON ITEMS, and they should 
probably do so AFTER reading the chronology.  

I probably rebuilt my system three or four times before I actually read it.  
But reading it opened my eyes to features (and potential problems) that I 
never imagined.

Besides!  You missed something of particular import from his uname:

5.3-RELEASE FreeBSD 5.3-RELEASE #0: Fri Nov  5 04:19:18 UTC 2004     
[EMAIL PROTECTED]:/usr/obj/usr/src/sys/GENERIC  i386

His kernel was compiled by [EMAIL PROTECTED], is at level #0 for the 
machine, and it just so happens to be on the very date (Fri, Nov 5) that the 
ISO image for the mini install was compiled -- I know this information 
because I just recently used the mini-install package.  But the point is that 
it made me believe that the OP was building world for the very first time and 
would benefit from fresh sources AND from taking a moment to read about the 
software.

I could be wrong.  I was wrong not to read more before I crashed my system for 
the first time :)

lane
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: make buildworld 5.3.0

[jason henson]

Finally, start from where you started:
cd /usr/src
make buildworld
make installworld
... etc
Make sure you read /usr/src/UPDATING (all the way through) before you
restart
"make buildworld"
good luck!
___
Maybe he doesn't need to read it all the way through?
2315:
4.0 RELEASE shipped.  Please see the 4.0 UPDATING file for how
to upgrade to 4.0 from 3.x.
I would recommned ready cooments through Nov after seeing his system  
build date.

Output of uname -a
FreeBSD sdhawley.eatel.net 5.3-RELEASE FreeBSD 5.3-RELEASE #0: Fri Nov   
5
04:19:18 UTC 2004

Also I would remove /usr/obj to be safe.  It's in the handbook under  
staying current.

___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: make buildworld 5.3.0

[Lane]

On Sunday 26 December 2004 18:45, sdhawley wrote:
> Thanks for any help
> stewart at [EMAIL PROTECTED]
>  Errors at end of make buildworld
> xml.o(.text+0x1764): more undefined references to `xmalloc' follow
> *** Error code 1
>
> Stop in /usr/src/gnu/usr.bin/texinfo/makeinfo.
> *** Error code 1
>
> Stop in /usr/src/gnu/usr.bin/texinfo.
> *** Error code 1
>
> Stop in /usr/src.
> *** Error code 1
>
> Stop in /usr/src.
> *** Error code 1
>
> Stop in /usr/src.
>  Freebsd version # 5.3.0
>  Contents of /var/run/dmesg.boot file attached
>  Output of uname -a
> FreeBSD sdhawley.eatel.net 5.3-RELEASE FreeBSD 5.3-RELEASE #0: Fri Nov  5
> 04:19:18 UTC 2004
> [EMAIL PROTECTED]:/usr/obj/usr/src/sys/GENERIC  i386
>  Thankes stewart
stewart,

It's probably an issue with outdated source.

do this:

cd /usr/ports/net/cvsup-without-gui
make all install clean
rehash

... then create a supfile ... something like this:

ee /etc/cvsupfile (to start the ee editor).  Add the following lines:

*default host=cvsup3.freebsd.org
*default base=/usr
*default prefix=/usr
*default release=cvs tag=RELENG_5_3
*default delete use-rel-suffix
*default compress
src-all

hit  to exit, and save the file.  Then, issue this command from the 
command line:

cvsup -g -L 2 /etc/cvsupfile 

This will update your /usr/src directory with relevant code for FreeBSD 
5.3-RELEASE

Finally, start from where you started:

cd /usr/src
make buildworld
make installworld
... etc

Make sure you read /usr/src/UPDATING (all the way through) before you restart 
"make buildworld"

good luck!
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: make buildworld dies

[Kris Kennaway]

On Sat, Dec 18, 2004 at 11:49:53AM -0500, Zachary Huang wrote:
> Sorry for so many questions. On yet another FreeBSD (4.2), I  first
> did a sysinstall to upgrade to 5.10, it messed up everything because
> the source (/usr/src) did not match all the config files, so sendmail
> complains a lot and cannot ssh or telnet to the system.  I then did a
> cvsup (without specify which release, simply "cvs") successfully (took
> like 10 hrs),  then today I tried to
> 
> cd /usr/src
> make buildworld
> 
> after about 8 min,  it stopped with the following error:
> cc -O -pipe -DSHELL -I .I/usr/src/bin/sh -Wall -Wfont (? cannot see my
> own writing) -c /usr/src/bin/sh
> /usr/src/bin/sh/mknodes.c:101.
> initializer element is not constant
> ***error code 1
> Stop in /usr/src/bin/sh
> *** error code 1
> stop in /usr/src.
> 
> now I am sort of stuck.  I made a new kernel the day before the
> sysinstall, but now I cannot even try compile a new kernel because it
> compains the config file is newer than what it wants.
> 
> is my system totally messed up?  right now apache still works, but I
> can telnet or ssh out but to the host

It sounds like you're a bit confused about what you're doing..first,
there is no "FreeBSD 5.10", so it's not clear what you're aiming for,
and secondly it looks like you didn't go through the documented
upgrade procedure (see handbook) so you ended up with some kind of
broken partially-upgraded system.  The best thing for you to do would
be to grab the installation media for the release you want to install,
and reinstall over the top of your broken system.

Kris


pgpJ6nHqKb76V.pgp
Description: PGP signature

Re: make buildworld dies

[Joshua Lokken]

On Sat, 18 Dec 2004 11:49:53 -0500, Zachary Huang <[EMAIL PROTECTED]> wrote:
> Sorry for so many questions. On yet another FreeBSD (4.2), I  first
> did a sysinstall to upgrade to 5.10, 

Wha?  4.2 is very old. and 5.3 is the latest production release.
I'll assume the above is a typo for 4.10.  I'm not certain that
you can directly upgrade from 4.2 to 4.10, but in any case, you
want to read /usr/src/UPGRADING.

> it messed up everything because
> the source (/usr/src) did not match all the config files, so sendmail
> complains a lot and cannot ssh or telnet to the system.  I then did a
> cvsup (without specify which release, simply "cvs") successfully (took
> like 10 hrs)

I don't believe this is what you wanted to do.  If you're going to
track a particular release, let's say 4.10, then you want to use
the appropriate cvs tag for that src tree, which for 4.10 release
will be RELENG_4_10.
 
> cd /usr/src
> make buildworld
> 
> after about 8 min,  it stopped with the following error:
> cc -O -pipe -DSHELL -I .I/usr/src/bin/sh -Wall -Wfont (? cannot see my
> own writing) -c /usr/src/bin/sh
> /usr/src/bin/sh/mknodes.c:101.
> initializer element is not constant
> ***error code 1
> Stop in /usr/src/bin/sh
> *** error code 1
> stop in /usr/src.

That seems reasonable.
 
> now I am sort of stuck.  I made a new kernel the day before the
> sysinstall, but now I cannot even try compile a new kernel because it
> compains the config file is newer than what it wants.

It sounds like your src tree needs to be cleaned up (# rm -rf /usr/src/*)
and that you should read the Handbook chapter on using cvsup, write
yourself a src-supfile, or use one of the examples, and then follow the
well-documented procedure for upgrading your system from source.
 
> is my system totally messed up?  

Probably, but the handbook is a great resource, and will help you
to prevent it from happening again.

> right now apache still works, but I can telnet or ssh out but to the host

Wow, I'm surprised that Apache is still able to run ;)

-- 
Joshua Lokken
Open Source Advocate
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: make buildworld failing

[Vonleigh Simmons]

try rm'ing your source tree and re-cvsup'ing
Lo
How could u do that? I'm interesting coz I've also got some problems
cd /usr/src
rm -rf *
Then follow the instructions in the handbook for cvsup:

Vonleigh Simmons

___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: make buildworld failing

[Guillaume R.]

>>>While trying to update to 5.3 stable, buildworld errors out on
>>>
>>> me. I'm
>>> running FreeBSD 5.2.1-RELEASE-p11. Following is part of the output,
>>> if you need more output please let me know. No luck looking up the
>>> errors in google, so your help is appreciated.
>>
>> try rm'ing your source tree and re-cvsup'ing
Lo
How could u do that? I'm interesting coz I've also got some problems
thx
>
>   Worked like a charm. Thanks.
>
> Vonleigh Simmons
> 
>
> ___
> [EMAIL PROTECTED] mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-questions
> To unsubscribe, send any mail to
> "[EMAIL PROTECTED]"



___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: make buildworld failing

[Vonleigh Simmons]

   While trying to update to 5.3 stable, buildworld errors out on 
me. I'm
running FreeBSD 5.2.1-RELEASE-p11. Following is part of the output, if
you need more output please let me know. No luck looking up the errors
in google, so your help is appreciated.
try rm'ing your source tree and re-cvsup'ing
Worked like a charm. Thanks.
Vonleigh Simmons

___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: make buildworld failing

[luke]

On Sun, 5 Dec 2004 17:09:18 -0800, Vonleigh Simmons
<[EMAIL PROTECTED]> wrote:
>While trying to update to 5.3 stable, buildworld errors out on me. I'm
> running FreeBSD 5.2.1-RELEASE-p11. Following is part of the output, if
> you need more output please let me know. No luck looking up the errors
> in google, so your help is appreciated.

try rm'ing your source tree and re-cvsup'ing
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: make buildworld failed at suidperl

[Matthias Teege]

On Wed, Nov 10, 2004 at 12:09:26PM +0200, Nelis Lamprecht wrote:

> Have you tried cvsuping from another source ?

Yes, didn't help.

> NOPERL=true

The make buildworld work but make buildkernel exit with:

===> snp
@ -> /usr/src/sys
machine -> /usr/src/sys/i386/include
perl @/kern/vnode_if.pl -h @/kern/vnode_if.src
Internal error at @/kern/vnode_if.pl line 248,  chunk 120.
*** Error code 255

Stop in /usr/src/sys/modules/snp.
*** Error code 1

Stop in /usr/src/sys/modules.
*** Error code 1

Stop in /usr/obj/usr/src/sys/BULLET.
*** Error code 1


Matthias


-- 
Matthias Teege -- http://www.mteege.de
make world not war
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: make buildworld failed at suidperl

[Nelis Lamprecht]

On Wed, 10 Nov 2004 10:26:51 +0100, Matthias Teege
<[EMAIL PROTECTED]> wrote:
> Moin,
> 
> I try a cd /usr/src && make buildworld.
> 
> It fails with:
> 
> cc -O -pipe -I/usr/src/gnu/usr.bin/perl/suidperl/../../../../contrib/perl5 
> -I/usr/obj/usr/src/gnu/usr.bin/perl/suidperl -DIAMSUID-c sperl.c
> Global symbol "$dir" requires explicit package name at 
> /usr/obj/usr/src/gnu/usr.bin/perl/suidperl/lib/ExtUtils/MM_Unix.pm line 128.
> BEGIN not safe after errors--compilation aborted at 
> /usr/obj/usr/src/gnu/usr.bin/perl/suidperl/lib/ExtUtils/MM_Unix.pm line 242.
> BEGIN failed--compilation aborted at Makefile.PL line 1.
> *** Error code 255

Hi,

Have you tried cvsuping from another source ?

Otherwise..

I'm guessing that this is version 4.x of FreeBSD based on the fact
it's using perl5. To bypass the building of perl in the base system
you can add the following to /etc/make.conf

NOPERL=true

You can then build perl5.8 from ports afterwards and run use.perl ports.


Nelis
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: make buildworld.........24 hours????

[Chuck Swiger]

Brian Bobowski wrote:
Chuck Swiger wrote:
Using -j is recommended only when you have lots of memory and can keep 
all of the processes resident in memory.  Trying to run a parallel 
build on a low-memory machine is almost certainly going to be much 
slower, since you are going to swap more, not less.
[ ... ]
Ah, thanks for the clarification. I'd seen it cited as a way to deal 
with the delay caused by file access, but I guess it does make sense 
that it would apply to the actual filesystem rather than swap.
There's that point, too.  FreeBSD will happily cache all of the header files 
and such in memory if it can, rather than re-reading them from disk all of the 
time.  Adding more memory to this machine will do more for your dollar to 
improve the performance of the system, then anything else you can do.

--
-Chuck
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: make buildworld.........24 hours????

[Brian Bobowski]

Chuck Swiger wrote:
Using -j is recommended only when you have lots of memory and can keep 
all of the processes resident in memory.  Trying to run a parallel 
build on a low-memory machine is almost certainly going to be much 
slower, since you are going to swap more, not less.

Time it for yourself and see...
Ah, thanks for the clarification. I'd seen it cited as a way to deal 
with the delay caused by file access, but I guess it does make sense 
that it would apply to the actual filesystem rather than swap.

-BB
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: make buildworld.........24 hours????

[Chuck Swiger]

Brian Bobowski wrote:
[ ... ]
   One thing I have to wonder - how compatible is 'make buildworld' with
   multiple build processes(e.g. 'make -j4 buildworld')? I know some
   makefiles don't get along well with the -j parameter, but if
   buildworld is okay with it, this may offer a way to keep the processor
   busy rather than waiting for disk access all the time, which could
   make things faster, especially on such low-memory machines.
Using -j is recommended only when you have lots of memory and can keep all of 
the processes resident in memory.  Trying to run a parallel build on a 
low-memory machine is almost certainly going to be much slower, since you are 
going to swap more, not less.

Time it for yourself and see...
--
-Chuck
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"