summaryrefslogtreecommitdiffstats
path: root/cpukit/libcsupport (unfollow)
Commit message (Collapse)AuthorFilesLines
1999-10-05Patch from Wayne Bullaughey <wayne@wmi.com>. Comments follow:Joel Sherrill1-1/+1
I'm working on code to mount my host based file system on the base file system (imfs) and have a suggestion for a change to eval.c in the c/src/lib/libc directory of the 8/20/1999 snapshot. The current version does not test the result value returned from the evalpath callback (line 47) in the case where follow_link is true. Attached is my suggested change. Without this test the node_type callback may be called after evalpath failed. node_type could set the type to some value other then RTEMS_FILESYSTEM_HARD_LINK or RTEMS_FILESYSTEM_SYM_LINK but it seems cleaner to add the check on result.
1999-10-04Patch from Ralf Corsepius <corsepiu@faw.uni-ulm.de> to make fix bugJoel Sherrill1-3/+3
where wrapup left pieces out of the librtemsall.a.
1999-10-04Patch from Ralf Corsepius <corsepiu@faw.uni-ulm.de> to make fix bugJoel Sherrill1-1/+1
where wrapup left pieces out of the librtemsall.a.
1999-10-04Patch from Ralf Corsepius <corsepiu@faw.uni-ulm.de> to make libnetworkingJoel Sherrill1-8/+1
a top level more independently configured package.
1999-10-04Patch from Ralf Corsepius <corsepiu@faw.uni-ulm.de>:Joel Sherrill1-3/+2
The patch below actuallly consists of two patches: 1) moving librpc to c/src/librpc similar to what has been done to librtems++ 2) reworked configure scripts, many safety and dependency checks added to aclocal/*.m4 macros + configuration fixes. To apply: mkdir c/src/librpc mkdir c/src/librpc/src cp c/src/lib/librpc/*.c c/src/librpc/src cp c/src/lib/librpc/Makefile.in c/src/librpc/src mkdir c/src/librpc/include mkdir c/src/librpc/include/rpc cp c/src/lib/include/rpc/* c/src/librpc/include/rpc patch -p1 < ../rtems-rc-19990820-7.diff rm -rf c/src/lib/librpc rm -rf c/src/lib/include/rpc ./autogen The additional checks in aclocal/*m4 macros add rather restrictive, sometimes unnecessarily restrictive constraints on the sequence of how macros can be used in a configure.in script. Adding them has let my problems with some more complicated configuration options vanish. Apparently some macros had not been in the required order . ---- Now I still get some linking errors for some cpus and bsps, esp when linking cdtest, but also at other locations: e.g. this happens for mips64orion/p4600: # make[5]: Entering directory `/lfs/poseidon/users/rtems/src/multi/build/mips64orion-rtems/c/p4600/tests/samples/hello' /opt/rtems/bin/mips64orion-rtems-gcc --pipe -B../../../../../../p4600/lib/ -specs bsp_specs -qrtems -DP4000 -DCPU_R4000 -DP3_DIAG -D_R4000 -D__mips=3 -mcpu=4600 -G0 -I../../../../../../p4600/lib/include/networking -g -Wall -ansi -fasm -O4 -fomit-frame-pointer -o o-p4600/hello.exe o-p4600/init.o ../../../../../../p4600/lib/no-dpmem.rel ../../../../../../p4600/lib/no-event.rel ../../../../../../p4600/lib/no-msg.rel ../../../../../../p4600/lib/no-mp.rel ../../../../../../p4600/lib/no-part.rel ../../../../../../p4600/lib/no-signal.rel ../../../../../../p4600/lib/no-timer.rel ../../../../../../p4600/lib/no-rtmon.rel /opt/rtems/mips64orion-rtems/lib/libc.a(dtoa.o): In function `_dtoa_r': /opt/hermes/embedded/build/build-mips64orion-tools/mips64orion-rtems/newlib/libc/stdlib/../../../../../src/newlib/libc/stdlib/dtoa.c:348: relocation truncated to fit: R_MIPS_LITERAL no symbol /opt/hermes/embedded/build/build-mips64orion-tools/mips64orion-rtems/newlib/libc/stdlib/../../../../../src/newlib/libc/stdlib/dtoa.c:348: relocation truncated to fit: R_MIPS_LITERAL no symbol /opt/hermes/embedded/build/build-mips64orion-tools/mips64orion-rtems/newlib/libc/stdlib/../../../../../src/newlib/libc/stdlib/dtoa.c:348: relocation truncated to fit: R_MIPS_LITERAL no symbol collect2: ld returned 1 exit status # mips64orion-rtems-gcc -v Reading specs from /opt/rtems/lib/gcc-lib/mips64orion-rtems/2.95.1/specs gcc version 2.95.1 19990816 (release) # mips64orion-rtems-ld -v GNU ld version 2.9.5 (with BFD 2.9.5)
1999-10-01Addition of more functionality by Eric Norum to support GNU readline.Joel Sherrill3-2/+77
1999-09-07Applied patch rtems-rc-19990820-6.diff.gz fromJoel Sherrill1-0/+28
Ralf Corsepius <corsepiu@faw.uni-ulm.de> which converted many Makefile.in's to Makefile.am's. This added a lot of files.
1999-08-18 Patch from Ralf Corsepius <corsepiu@faw.uni-ulm.de>:Joel Sherrill1-4/+0
Here is another fix, which addresses a few more or less severe bugs in configuration and unix/posix: * Configuration fix: c/src/lib/configure.in didn't handle RDBG correctly * Configuration fix: make depend was non-functional in c/src/lib/libc/Makefile.in * Configuration fix: stray comment removed from aclocal/target.m4 * RTEMS fix: termios support for unix/posix now uses the host's headers only (was completely broken). - Don't install RTEMS's newlib sys/termios.h for unix (sys/termios.h apparently is a newlib specific header) - To be able to compile RTEMS's termios.c with glibc2.1, glibc-2.1 needs __USE_MISC, which is a private define from gcc's features.h, being defined only when _BSD_SOURCE of _SVID_SOURCE is defined. RTEMS's termios apparently implements BSD, thus -D_BSD_SOURCE was added to Linux-posix.cfg. - Conflicting definitions for __USE_MISC and _BSD_SOURCE inside of RTEMS codes removed due to definition of _BSD_SOURCE on the toplevel. This fix has been tested with linux/posix (primary glibc2.1 native), linux/posix (secondary libc5 native), sh/gensh1, i386/pc386 and a couple of other bsp's/CPU. To apply: cd <srcdir> patch -p1 < rtems-rc-19990709-9.diff and aclocal -I aclocal && automake && autoconf cd c/src/lib; autoconf or ./autogen
1999-07-02Added code to initialize the /etc/group and /etc/passwd files.Joel Sherrill2-0/+91
1999-07-02Fixed format strings and warnings.Joel Sherrill2-9/+9
1999-07-02Reentrant versions added by Joel. Signficant formatting cleanup.Joel Sherrill2-115/+176
1999-07-02Password and group routines added by Ralf Corsepius <corsepiu@faw.uni-ulm.de>.Joel Sherrill2-0/+248
1999-06-15After comments D. V. Henkel-Wallace <gumby@zembu.com>, the interface toJoel Sherrill3-37/+5
mount() was changed to avoid the use of a string as the options.
1999-06-14RTEMS_FILESYSTEM_READ_WRITE_ONLY changed to RTEMS_FILESYSTEM_READ_WRITEJoel Sherrill2-2/+2
for simplicity.
1999-06-14Wrong prototype corrected.Joel Sherrill1-1/+1
1999-06-14Warning removal from D. V. Henkel-Wallace <gumby@zembu.com>.Joel Sherrill1-0/+6
1999-06-11Added local prototype of ioctl() to avoid requiring sys/ioctl.h.Joel Sherrill3-3/+9
1999-06-09Switched to using strcasecmp() since it is more portable.Joel Sherrill1-2/+2
D. V. Henkel-Wallace <gumby@zembu.com> spotted this one.
1999-05-27Split out the routine rtems_assoc_name_bad().Joel Sherrill2-14/+41
1999-05-27Removed usage of printf.Joel Sherrill1-1/+1
1999-05-27Split initialization and reserve resources from termios to reduceJoel Sherrill3-59/+93
size of mininum application.
1999-05-11Fix based on bug report from Jay Kulpinski <jskulpin@eng01.gdds.com>Joel Sherrill1-1/+11
that the per task reentrancy structure was not being processed properly during exit(). joel@oarcorp.com wrote: > > > This is always an ugly place to poke around. :( > > The code in newlib/libc/stdlib/exit.c walks the atexit chain for the > reentrancy structure for JUST the current task. The code in libc_wrapup() > does it for both the current task and the global reentrancy structure > (which tends to be where driver atexit()'s were registered. > > So I think the _wrapup_reent(0) in libc_wrapup() should be commented out. > > If you concur, then I will make the change and improve the comment on this > line of code to explain things: > > libc_wrapup(); /* Why? XXX */ > > --joel That does the job. cdtest.exe works correctly now.
1999-04-22Added lstat().Joel Sherrill2-6/+39
1999-04-15Added reentrant versions.Joel Sherrill2-0/+41
1999-04-15Updated version string.Joel Sherrill1-2/+1
1999-04-01Disable IXON by default based on comment from Eric NorumJoel Sherrill1-1/+1
<e.norum@sk.sympatico.ca> and concerns from Thomas Doerfler <td@imd.m.ISAR.de> when he submitted the patch: Since enabling XON/XOFF has such a major performance hit on `smart' output devices I think it should be *off* by default. I think some thought should be given to adding hooks for hardware that can support XON/XOFF without software intervention, or for hardware like the 68360 SCC's that can use large buffers, but still handle special characters immediately. The patch you sent is a very good start, though. I just think that the software flow control should be off -- to match the way the serial I/O support has worked up until now.
1999-03-31Patch from Thomas Doerfler <td@imd.m.ISAR.de> to add flow control:Joel Sherrill1-32/+272
Some lines for "documentation": ====================================== One thing should be noted: when XON/XOFF is enabled, the serial device will always work with one-character buffers, so the interrupt load for the CPU might get higer, especially on devices like MC68360 and MPC860, where the serial channels are capable of using big buffers. But, once again, this only happens when XON/XOFF is actually selected. Please note that the flag IXON is set by default, so outgoing XON/XOFF flow control is enabled by default. XON/XOFF is controlled using the "standard" fields IXON/IXOFF in the termios structure. The termios flag IXANY is not (yet) supported. Hardware handshake for the incoming data stream is controlled using the standard flag CRTSCTS. If this flag is set, whenever the receive buffer is almost full, the driver function "device.stopRemoteTx()" is called, when the receive buffer has more space available, "device.startRemoteTx()" is called again. If the driver does not provide these interface functions (entries in device structure are NULL pointers), then these calls are suppressed. Changes of the flow control options during operation should work at any time, but this has not been extensively tested. No changes to the device driver interface are needed. ================================================ One critical point when using this patch might be, that any BSP using this version of termios will now have outgoing flow control enabled by default, so the behaviour of these BSPs will change here. The option IXON has already been set in older termios by default, but it did not work until this patch. Maybe this option should be switched off by default, what do you think?
1999-03-31Removed asserts that shouldn't be called and commented case where thisJennifer Averett1-1/+0
indicates an internal error.
1999-03-31Corrected return value.Jennifer Averett1-1/+1
1999-03-30Removed warning for const removal.Joel Sherrill1-1/+1
1999-03-29Removed an uninitialized variable.Jennifer Averett1-4/+5
1999-03-24 Fix based on bug report from Ralf Corsepius <corsepiu@faw.uni-ulm.de>:Joel Sherrill1-0/+25
There seems to be an ugly dependency between posix-headers and libcsupport. Configuring rtems with ../rtems-rc-19990324-0/configure \ --target=i386-rtems \ --prefix=<somewhere> \ --disable-posix "make RTEMS_BSP=pc386" results into: [...] /opt/rtems/bin/i386-rtems-gcc --pipe -B/users/rtems/src/multi/build/pc386/lib/ -specs bsp_specs -qrtems -I/users/rtems/src/multi/build/pc386/lib/include/networking -g -Wall -ansi -fasm -O4 -fomit-frame-pointer -c -o o-pc386/utime.o ../../../../../rtems-rc-19990324-0/c/src/lib/libc/utime.c In file included from ../../../../../rtems-rc-19990324-0/c/src/lib/libc/utime.c:16: /opt/rtems/i386-rtems/include/utime.h:4: sys/utime.h: No such file or directory ../../../../../rtems-rc-19990324-0/c/src/lib/libc/utime.c:24: warning: `struct utimbuf' declared inside parameter list ../../../../../rtems-rc-19990324-0/c/src/lib/libc/utime.c:24: warning: its scope is only this definition or declaration, ../../../../../rtems-rc-19990324-0/c/src/lib/libc/utime.c:24: warning: which is probably not what you want. ../../../../../rtems-rc-19990324-0/c/src/lib/libc/utime.c: In function `utime': ../../../../../rtems-rc-19990324-0/c/src/lib/libc/utime.c:34: dereferencing pointer to incomplete type ../../../../../rtems-rc-19990324-0/c/src/lib/libc/utime.c:34: dereferencing pointer to incomplete type make[4]: *** [o-pc386/utime.o] Error 1 make[3]: *** [all] Error 1 make[2]: *** [all] Error 1 make[1]: *** [all] Error 1 make[1]: Leaving directory `/lfs/poseidon/users/rtems/src/multi/build/c' make: *** [all] Error 1 Apparently sys/utime.h is one of the posix headers and therefore gets not installed (I suppose this is correct). IMO, this probably indicates that sys/utime.h has to be moved to another include subdirectory and should not be part of the posix-package. [AFAIK, sys/*.h are system dependent headers, so why should it be a posix-header? - Hmm]
1999-03-19Another cleanup patch for the previous rejected hunk.Joel Sherrill1-0/+1
1999-03-19A cleanup patch on fcntl.c from Eric Norum <eric@skatter.usask.ca> forJoel Sherrill1-0/+2
2 lines of code that did not get included when Joel tried to manually add a rejected patch.
1999-03-19Patch from Eric Norum <eric@skatter.usask.ca> that adds externalJoel Sherrill2-24/+42
fcntl support and an external fcntl handler for sockets.
1999-03-16Use proper include for libio.h.Joel Sherrill5-8/+5
1999-03-08Added code to translate internal libio flags to POSIX style flags.Joel Sherrill1-3/+20
1999-03-08Added support for F_GETFL and F_SETFL.Joel Sherrill1-2/+3
1999-03-06Added F_GETFL support so the fdopen() implementation in newlib 1.8.1Joel Sherrill3-2/+39
would work. At the same time, the initial implementation of F_SETFL was added. A support routine was added to convert internal libio flags back to the POSIX style. Eventually the internal representation should be eliminated in the interest of simplicity and code reduction. This problem was reported by Jake Janovetz <janovetz@tempest.ece.uiuc.edu>.
1999-03-01Patch from Eric Norum <eric@skatter.usask.ca> to eliminate externalJoel Sherrill16-244/+26
IO handlers scheme that was implemented originally just to support sockets. The file system IO switch is more general and works fine.
1999-02-24Changed IMFS to use IMFS_NAME_MAX as the maximum length of a basenameJoel Sherrill1-1/+5
rather then NAME_MAX. NAME_MAX is 255 and that lets IMFS chew up memory too fast. Perhaps in the future, the places in IMFS that put a maximum length name string on the stack and the jnode structure does not include a maximu length name string can be fixed so this is not a problem.
1999-02-18GLobal reentrancy structure is now dynamically initialized.Joel Sherrill1-1/+2
1999-02-15Patch from Eric Valette <valette@crf.canon.fr> to undo the patchJoel Sherrill1-2/+0
that added ifdef on the pc386.
1999-02-10Set the read/write offset to 0 when the file is opened. The ACVC had a testJoel Sherrill1-0/+1
that performed the sequence open/write/close/open/read/close on a file. It did not get the correct result since the file descriptor was reused.
1999-02-10Added getcwd().Joel Sherrill1-0/+280
1999-02-05Corrected spacing and added some new error checks that were neededJoel Sherrill2-15/+25
to avoid dereferencing NULLs.
1999-01-28Patch from Eric Norum <eric@skatter.usask.ca> to set more flags inJoel Sherrill1-2/+2
rtems_bsdnet_makeFdForSocket().
1999-01-26Added libio_sockets.c to hold support routines for networking code.Joel Sherrill1-0/+58
1999-01-20More general fix based on bug report and patch from Ian Lance TaylorJoel Sherrill13-1/+27
<ian@airs.com> to fix this problem: There is a small bug in __rtems_close in c/src/lib/libc/libio.c. It does not check whether the file descriptor it is passed is open. This can cause it to make a null dereference if it is passed a file descriptor which is in the valid range but which was not opened, or which was already closed.
1999-01-19Per bug report from Jiri Gaisler that RTEMS would no longer buildJoel Sherrill1-1/+13
with the --disable-posix option, stubs for some routines (_getpid_r and _kill_r) that are normally defined with POSIX were added.
generated by cgit v1.2.3 (git 2.25.1) at 2024-05-06 14:19:43 +0000