* repository copy of FreeBSD i386 config file.
@ 2000-09-04 13:52 David O'Brien
2000-09-12 5:02 ` Gerald Pfeifer
` (2 more replies)
0 siblings, 3 replies; 8+ messages in thread
From: David O'Brien @ 2000-09-04 13:52 UTC (permalink / raw)
To: gcc
I would like to see gcc/config/i386/freebsd.h,v repository copied to
gcc/config/i386/freebsd-aout.h,v (I have a script to fixup the tags).
I then would like to see gcc/config/i386/freebsd-elf.h [checked out]
copied on top of gcc/config/i386/freebsd.h and committed. Then
gcc/config/i386/freebsd-elf.h put in the Attic by
``cvs rm -f freebsd-elf.h ; cvs ci freebsd-elf.h''.
Doing such repository copies (ie, moving and coping files around w/in the
repository) is documented in the CVS docs.
The purpose is to create a standard naming for FreeBSD configuration
files. FreeBSD's a.out support is now ancient history and we will never
return to it. I will donate configuration bits for FreeBSD/Alpha and
FreeBSD/IA-64 later. There are two other FreeBSD ports in the works. So
a standard setup would really be nice and clean.
Is this acceptable? If not, could I get permission to do it this way:
cvs co gcc/config/i386/freebsd.h
mv gcc/config/i386/freebsd.h gcc/config/i386/freebsd-aout.h
cvs add gcc/config/i386/freebsd-aout.h
cvs ci gcc/config/i386/freebsd-aout.h
cvs co gcc/config/i386/freebsd-elf.h
mv gcc/config/i386/freebsd-elf.h gcc/config/i386/freebsd.h
cvs ci gcc/config/i386/freebsd.h
cvs rm gcc/config/i386/freebsd-elf.h
cvs ci gcc/config/i386/freebsd-elf.h
# add freebsd-aout.h and remove freebsd-elf.h from gcc/po/*
--
-- David (obrien@FreeBSD.org)
^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: repository copy of FreeBSD i386 config file.
2000-09-04 13:52 repository copy of FreeBSD i386 config file David O'Brien
@ 2000-09-12 5:02 ` Gerald Pfeifer
2000-09-12 7:06 ` Geoff Keating
2000-09-17 22:48 ` H . J . Lu
2000-09-12 11:53 ` Richard Henderson
2000-09-12 14:03 ` Marc Espie
2 siblings, 2 replies; 8+ messages in thread
From: Gerald Pfeifer @ 2000-09-12 5:02 UTC (permalink / raw)
To: David O'Brien; +Cc: gcc
On Mon, 4 Sep 2000, David O'Brien wrote:
> I would like to see gcc/config/i386/freebsd.h,v repository copied to
> gcc/config/i386/freebsd-aout.h,v (I have a script to fixup the tags).
> [...]
> Doing such repository copies (ie, moving and coping files around w/in
> the repository) is documented in the CVS docs.
I'm not sure whether we really want to do that (Basically, this is a
shortcoming of CVS that cannot be solved completely satisfactory)
or the following...
> Is this acceptable? If not, could I get permission to do it this way:
>
> cvs co gcc/config/i386/freebsd.h
> mv gcc/config/i386/freebsd.h gcc/config/i386/freebsd-aout.h
> [...]
...but in principle it makes sense to clean this up now, though you'll
also have to update the configure stuff, right?
Can someone with global write priviledge please have a look?
Gerald
PS: Though GCC became rather useless on FreeBSD these days, but that's a
different story: http://www.FreeBSD.org/cgi/query-pr.cgi?pr=20966 :-(
--
Gerald "Jerry" pfeifer@dbai.tuwien.ac.at http://www.dbai.tuwien.ac.at/~pfeifer/
^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: repository copy of FreeBSD i386 config file.
2000-09-12 5:02 ` Gerald Pfeifer
@ 2000-09-12 7:06 ` Geoff Keating
2000-09-13 20:13 ` David O'Brien
2000-09-17 22:48 ` H . J . Lu
1 sibling, 1 reply; 8+ messages in thread
From: Geoff Keating @ 2000-09-12 7:06 UTC (permalink / raw)
To: Gerald Pfeifer; +Cc: gcc, David O'Brien
Gerald Pfeifer <pfeifer@dbai.tuwien.ac.at> writes:
> On Mon, 4 Sep 2000, David O'Brien wrote:
> > I would like to see gcc/config/i386/freebsd.h,v repository copied to
> > gcc/config/i386/freebsd-aout.h,v (I have a script to fixup the tags).
> > [...]
> > Doing such repository copies (ie, moving and coping files around w/in
> > the repository) is documented in the CVS docs.
>
> I'm not sure whether we really want to do that (Basically, this is a
> shortcoming of CVS that cannot be solved completely satisfactory)
> or the following...
I think we really _don't_ want to do that. It means that anyone who
checks out the release branch would find it doesn't work on freebsd.
(I assume you're not proposing this change for the release branch
too).
> > Is this acceptable? If not, could I get permission to do it this way:
> >
> > cvs co gcc/config/i386/freebsd.h
> > mv gcc/config/i386/freebsd.h gcc/config/i386/freebsd-aout.h
> > [...]
Probably. Submit a patch.
--
- Geoffrey Keating <geoffk@cygnus.com>
^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: repository copy of FreeBSD i386 config file.
2000-09-04 13:52 repository copy of FreeBSD i386 config file David O'Brien
2000-09-12 5:02 ` Gerald Pfeifer
@ 2000-09-12 11:53 ` Richard Henderson
2000-09-12 14:03 ` Marc Espie
2 siblings, 0 replies; 8+ messages in thread
From: Richard Henderson @ 2000-09-12 11:53 UTC (permalink / raw)
To: David O'Brien; +Cc: gcc
On Mon, Sep 04, 2000 at 01:52:48PM -0700, David O'Brien wrote:
> I would like to see gcc/config/i386/freebsd.h,v repository copied to
> gcc/config/i386/freebsd-aout.h,v (I have a script to fixup the tags).
I think I'd rather we not play with the ,v files, but instead
just do the "userland" move.
r~
^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: repository copy of FreeBSD i386 config file.
2000-09-04 13:52 repository copy of FreeBSD i386 config file David O'Brien
2000-09-12 5:02 ` Gerald Pfeifer
2000-09-12 11:53 ` Richard Henderson
@ 2000-09-12 14:03 ` Marc Espie
2000-09-13 20:23 ` David O'Brien
2 siblings, 1 reply; 8+ messages in thread
From: Marc Espie @ 2000-09-12 14:03 UTC (permalink / raw)
To: obrien; +Cc: gcc
You definitely don't want to move ,v files around on any project
where you wish to keep history and be able to check out old versions
and have them work.
The only leeway that cvs leaves you, in my experience, is that you
can duplicate a ,v file, to keep a better sense of history of a file
(this makes it appear as if the file was always there in the old
checkouts).
You still have to make sure a new version of the new file is checked in,
possibly forcibly if you just want to move stuff around.
You'd better have very good reasons for such a hack (such as a 300
revisions long history), otherwise, the classical
cp old new
cvs rm -f old
cvs add new
cvs commit old new
works just fine.
^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: repository copy of FreeBSD i386 config file.
2000-09-12 7:06 ` Geoff Keating
@ 2000-09-13 20:13 ` David O'Brien
0 siblings, 0 replies; 8+ messages in thread
From: David O'Brien @ 2000-09-13 20:13 UTC (permalink / raw)
To: Geoff Keating; +Cc: Gerald Pfeifer, gcc
On Tue, Sep 12, 2000 at 07:05:29AM -0700, Geoff Keating wrote:
> > > I would like to see gcc/config/i386/freebsd.h,v repository copied to
> > > gcc/config/i386/freebsd-aout.h,v (I have a script to fixup the tags).
> > > [...]
> > > Doing such repository copies (ie, moving and coping files around w/in
> > > the repository) is documented in the CVS docs.
> >
> > I'm not sure whether we really want to do that (Basically, this is a
> > shortcoming of CVS that cannot be solved completely satisfactory)
> > or the following...
>
> I think we really _don't_ want to do that. It means that anyone who
> checks out the release branch would find it doesn't work on freebsd.
Why do you think that? I assure you, this is not the case. We do repo
copies on a regular basis in the FreeBSD CVS repository. And that is
even mirrored by many, many thousands of people.
--
-- David (obrien@FreeBSD.org)
^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: repository copy of FreeBSD i386 config file.
2000-09-12 14:03 ` Marc Espie
@ 2000-09-13 20:23 ` David O'Brien
0 siblings, 0 replies; 8+ messages in thread
From: David O'Brien @ 2000-09-13 20:23 UTC (permalink / raw)
To: Marc Espie; +Cc: gcc
On Tue, Sep 12, 2000 at 11:02:42PM +0200, Marc Espie wrote:
> You definitely don't want to move ,v files around on any project
> where you wish to keep history and be able to check out old versions
> and have them work.
True. This is why I was requesting a repository _COPY_.
> The only leeway that cvs leaves you, in my experience, is that you
> can duplicate a ,v file, to keep a better sense of history of a file
Yes.
> (this makes it appear as if the file was always there in the old
> checkouts).
Not quite. It appears on the HEAD only, as the tags (branch point too)
are changed. In FreeBSD we prepend "old_" to them.
> You still have to make sure a new version of the new file is checked in,
> possibly forcibly if you just want to move stuff around.
I don't follow this. ``cp old.h,v new.h,v'' will do it.
> You'd better have very good reasons for such a hack (such as a 300
> revisions long history),
I think you're streaching the amount of history that is important.
In what I'm asking, it will be a total pain in the ass to see the changes
to freebsd-aout.h after a few changes to it. This because one will have
to:
cvs up -r<REVISION_YOU_WANT_TO_COMPARE_WITH> freebsd.h
cvs up -r<REVISION_YOU_WANT_TO_COMPARE_WITH> freebsd-aout.h
diff freebsd.h freebsd-aout.h
This is not how CVS was envisioned to be used.
> otherwise, the classical
> cp old new
> cvs rm -f old
> cvs add new
> cvs commit old new
> works just fine.
We have found that it doesn't in FreeBSD.
--
-- David (obrien@FreeBSD.org)
^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: repository copy of FreeBSD i386 config file.
2000-09-12 5:02 ` Gerald Pfeifer
2000-09-12 7:06 ` Geoff Keating
@ 2000-09-17 22:48 ` H . J . Lu
1 sibling, 0 replies; 8+ messages in thread
From: H . J . Lu @ 2000-09-17 22:48 UTC (permalink / raw)
To: Gerald Pfeifer; +Cc: David O'Brien, gcc
On Tue, Sep 12, 2000 at 02:02:21PM +0200, Gerald Pfeifer wrote:
>
> PS: Though GCC became rather useless on FreeBSD these days, but that's a
> different story: http://www.FreeBSD.org/cgi/query-pr.cgi?pr=20966 :-(
That is the typical FreeBSD problem with gcc/binutils. Why not FreeBSD
just uses the straight ELF support in binutils like Linux and Solaris?
Don't tell me you need the Linux emulation :-).
H.J.
^ permalink raw reply [flat|nested] 8+ messages in thread
end of thread, other threads:[~2000-09-17 22:48 UTC | newest]
Thread overview: 8+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2000-09-04 13:52 repository copy of FreeBSD i386 config file David O'Brien
2000-09-12 5:02 ` Gerald Pfeifer
2000-09-12 7:06 ` Geoff Keating
2000-09-13 20:13 ` David O'Brien
2000-09-17 22:48 ` H . J . Lu
2000-09-12 11:53 ` Richard Henderson
2000-09-12 14:03 ` Marc Espie
2000-09-13 20:23 ` David O'Brien
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).