http://pflog.net/~floyd/gpac-libgpac.patch
Oops, if anyone grabbed that patch, grab it again, I ran the diff
against the wrong original Makefile that had my --disable-opengl
hard-coded in there during testing.
Sorry for the trouble.
Josh
___
Hi Mel,
Sorry for not getting back to you earlier, I have been out of the office
for some time...
Does this one also have a link UP message after nfs mounting? If not,
then
there's your culprit: network isn't up at mountcritremote time. You
should
mark it 'late' in fstab
The UP message came
On Tuesday 10 February 2009 01:34:47 Arjan van der Oest wrote:
Hi Mel,
Sorry for not getting back to you earlier, I have been out of the office
for some time...
Does this one also have a link UP message after nfs mounting? If not,
then
there's your culprit: network isn't up at
Hello,
I need to run a Linux 32Bit IDL-7.0 binary (IDL vm) on a
FreeBSD-8.0-CURRENT/amd64 box. Does anyone out here already performed
that task and is willing and able giving some hints?
Thanks in advance,
Oliver
___
freebsd-questions@freebsd.org
Im currently running AMD64 4gig FreebSD7.1-STABLE .. below is the error
msg when trying to compile the new KDE4.2 KDEBASE
--
[ 0%] Building CXX object
apps/lib/konq/CMakeFiles/konq.dir/konq_popupmenuinformation.o
cd /usr/ports/x11/kdebase4/work
Mel wrote:
- why does the system tries to mount the nfs filesystem from the
fstab
while nfs_client_enable has been set to no in rc.conf?
Because there is no relation between the two. You could be using a 3rd
party nfs kernel module.
Yes, but I am not. I'm using the default kernel option which
amd64] NFS mount in fstab hangs
duringmountcritremote execution
Mel wrote:
- why does the system tries to mount the nfs filesystem from the
fstab
while nfs_client_enable has been set to no in rc.conf?
Because there is no relation between the two. You could be using a 3rd
party nfs kernel module
On Friday 30 January 2009 04:36:04 Arjan van der Oest wrote:
Mel wrote:
- why does the system tries to mount the nfs filesystem from the
fstab
while nfs_client_enable has been set to no in rc.conf?
Because there is no relation between the two. You could be using a 3rd
party nfs kernel
Hi,
I’m puzzled and either I don’t understand the boot rc.d process or there is
something wrong with it ☺
I have this 7.1-RELEASE-p2 amd64 machine compiled with a GENERIC kernel, so NFS
support is baked right into the kernel by default. In fsstab I have this entry:
nfs server ip:/data/nfs
...@freebsd.org
[mailto:owner-freebsd-questi...@freebsd.org] On Behalf Of Arjan van der Oest
Sent: donderdag 29 januari 2009 10:48
To: freebsd-questions@freebsd.org
Subject: [7.1-RELEASE-p2 amd64] NFS mount in fstab hangs duringmountcritremote
execution
Hi,
I’m puzzled and either I don’t understand
On Thursday 29 January 2009 00:47:49 Arjan van der Oest wrote:
Hi,
I’m puzzled and either I don’t understand the boot rc.d process or there is
something wrong with it ☺
I have this 7.1-RELEASE-p2 amd64 machine compiled with a GENERIC kernel, so
NFS support is baked right into the kernel
This may turn out to be a PR, but I'll check here quickly first and if I
have no success I'll send to the -po...@.
I tried installing kino from ports on an amd64 system but got the
following errors after a few hours of building:
In file included from h264.h:32,
from h264.c:31
systems while installing 7.x, quite
possibly while upgrading from 6.3. When this occurred, I was also
moving from i386 to amd64; Is there some kind of offset for partition
tables which may change based on architecture?
Lastly, here's a screenshot of the partition editor:
http
installing 7.x, quite possibly
while upgrading from 6.3. When this occurred, I was also moving from
i386 to amd64; Is there some kind of offset for partition tables which
may change based on architecture?
Lastly, here's a screenshot of the partition editor:
http://people.collaborativefusion.com
The booting process stops at the line mounting root ufs /dev/md0
(Starting with the option for no acpi )
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to
there is a hardware problem. The system currently boots
Windows XP fine. I installed Ubuntu 8.10 AMD64 sucessfully and it runs find.
I am at a loss of how to proceed.
Brent
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo
, 10. Dezember 2008 18:30
To: Hell, Robert
Cc: freebsd-questions@freebsd.org
Subject: Re: PostgreSQL on FreeBSD 7.0 amd64 with more than 2GB shared
memory
fails again with ENOMEM.
Is there any easy way to use a shared memory segment which is larger
than 2GB?
getting two smaller
for GDB. Type show warranty for details.
This GDB was configured as amd64-marcel-freebsd...
Unread portion of the kernel message buffer:
kernel trap 12 with interrupts disabled
Fatal trap 12: page fault while in kernel mode
cpuid = 0; apic id = 00
fault virtual address = 0xb4
fault code
#4 0x804da163 in trap_fatal (frame=0xff0001ae06e0,
eva=Variable eva is not available.
)
at ../../../amd64/amd64/trap.c:764
#5 0x804da535 in trap_pfault (frame=0xa53818f0,
usermode=0)
at ../../../amd64/amd64/trap.c:680
#6 0x804dae85 in trap (frame
Hi,
I'm trying to run PostgreSQL 8.3 on a FreeBSD 7.0 amd64 server with more
than 2GB shared memory. The machine has 32GB RAM installed.
After setting kern.ipc.shmmax and kern.ipc.shmall to the appropriate
values, I still had no chance to start postgres with more than 2GB of
shared memory.
I
fails again with ENOMEM.
Is there any easy way to use a shared memory segment which is larger
than 2GB?
getting two smaller ? :)
no idea - maybe it's bug of SHM. as you already checked it please do
sent-pr
___
freebsd-questions@freebsd.org mailing
: PostgreSQL on FreeBSD 7.0 amd64 with more than 2GB shared
memory
fails again with ENOMEM.
Is there any easy way to use a shared memory segment which is larger
than 2GB?
getting two smaller ? :)
no idea - maybe it's bug of SHM. as you already checked it please do
sent-pr
Hello I have updated my server (Intel Modular server) using the
classical
# freebsd-update install
And I am now facing very weired issues only on amd64 servers I am
maintaining.
Servers boots and then freezes when It launch ipfilter. This is not
a low level freeze, simply all access
.
Le 25 nov. 08 à 16:27, bsd a écrit :
Hello I have updated my server (Intel Modular server) using the
classical
# freebsd-update install
And I am now facing very weired issues only on amd64 servers I am
maintaining.
Servers boots and then freezes when It launch ipfilter. This is
not a low
the last few
months, so it's pretty close. Also, the i386 is a direct replacement
of the amd64 to fix this and other problems, so the software
settings set is pretty identical also...
kqemu crawls when I boot amd64 (and I notice the processor is always
over 50%), and it's reasonalbly usable
Hello BSD guys,
My system information is like this.
- FreeBSD 7.0-RELEASE amd64
- gcc 4.2.1
- gdb 6.1.1
- eclipse-cdt-3.1.2_1
I used ports tree to compile and install eclipse-cdt-3.1.2_1.
Running eclipse and compiling my C++ project are fine.
But, when I try to debug, an error dialog box pops up
Forwarded Message: Re: yelp install error on amd64 running
freebsd 6.3
Tuesday, November 4, 2008 7:32 PM
From:
Mel [EMAIL
On Tuesday 04 November 2008 19:19:44 Dino Vliet wrote:
Dear freebsd people,
who is able to help me with this problem I have on my machine (a amd64
system running freebsd 6.3).
What did you do back in April, when you had the exact same problem?
--
Mel
Problem with today's modular software
I'm not comparing apples-to-apples exactly, but both my disks are in
the same system, both are running 7-stable from within the last few
months, so it's pretty close. Also, the i386 is a direct replacement
of the amd64 to fix this and other problems, so the software
settings set is pretty
close. Also, the i386 is a direct replacement
of the amd64 to fix this and other problems, so the software
settings set is pretty identical also...
kqemu crawls when I boot amd64 (and I notice the processor is always
over 50%), and it's reasonalbly usable on i386 (also, the processor is
often
PROTECTED] wrote:
I'm not comparing apples-to-apples exactly, but both my disks are in
the same system, both are running 7-stable from within the last few
months, so it's pretty close. Also, the i386 is a direct replacement
of the amd64 to fix this and other problems, so the software
settings set
it's pretty close. Also, the i386 is a direct replacement
of the amd64 to fix this and other problems, so the software
settings set is pretty identical also...
kqemu crawls when I boot amd64 (and I notice the processor is always
over 50%), and it's reasonalbly usable on i386 (also
on the host cpu. An amd64 compatible processor can't run
32-bit code in 64-bit mode and vice-versa, so it's either doing some
emulation or switching back and forth between 32/64-bit modes.
___
freebsd-questions@freebsd.org mailing list
http
Hello list,
I want your opinion about migrating a freebsd server to amd64.
I have the following configuration:
Motherboard: Intel S5000VSA
CPU: Intel Xeon E5335 @ 2Ghz
RAM: 2 x 1Gb DDR2 FB-DIMM 667Mhz
HDD: 2 x 320 Gb SATA II + 1 x 500 Gb SATA II
This server runs as a web / mail server using
while it's strange you haven't installed amd64 at first place, why
migrating WORKING thing? if it works fine - don't touch.
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send
On Mon, Oct 27, 2008 at 1:56 PM, Wojciech Puchar
[EMAIL PROTECTED] wrote:
while it's strange you haven't installed amd64 at first place, why
migrating WORKING thing? if it works fine - don't touch.
I didn't install amd64 from the start because my knowledge at the time
I installed the server
On Mon, Oct 27, 2008 at 10:10:19AM +0100, Valentin Bud wrote:
Hello list,
I want your opinion about migrating a freebsd server to amd64.
I have the following configuration:
Motherboard: Intel S5000VSA
CPU: Intel Xeon E5335 @ 2Ghz
RAM: 2 x 1Gb DDR2 FB-DIMM 667Mhz
HDD: 2 x 320 Gb SATA II
Hi all,
I have a fresh install of FBSD 7 amd64, and I want to run some
legacy binaries from my old box (Fbsd 5.x i386).
Searching the archives, I found this message:
On Tue, 19 Aug 2008, Oliver Fromme wrote:
|Christopher Joyner wrote:
| Is there some way of doing
On Fri 2008-10-24 14:03:42 UTC-0200, [EMAIL PROTECTED] ([EMAIL PROTECTED])
wrote:
I have a fresh install of FBSD 7 amd64, and I want to run some
legacy binaries from my old box (Fbsd 5.x i386).
I don't run 64-bit FreeBSD but from what I've read elsewhere, you can
install 32-bit binary
When I try to run the binaries, the following error message is
displayed:
ELF interpreter /libexec/ld-elf32.so.1 not found
Abort
I found the following tip to install 32bits libraries:
cd /usr/src
make build32
make install32
ldconfig -32 /usr/lib32
Is that enough?
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
mv wrote:
Hello Greg,
When I tried to upgrade kmymoney2 on my amd64 6.4-PRERELEASE using
portmaster I also received the same error message as Dino. However,
after I amended the Makefile as you had suggested portmaster worked as
it should
Hello Greg,
When I tried to upgrade kmymoney2 on my amd64 6.4-PRERELEASE using
portmaster I also received the same error message as Dino. However,
after I amended the Makefile as you had suggested portmaster worked as
it should.
Just wanted to let you know that you seem to be on the right
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Dino Vliet wrote:
Hi Greg
Here the tow output file pkg_info_output.txt and the Makefile
as attachments because otherwise this messsage would be too
large (I know that the freebsd mailinglist will not let my
message through)
Brgds
Hi freebsd peeps,
Who can help me sort this error out when I try to installl kmymoney2 on my
amd64 system. The error I get is:
test ! -f sk.gmo || touch sk.gmo
rm -f es_AR.gmo; /usr/local/bin/msgfmt -o es_AR.gmo ./es_AR.po
test ! -f es_AR.gmo || touch es_AR.gmo
rm -f pt_BR.gmo; /usr/local/bin
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Dino Vliet wrote:
Hi freebsd peeps,
Who can help me sort this error out when I try to installl kmymoney2 on my
amd64 system. The error I get is:
test ! -f sk.gmo || touch sk.gmo
rm -f es_AR.gmo; /usr/local/bin/msgfmt -o es_AR.gmo ./es_AR.po
Hi All,
when I start opera on my amd64 machine running freebsd 6.3 I get the following
warning message on my console:
[: missing ]
grep: ]: No such file or directory
exec: /usr/local/share/opera/bin//operapluginwrapper.linux: not found
opera: Search operapluginwrapper: No response from wrapper
4364
files in cache124696
cache size 2.1 Gbytes
max cache size 15.0 Gbytes
For the benefit of anyone that didn't follow the previous thread, the
issue was that in building 32-bit libraries under amd64, extra
arguments get
On Monday 22 September 2008 04:55:39 Brian wrote:
Has there been any change in the above? On a single core i386, the
documentation described notes work properly. However, on a AM2 based
machine with the amd64 version of freebsd (both 6.4 Beta and 7.0 show
this behavior) I consistently get
On Thursday 25 September 2008 12:50:25 Mel wrote:
On Monday 22 September 2008 04:55:39 Brian wrote:
Has there been any change in the above? On a single core i386, the
documentation described notes work properly. However, on a AM2 based
machine with the amd64 version of freebsd (both 6.4
Ok, cracked it. ccache will dump core, if the argument list 255 arguments,
most likely because the page size is 2048 bytes, but I'm guessing here. What
happens in x_realloc is that it wants to copy the 2048+8 from the old pointer
to the new, yet the old pointer is only 2040 bytes big.
I think
On Thursday 25 September 2008 21:03:12 Brian wrote:
[EMAIL PROTECTED] /usr/ports/devel/ccache]# make
=== Patching for ccache-2.4_7
=== Applying FreeBSD patches for ccache-2.4_7
patch: malformed patch at line 9: sizeof(char *));
= Patch patch-args.c failed to apply cleanly.
Result of
On Wednesday 24 September 2008 05:34:22 Brian wrote:
/usr/local/libexec/ccache/world-cc -m32 -march=athlon64 -mfancy-math-387
-DCOMPAT_32BIT -iprefix /usr/obj/usr/src/lib32/usr/
-L/usr/obj/usr/src/lib32/usr/lib32 -B/usr/obj/usr/src/lib32/usr/lib32
-fpic -DPIC -O2 -fno-strict-aliasing -pipe
Mel wrote:
On Wednesday 24 September 2008 05:34:22 Brian wrote:
/usr/local/libexec/ccache/world-cc -m32 -march=athlon64 -mfancy-math-387
-DCOMPAT_32BIT -iprefix /usr/obj/usr/src/lib32/usr/
-L/usr/obj/usr/src/lib32/usr/lib32 -B/usr/obj/usr/src/lib32/usr/lib32
-fpic -DPIC -O2
On Wednesday 24 September 2008 16:28:44 Brian wrote:
Mel wrote:
On Wednesday 24 September 2008 05:34:22 Brian wrote:
/usr/local/libexec/ccache/world-cc -m32 -march=athlon64 -mfancy-math-387
-DCOMPAT_32BIT -iprefix /usr/obj/usr/src/lib32/usr/
-L/usr/obj/usr/src/lib32/usr/lib32
variable set in /etc/profile.
For the benefit of anyone that didn't follow the previous thread, the
issue was that in building 32-bit libraries under amd64, extra
arguments get passed to the compiler inside the CC variable
definition, hence the problem with overriding CC/CXX. I doubt that those
updated
/libexec/ccache/world-cc,1}
CXX := ${CXX:C,^c\+\+,/usr/local/libexec/ccache/world-c++,1}
If this is what amd64 peeps should be using, can the docs be updated?
Brian
.endif
I have tried the above 3 times on 6.4 Beta releases. It always fails at
the same point in the same way.
/usr/local
On Tuesday 23 September 2008 18:35:22 Brian wrote:
/usr/local/libexec/ccache/world-cc -m32 -march=i686 -mmmx -msse -msse2
-mfancy-math-387 -DCOMPAT_32BIT -iprefix /usr/obj/usr/src/lib32/usr/
-L/usr/obj/usr/src/lib32/usr/lib32 -B/usr/obj/usr/src/lib32/usr/lib32
-fpic -DPIC -O2
Mel wrote:
On Tuesday 23 September 2008 18:35:22 Brian wrote:
/usr/local/libexec/ccache/world-cc -m32 -march=i686 -mmmx -msse -msse2
-mfancy-math-387 -DCOMPAT_32BIT -iprefix /usr/obj/usr/src/lib32/usr/
-L/usr/obj/usr/src/lib32/usr/lib32 -B/usr/obj/usr/src/lib32/usr/lib32
-fpic -DPIC -O2
Brian wrote:
Mel wrote:
On Tuesday 23 September 2008 18:35:22 Brian wrote:
/usr/local/libexec/ccache/world-cc -m32 -march=i686 -mmmx -msse -msse2
-mfancy-math-387 -DCOMPAT_32BIT -iprefix /usr/obj/usr/src/lib32/usr/
-L/usr/obj/usr/src/lib32/usr/lib32 -B/usr/obj/usr/src/lib32/usr/lib32
-fpic
Has there been any change in the above? On a single core i386, the
documentation described notes work properly. However, on a AM2 based
machine with the amd64 version of freebsd (both 6.4 Beta and 7.0 show
this behavior) I consistently get the below error.
=== lib/csu/i386-elf (obj,depend
Brian wrote:
Has there been any change in the above? On a single core i386, the
documentation described notes work properly. However, on a AM2 based
machine with the amd64 version of freebsd (both 6.4 Beta and 7.0 show
this behavior) I consistently get the below error.
=== lib/csu/i386-elf
I've been trying to find anything that fits the
bill. My only
requirements are:
* That it works with amd64 (on FreeBSD, obviously).
* That it supports Xvideo.
* That it has decent 2D performance.
* That it works with wide screen resolutions (so I
guess basically
modern hardware + modern
Mel [EMAIL PROTECTED] wrote:
On Thursday 18 September 2008 16:44:40 Nash Nipples wrote:
thanks for the new /etc/rc.d/ntpd
...
rc_flags=-c ${ntpd_config} ${ntpd_flags}
...
what we can learn from it is that on 7.1 BETA your rc.conf.local file
should look like this
Hey,
I've been trying to find anything that fits the bill. My only
requirements are:
* That it works with amd64 (on FreeBSD, obviously).
* That it supports Xvideo.
* That it has decent 2D performance.
* That it works with wide screen resolutions (so I guess basically
modern hardware + modern
On Fri, 19 Sep 2008, Peter Schuller wrote:
I've been trying to find anything that fits the bill. My only
requirements are:
* That it works with amd64 (on FreeBSD, obviously).
* That it supports Xvideo.
* That it has decent 2D performance.
* That it works with wide screen resolutions (so I
/ntp.drift
on my second machine 7.1-BETA amd64, the same configuration produces
this error
--
:/etc/rc.d/ntpd start
Starting ntpd.
ERROR: only one configfile option allowed
ntpd - NTP daemon program - Ver. 4.2.4p5
USAGE: ntpd [ -flag [val
-
If I comment out the
ntpd_flags=-c /etc/ntp.conf -p
/var/run/ntpd.pid
line.
ntp starts without any error.
Should I accept this or is something wrong?
Thanks
/Leslie
Looks like it wants only one parameter as a flag in
thanks for the new /etc/rc.d/ntpd
...
rc_flags=-c ${ntpd_config} ${ntpd_flags}
...
what we can learn from it is that on 7.1 BETA your rc.conf.local file should
look like this
ntpd_config=/etc/ntpd.conf
ntpd_flags=-p /var/run/ntpd.pid
hope that explains
Nash
On Thursday 18 September 2008 16:44:40 Nash Nipples wrote:
thanks for the new /etc/rc.d/ntpd
...
rc_flags=-c ${ntpd_config} ${ntpd_flags}
...
what we can learn from it is that on 7.1 BETA your rc.conf.local file
should look like this
ntpd_config=/etc/ntpd.conf
ntpd_flags=-p
Here's my uname -a:
FreeBSD fbsd.its1.localhost.com 7.0-RELEASE FreeBSD 7.0-RELEASE #0: Sun Feb
24 10:35:36 UTC 2008
[EMAIL PROTECTED]:/usr/obj/usr/src/sys/GENERIC
amd64
Error upon running adduser:
pwd_mkdb: 14 uid is incorrect
pwd_mkdb: /etc/master.passwd: Inappropiate file type or format
pw
:
Here's my uname -a:
FreeBSD fbsd.its1.localhost.com 7.0-RELEASE FreeBSD 7.0-RELEASE #0: Sun Feb
24 10:35:36 UTC 2008
[EMAIL PROTECTED]:/usr/obj/usr/src/sys/GENERIC
amd64
Error upon running adduser:
pwd_mkdb: 14 uid is incorrect
pwd_mkdb: /etc/master.passwd: Inappropiate file type or format
pw_mkdb -p /etc/master.passwd
Cheers!
Subhro
On Fri, Sep 12, 2008 at 2:09 PM, Froilan Romualdo [EMAIL PROTECTED] wrote:
Here's my uname -a:
FreeBSD fbsd.its1.localhost.com 7.0-RELEASE FreeBSD 7.0-RELEASE #0: Sun Feb
24 10:35:36 UTC 2008
[EMAIL PROTECTED]:/usr/obj/usr/src/sys/GENERIC
amd64
library: jpeg.9 - found
=== ghostscript8-8.62_5 depends on shared library: png.5 - found
=== ghostscript8-8.62_5 depends on shared library: vga.1 - not found
=== Verifying install for vga.1 in /usr/ports/graphics/svgalib
=== svgalib-1.4.3_5 is only for i386, while you are running amd64.
*** Error
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Dino Vliet wrote:
| Hi folks,
Hello,
|
| On my adm64 dualcore system running freebsd 7 I want to install
/usr/ports/multmedia/kino. However the port stops because of this:
[snip]
| === svgalib-1.4.3_5 is only for i386, while you are running amd64
/svgalib
=== svgalib-1.4.3_5 is only for i386, while you are running amd64.
Try cd'ing to /usr/ports/print/ghostscript8, then run make config and
make sure the two SVGALIB options are unselected. They should be about
15 lines from the top:
[ ] GS_lvga256 D: SVGAlib, 256-color VGA modes
I'm running 7-stable on an x86-64 card in an ibm server and was
wondering if anyone else was, or in a similar environment, and has IO
errors on the shared disk. The errors do not happen all the time, not
even under heavy load, it seems to be at random. Shared disk presents
itself as an LSI
Hi all,due to this opera errer I get when I want to test the working of my java
browser plugin I get a message that libjvm.so is not found on my amd64 box
running freebsd 7.The commands I type are:[EMAIL PROTECTED] /usr/ports/math]#
ldd /usr/local/diablo-jdk1.6.0/jre/lib/amd64/libjava.so
/usr
On Thu, Aug 28, 2008 at 5:16 PM, Wojciech Puchar
[EMAIL PROTECTED] wrote:
Now, I'm sure, as usual, I'm being naive, but:
1) We can run 32-bit linux on amd64, so do we have 32-bit freebsd libs
already?
yes.
2) If we don't have the 32-bit libs, is it possible to steal them
base system's
Hi,
Something seems to be wrong with my current 7.0/amd64 setup.
# sudo portupgrade -Rra
Sometimes portupgrade stops while Updating the portsdb [1].
OK, actually it doesn't really stop, with top I see that the
ruby18 process is eating up the whole CPU[2].
In the current case it's about
On Thu, Aug 28, 2008 at 5:16 PM, Wojciech Puchar
[EMAIL PROTECTED] wrote:
Now, I'm sure, as usual, I'm being naive, but:
1) We can run 32-bit linux on amd64, so do we have 32-bit freebsd libs
already?
yes.
2) If we don't have the 32-bit libs, is it possible to steal them
base system's
being naive, but:
1) We can run 32-bit linux on amd64, so do we have 32-bit freebsd libs already?
2) If we don't have the 32-bit libs, is it possible to steal them
directly from the corresponding i386 freebsd (as long as we haven't
rebuilt our kernel too many times), or should we in all cases
Now, I'm sure, as usual, I'm being naive, but:
1) We can run 32-bit linux on amd64, so do we have 32-bit freebsd libs already?
yes.
2) If we don't have the 32-bit libs, is it possible to steal them
base system's 32-bit libs are installed by default, for older version
through compat6x,5x
Hi there,
I've recently got a chance to run a rather modern CPU and mobo for a
few weeks, and since the beast is 8GB worth of RAM, I figured amd64
would fit nicely in it.
After updating to HEAD to trying usual make world/kernel magic, the
following issues arised I haven't seen previously in i386
Hello,
I made some strange experiences in running OpenLDAP 2.4.11 on both i386
and amd64 architectures of the most recent FreeBSD 7.0-STABLE.
I already setup and run three servers (fourth is coming soon). Two of
them are based on FreeBSD amd64, one is based on i386. The do have
almost
VeeJay wrote:
For following hardware, I am wonderting that which Freebsd amd64, ia64 or
i386 to install?
Hardware:
Dell PowerEdge 2950 III having 2 x CPU 3,0 GHz Intel Xeon L5450 Quad-Core
2x6MB cache WITH 16 GB RAM.
Tools:
1. FreeBSD 7 Production Release
2. Apache 2.2.9
3
Hi guys
For following hardware, I am wonderting that which Freebsd amd64, ia64 or
i386 to install?
Hardware:
Dell PowerEdge 2950 III having 2 x CPU 3,0 GHz Intel Xeon L5450 Quad-Core
2x6MB cache WITH 16 GB RAM.
Tools:
1. FreeBSD 7 Production Release
2. Apache 2.2.9
3. MySQL 5.1.26
4. PHP 5.2.6
Considering the amount of RAM in the box, AMD64 would prob be best for your
needs.
If you need 32-bit software or features go with i386 instead but you wont have
access to all the RAM
ia64 is for Itanium-based systems only
Date: Mon, 25 Aug 2008 23:39:07 +0200
From: [EMAIL PROTECTED
Christopher Joyner wrote:
Is there some way of doing that? Running i386 software on amd64 machine?
Yes. FreeBSD/amd64 contains a compatibility facility
for i386 binaries. It should just work out of the box,
unless disabled explicitly.
Best regards
Oliver
--
Oliver Fromme, secnetix GmbH
Date: Tue, 19 Aug 2008 16:05:06 +0200 From: [EMAIL PROTECTED] To:
freebsd-questions@FreeBSD.ORG; [EMAIL PROTECTED] CC: Subject: Re: Is it
possible to run i386 only, on a amd64 freebsd 7? Christopher Joyner
wrote: Is there some way of doing that? Running i386 software on amd64
Sean Cavanaugh [EMAIL PROTECTED] wrote:
he was asking about ports that are labled as i386 only
Well, he didn't mention building ports. He only said
*running* i386 software on amd64, which is certainly
possible.
Whether i386 only packages will run on amd64 depends
on the reason why they're
Christopher Joyner wrote:
Is there some way of doing that? Running i386 software on amd64 machine?
Yes. FreeBSD/amd64 contains a compatibility facility
for i386 binaries. It should just work out of the box,
unless disabled explicitly.
Best regards
Oliver
Ok I see, I understand that I
Christopher Joyner wrote:
Ok I see, I understand that I am able to run i386 software on my amd64
(Pentium D).
Because of the error message i386 only, how do I make it install?
Do I use a force switch?
I am going to try some things after posting this.
You didn't mention that you
Christopher Joyner wrote:
Ok I see, I understand that I am able to run i386 software on my amd64
(Pentium D).
Because of the error message i386 only, how do I make it install?
Do I use a force switch?
I am going to try some things after posting this.
You didn't mention that you want
Sean Cavanaugh [EMAIL PROTECTED] wrote:
he was asking about ports that are labled as i386 only
Well, he didn't mention building ports. He only said
*running* i386 software on amd64, which is certainly
possible.
Whether i386 only packages will run on amd64 depends
on the reason why they're
O.K I understand that. So I can see that unless I have an i386 FreeBSD
build, I really cannot
install those i386 only software titles.
In that situation I assume I can only use amd64 ports and software.
I have an idea though, would it be possible to build a i386 FreeBSD on an
another
is compiled twice; once from /usr/src/lib/csu/amd64/crt1.c, and
// a second time from /usr/src/lib/csu/i386-elf/crt1.c. If LIB32 is
// disabled in src.conf, only the first compilation takes place. If the
// generated hash values are the same, by some chance, then the actual
// problem is that the file
Is there some way of doing that? Running i386 software on amd64 machine?
In Love in Jesus Christ, Or Lord and Savior.
For God so loved the world, that he gave his only *begotten Son, that whosoever
believeth in him should not perish, but have everlasting life.
--John 3:16
On Fri, 15 Aug 2008 11:22:01 -0400
Maxim Khitrov [EMAIL PROTECTED] wrote:
I think what's happening is that there is a collision in hash values
generated by ccache. That's the only thing I can think of, because
crt1.c is compiled twice; once from /usr/src/lib/csu/amd64/crt1.c, and
a second
On Thu, 14 Aug 2008 16:04:52 -0400
Maxim Khitrov [EMAIL PROTECTED] wrote:
This is an old problem, but so far I haven't been able to find a
solution. When ccache is used to build world on amd64, the process
fails when /usr/src/lib/csu/i386-elf/crt1.c is compiled. If
WITHOUT_LIB32 is added
On Fri, Aug 15, 2008 at 10:48 AM, RW [EMAIL PROTECTED] wrote:
On Thu, 14 Aug 2008 16:04:52 -0400
Maxim Khitrov [EMAIL PROTECTED] wrote:
This is an old problem, but so far I haven't been able to find a
solution. When ccache is used to build world on amd64, the process
fails when /usr/src/lib
801 - 900 of 2012 matches
Mail list logo
