Re: Problems with OpenOffice compile after upgrade from 5.2.1 to 5.3
Selon Peter Olsson <[EMAIL PROTECTED]>:
> I recently upgraded from 5.2.1-p{something} to 5.3-p5.
> The system seems fine after the upgrade, but I have one problem.
>
> The reason for the upgrade to 5.3 was to be able to compile
> OpenOffice, but when I tried to do that I got an error in the
> dmake part stating that the file types.h didn't exist. While
> searching for the cause of this problem I ended up in the directory
> /usr/local/lib/gcc-lib/i386-portbld-freebsd5.2.1/3.2.3, where
> I moved away the whole include directory. Then the OpenOffice
> compile could finish the dmake part and continue.
>
> Later in the compile I got errors because the include directory
> was missing, so I moved it back. Now I get the error below about
> types.h.
>
> I think that the problem has to do with the fact that the files
> in /usr/local/lib/gcc-lib/ seem to be from the 5.2.1 release I had
> before upgrading. Why haven't these files been upgraded and how can
> I fix the problem?
>
> (I have to admit that I didn't go to single user before upgrading,
> I just killed almost all of the processes without [] in the ps list.
> This might be the cause of the problem.)
>
> I have successfully compiled some other applications after the upgrade,
> so the gcc-lib/i386-portbld-freebsd5.2.1 problem doesn't seem to break
> everything.
>
> Here is the current error:
>
> cd ./unxfbsd.pro/misc/build/STLport-4.5/src && gmake -f gcc-3.0-freebsd.mak
> -j1 && touch so_built_so_stlport
> g++32 -D_REENTRANT -fexceptions -I../stlport
>
-DGXX_INCLUDE_PATH=/usr/local/lib/gcc-lib/i386-portbld-freebsd5.2.1/3.2.3/include/g++-v3
> -Wall -W -Wno-sign-compare -Wno-unused -Wno-uninitialized -ftemplate-depth-32
> -fPIC dll_main.cpp -c -o ../lib/obj/GCC-FREEBSD/ReleaseD/dll_main.o
> In file included from /usr/include/pthread.h:42,
> from ../stlport/pthread.h:26,
> from ../stlport/stl/_threads.h:74,
> from ../stlport/stl/_alloc.h:64,
> from ../stlport/memory:28,
> from dll_main.cpp:38:
>
/usr/local/lib/gcc-lib/i386-portbld-freebsd5.2.1/3.2.3/include/sys/types.h:251:
> syntax
> error before `;' token
> In file included from ../stlport/stl/_vector.h:572,
> from ../stlport/vector:36,
> from dll_main.cpp:39:
> ../stlport/stl/_bvector.h:37:1: warning: "__WORD_BIT" redefined
> In file included from /usr/include/sys/limits.h:36,
> from /usr/include/limits.h:128,
> from
> /usr/local/lib/gcc-lib/i386-portbld-freebsd5.2.1/3.2.3/include/limits.h:132,
> from
> /usr/local/lib/gcc-lib/i386-portbld-freebsd5.2.1/3.2.3/include/syslimits.h:7,
> from
> /usr/local/lib/gcc-lib/i386-portbld-freebsd5.2.1/3.2.3/include/limits.h:11,
> from /usr/include/pthread.h:45,
> from ../stlport/pthread.h:26,
> from ../stlport/stl/_threads.h:74,
> from ../stlport/stl/_alloc.h:64,
> from ../stlport/memory:28,
> from dll_main.cpp:38:
> /usr/include/machine/_limits.h:95:1: warning: this is the location of the
> previous definition
> gmake: *** [../lib/obj/GCC-FREEBSD/ReleaseD/dll_main.o] Fel 1
> dmake: Error code 2, while making
> './unxfbsd.pro/misc/build/so_built_so_stlport'
> ---* TG_SLO.MK *---
>
> ERROR: Error 65280 occurred while making
> /usr/ports/editors/openoffice-1.1-se/work/stlport
> dmake: Error code 1, while making 'instsetoo/prj/build_all'
> *** Error code 255
>
> Stop in /usr/ports/editors/openoffice-1.1-se.
> ---* TG_SLO.MK *---
>
> Thanks!
>
> --
> Peter Olsson[EMAIL PROTECTED]
> ___
> freebsd-stable@freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-stable
> To unsubscribe, send any mail to "[EMAIL PROTECTED]"
>
I'd like to help you with my few knowledge in FreeBSD. I just have to tell that
I compiled openoffice-1.1.4 yesterday but on a fresh 5.3 install and no problem
(just 15 hours, is that normal?).
sorry for this quite useless post but if I could help, just ask.
Regards, Ivan.
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Save the Demon!
Freddie Cash a écrit : On February 8, 2005 03:31 pm, Thomas T. Veldhouse wrote: Can this be true? Are they really looking to kill the FreeBSD demon? This borders on sacrilege. http://bsd.slashdot.org/article.pl?sid=05/02/09/1955251&from=rss Read the advocacy archives for posts from Robert Watson and Anthony Atkielsky. These (along with a bunch of other well-written posts) will clear things up very quickly. http://lists.freebsd.org/pipermail/freebsd-adcocacy/2005-February/ The main points to remember: a mascot and a logo are not the same thing, and the logo will be used IN ADDITION TO the mascot. And, *this contest is not even live yet*. Check the text on http://logo-contest.freebsd.org sorry to say that but I agree to kill the daemon for 500$. Oups, didn't want to say that, sorry :) sorry to ask that but which software could I use to produce vectorial graphics? Quite newbie to freebsd, don't know such free software. (won't annoy you with such useless questions I promess, just don't know where to ask). have a good night. Ivan (france) ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
compile kernel problem
I got problems when trying to compile my new kernel on 5.3-release. I didn't go to stable yet cause I never did it (really new to unix...) and I heard that it was better to customize the system first (?). But when I put a # before lines I don't need like all RAID and SCSI options, kernel don't want to make properly. Can somebody helps? Or is it a question for another list? thanks, Ivan ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: compile kernel problem
I just try it again cause I didn't want to annoy anybody and it worked! (?) I left the SCSI lines cause I use an iPod (and it seems to be an SCSI drive inside). I commented all the RAID lines and compilation succeeded. Now can you tell me how to be sure that my kernel conf is optimized? I attached my actual kernel. Thanks for your help, I really appreciate it. my physical conf is: AMD Sempron 2400+ (slowed at 1333 MHz cause of only PC 2100 DDR) ASUS A7V8X-X motherboard asus DVD writer 80 GB maxtor HDD one floppy drive ATI Radeon 64 MB DDR VIVO (if VIVO is useable on freeBSD I'd like to know how :) I think I didn't forget anything. Thanks, Ivan. # # TENSHI -- Generic kernel configuration file for FreeBSD/i386 # # For more information on this file, please read the handbook section on # Kernel Configuration Files: # # http://www.FreeBSD.org/doc/en_US.ISO8859-1/books/handbook/kernelconfig-config.html # # The handbook is also available locally in /usr/share/doc/handbook # if you've installed the doc distribution, otherwise always see the # FreeBSD World Wide Web server (http://www.FreeBSD.org/) for the # latest information. # # An exhaustive list of options and more detailed explanations of the # device lines is also present in the ../../conf/NOTES and NOTES files. # If you are in doubt as to the purpose or necessity of a line, check first # in NOTES. # # $FreeBSD: src/sys/i386/conf/GENERIC,v 1.413.2.6.2.2 2004/10/24 18:02:52 scottl Exp $ machine i386 cpu I686_CPU ident TENSHI # To statically compile in device wiring instead of /boot/device.hints #hints "GENERIC.hints" # Default places to look for devices. options CPU_ENABLE_SSE # used by DVD options USER_LTD# used by many apps options SCHED_4BSD # 4BSD scheduler 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 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_43 # Compatible with BSD 4.3 [KEEP THIS!] options COMPAT_FREEBSD4 # Compatible with FreeBSD4 options SCSI_DELAY=5000 # 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. device apic# I/O APIC # Bus support. Do not remove isa, even if you have no isa slots device isa device eisa device pci device sound device "snd_emu10k1" # Floppy drives device fdc # ATA and ATAPI devices device ata 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 options ATA_STATIC_ID # Static device numbering # SCSI Controllers device ahb # EISA AHA1742 family device ahc # AHA2940 and onboard AIC7xxx devices device ahd # AHA39320/29320 and onboard AIC79xx devices device amd # AMD 53C974 (Tekram DC-390(T)) device isp # Qlogic family device mpt # LSI-Logic MPT-Fusion #device ncr # NCR/Symbios Logic device sym
Re: compile kernel problem
no, I don't think so. I read carefully the handbook's section and I quote it: SCSI controllers. Comment out any you do not have in your system. If you have an IDE only system, you can remove these altogether. SCSI peripherals. Again, comment out any you do not have, or if you have only IDE hardware, you can remove them completely. Supported RAID controllers. If you do not have any of these, you can comment them out on http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/kernelconfig-config.html or remove them. first I didn't use my ipod so I removed all that lines and it didn't work. I don't think the number of commented lines is limited...am I wrong? Nevermind, the problem is solved since I compiled it succesfully just with RAID off. Now can somebody help me about configuring my kernel in a more personal way? I forgot to mention that I have two Ethernet cards on PCI slots and one on the motherboard. I also have a sound card. I hope I am not too boring. Just tell it if I am. Thanks. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: compile kernel problem
Kris Kennaway wrote: On Thu, Feb 10, 2005 at 02:39:38AM +0100, Ivan Roth wrote: no, I don't think so. I read carefully the handbook's section and I quote it: I said to read the comments in the GENERIC kernel, not the handbook. e.g. if you commented out SCSI support, you probably left in the USB mass storage device (umass), which requires SCSI and will leave your kernel uncompilable. Kris ok. I didn't know that and should have read more carrefully :) but it doesn't matter since I realized I need the SCSI support. But for example, do I need to keep all the lines for the SCSI peripherals or can I keep just some of them. How to know if iPod need this one or this other line? ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Adding an usb harddisk
Doug White a écrit : On Thu, 10 Feb 2005, Jack Raats wrote: I want to add an usb harddisk. Acoording to fdisk it's formatted as a "NTFS/HPFS/QNX" disk Can I add this disk and still using this file system? NTFS is a Windows filesystem. You can't install FreeBSD to it but you can mount and use the volume. See the mount_ntfs manpage for restrictions on our NTFS support. You can mount it using 'mount -t ntfs /dev/da /' if you don't want to make a UFS filesystem. (replace with device name and with desired mountpoint.) If you do want to reformat it for UFS, see the article on formatting media at www.freebsd.org for instructions. What kind of dev/fstab do I need to add? Its like an existing one, just change the filesystem type from 'ufs' to 'ntfs'. Do I need an extra swap slice? How to make one? Not unless you want one, but if you do you probably need to destroy the NTFS filesystem to make space. I'm using FreeBSD 4.11. NTFS support there may not be as mature as the one in 5.x. just note that it could not be /dev/da but /dev/ad, e.g, da is only for SCSI disks and ad is for IDE ones. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
