| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Here is the result of my nightly work to get RTEMS_ROOT=$srcdir working
with different shells and relative/absolute paths.
What I did is relatively simple in principle:
Instead of setting RTEMS_ROOT in configure.in and then let configure
substitute @RTEMS_ROOT@ inside the Makefiles, I now let each Makefile
set RTEMS_ROOT from each Makefile's @top_srcdir@ value.
The difference is subtile, but with enormous side effects:
- If RTEMS_ROOT is set in configure, then the same single value will be
propagated to all Makefiles. This breaks using relative paths, as the
relative path to the root of the source tree is used inside of all
subdirectory Makefiles.
- Now each Makefile.in sets RTEMS_ROOT = @top_srcdir@. top_srcdir is
computed individually by configure for each single Makefile.in, hereby
receiving the correct value, no matter if relative or absolute paths are
used.
To get this working, I needed to remove setting RTEMS_ROOT from
target.cfg.in, because this overrides the value of RTEMS_ROOT from each
individual Makefile.
Furthermore, I removed RTEMS_CUSTOM from the Makefiles and replaced all
"include $(RTEMS_CUSTOM)" directives with"include
$(RTEMS_ROOT)/make/custom/$(RTEMS_BSP)". Perhaps you don't like this,
but I think, to have one variable less is clearer and easier to
understand than having several variables refering to the next one.
I enclose a small patch to this mail, which
- fixes the config.h problem (to finally clearify misunderstands)
- removes assignment/subsitution of RTEMS_ROOT from configure.in
- contains a workaround for the application Makefile's RTEMS_ROOT
problem (reported by Eric)
- removes some unused lines from the toplevel Makefile.in
- removes assignment of RTEMS_ROOT from make/target.cfg.in
|
| |
|
| |
|
| |
|
|
|
|
| |
be one paragraph with manual line breaks rather than multiple paragraphs..
|
|
|
|
| |
suggestion.
|
|
|
|
|
| |
There's an explicit invocation of `make' in c/Makefile.in. This
breaks for those of us with different `gmake' and `make' programs.
|
|
|
|
|
|
|
| |
> 4) The toplevel Makefile.in contains rules named make_subdir and
> clean_modules, which probably can be deleted, IMO.
> At least make_subdir doesn't give any sense anymore. (I had removed it
> im my original patch).
|
| |
|
|
|
|
| |
by Ralf Corsepius
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
doing the HWAPI manual.
|
| |
|
| |
|
| |
|
|
|
|
|
| |
direction. This fixes a problem reported by Steve Evans of Radstone
since he is using glibc2.
|
| |
|
|
|
|
| |
generated when egcs is used with "-Wall -pedantic".
|
|
|
|
| |
Application Cindy has written can transform into a nice Word document.
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
| |
With this in place, it is possible to fdopen a TCP stream socket and
getc/fprintf/etc. on the STDIO stream!
|
|
|
|
|
|
|
|
|
|
| |
> RTEMS is under CVS control and has been since rtems 3.1.16 which was
> around May 1995. So I just to add the $Id$. If you notice other files
> with missing $Id$'s let me know. I try to keep w\up with it.
Now that you have asked -- I'll attach a list of files lacking an RCS-Id to
this mail. This list has been generated by a little sh-script I'll also
enclose.
|
|
|
|
|
|
| |
+ major and minor number elements in rtems_termios_open.
+ arg->ioctl_return in rtems_termios_ioctl routine.
|
|
|
|
|
| |
lines so setting RTEMS_BSP in an environment variable works even
from the top level directory.
|
|
|
|
|
|
|
|
|
|
|
| |
RTEMS_CHECK_FILES_IN uses a sequence of find, sort and sed to collect
all *.in files in a given subdirectory.
The current version uses : `find $1 -name $2 -print | sed 's%\.in%%' |
sort` with $1 being a subdirectory $2 set to Makefile.in.
This works as long all subdirectories start with a letter that is
lexically bigger than the letter M, but will fail otherwise.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
>> >>There is a 30 day error in _TOD_Days_since_last_leap_year[2..3]
>> >
>> >Thanks.
>> >What's the condition to hit this error?
>> >Every year 4n+2 and 4n+3 ?
>> >(i.e. 1998, 1999, 2002, 2003, ...)
>> >
>> OK: 96 97 00 01 04 05 ...
>> Bad: 98 99 02 03 06 07 ...
There is also a problem in newlib 1.7.x reported at the same time:
>> I found another, that would strike only on 2/29/2000, or other leapyears.
>> Only a problem on 1 day.
>>
>> Joel: FYI, there is a bug in Newlib localtime.c, localtime or (_tm_time).
>> Ours is modified for dst and timezones, but the bug was in original source.
>> I have not looked at the latest public source (nor do I know where to find
>> it).
|
| |
|
|
|
|
|
|
|
| |
configuration successfully.
Added code to detect configuring macros and POSIX API at the same time.
There is no macro implementation for the POSIX API.
|
|
|
|
| |
for the network driver attach entry point.
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
|
| |
for GNAT. It was the number of Ada tasks when in fact the run-time
only required a single key.
Also added the CONFIGURE_MAXIMUM_FAKE_ADA_TASKS constant to account
for resources allocated for each non-Ada task/thread which invokes
the Ada run-time implicitly through an Ada call.
|
|
|
|
|
|
| |
it anyway. :)
Added hints about --prefix and --program-prefix options.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
1) In my haste to add C++ constructor/destructors to the 68360
linkcmds scripts I managed to break all existing 68360 programs.
Linker scripts which actually produce a working executable are
contained below. The problem was that the constructor/destructors
weren't included before the etext symbol.
On top of that Eric and I appear to have problems with attachments:
2) In deciphering the above problem I think I stumbled across the
reason you've had with patches mailed from me. I noticed that the
linkcmds (and linkcmds.bootp) scripts in the latest distribution have
a control-M (carriage return) at the end of each line. Could you
check the files below before installing them in the distribution and
see that there aren't returns in the files? Maybe if I send
everything as a tar attatchment things will work better.
|
|
|
|
| |
properly reflect the const on the buffer pointer being passed in.
|
|
|
|
| |
much target specific information in the script.
|
| |
|
|
|
|
|
| |
.align between i386-rtems (real number on .align) and i386-go32-rtems
(power of 2).
|