public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
* i586-(pc-)cygwin
@ 1999-06-15 20:50 Samy Alex ZAIMI
  1999-06-15 21:03 ` i586-(pc-)cygwin Mikey
  1999-06-30 22:10 ` i586-(pc-)cygwin Samy Alex ZAIMI
  0 siblings, 2 replies; 6+ messages in thread
From: Samy Alex ZAIMI @ 1999-06-15 20:50 UTC (permalink / raw)
  To: cygwin

Hello,
I have installed a recent
cygwin-inst-YYYYMMDD.tar.gz.
After unpacking it, it creates a folder
"i586-pc-cygwin", which contains a "lib" subfolder
and an "include" subfolder.
My first cygwin-20.1 installation created a folder
"i586-cygwin", which contains similar folders
(actually, the old versions of the files contained
in the more recent "i586-pc-cygwin").
I am really sorry if my question looks too silly,
but what could be the consequences of replacing
"i586-cygwin" by "i586-pc-cygwin" ?
The things I found so far that needs some update
are :
1. C_INCLUDE_PATH in my .bashrc
2. my cygwin*.cf files under
/usr/X11R6.4/lib/X11/config
What else could need some updating ?
Do I have for instance to change
"/usr/lib/gcc-lib/i586-cygwin32" into
"/usr/lib/gcc-lib/i586-pc-cygwin32" ?
Note that this folder contains egcs binaries, and
usually these binaries point directly to
../../../../i586-cygwin32 for libraries, include
files, and "ld.exe" among other things.
Any comment ?
(Again, sorry if these questions seem too naive).
--
Dr.-Ing. Sami Alex ZAIMI
IAMP - Tohoku University - Sendai (Japan)



--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com

^ permalink raw reply	[flat|nested] 6+ messages in thread

* Re: i586-(pc-)cygwin
  1999-06-15 20:50 i586-(pc-)cygwin Samy Alex ZAIMI
@ 1999-06-15 21:03 ` Mikey
  1999-06-15 22:10   ` i586-(pc-)cygwin Glenn Spell
  1999-06-30 22:10   ` i586-(pc-)cygwin Mikey
  1999-06-30 22:10 ` i586-(pc-)cygwin Samy Alex ZAIMI
  1 sibling, 2 replies; 6+ messages in thread
From: Mikey @ 1999-06-15 21:03 UTC (permalink / raw)
  To: zaimi; +Cc: cygwin

What needs updating is the switches
to configure in DJ's autobuild script
just rename the dir  i586-pc-cygwin32
to i586-cygwin32 overwriting the old
files of the same name.

On Wed, 16 Jun 1999 05:49:45 +0000, you wrote:

>Hello,
>I have installed a recent
>cygwin-inst-YYYYMMDD.tar.gz.
>After unpacking it, it creates a folder
>"i586-pc-cygwin", which contains a "lib" subfolder
>and an "include" subfolder.
>My first cygwin-20.1 installation created a folder
>"i586-cygwin", which contains similar folders
>(actually, the old versions of the files contained
>in the more recent "i586-pc-cygwin").
>I am really sorry if my question looks too silly,
>but what could be the consequences of replacing
>"i586-cygwin" by "i586-pc-cygwin" ?
>The things I found so far that needs some update
>are :
>1. C_INCLUDE_PATH in my .bashrc
>2. my cygwin*.cf files under
>/usr/X11R6.4/lib/X11/config
>What else could need some updating ?
>Do I have for instance to change
>"/usr/lib/gcc-lib/i586-cygwin32" into
>"/usr/lib/gcc-lib/i586-pc-cygwin32" ?
>Note that this folder contains egcs binaries, and
>usually these binaries point directly to
>../../../../i586-cygwin32 for libraries, include
>files, and "ld.exe" among other things.
>Any comment ?
>(Again, sorry if these questions seem too naive).
>--
>Dr.-Ing. Sami Alex ZAIMI
>IAMP - Tohoku University - Sendai (Japan)


--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com

^ permalink raw reply	[flat|nested] 6+ messages in thread

* Re: i586-(pc-)cygwin
  1999-06-15 21:03 ` i586-(pc-)cygwin Mikey
@ 1999-06-15 22:10   ` Glenn Spell
  1999-06-30 22:10     ` i586-(pc-)cygwin Glenn Spell
  1999-06-30 22:10   ` i586-(pc-)cygwin Mikey
  1 sibling, 1 reply; 6+ messages in thread
From: Glenn Spell @ 1999-06-15 22:10 UTC (permalink / raw)
  To: cygwin

On Jun 16 1999 at 03:34AM +0000, Mikey wrote:
> 
> What needs updating is the switches to configure in DJ's autobuild
> script

Not necessarily.

I believe config.guess/config.sub will render the canonical form of
"i586-pc-cygwin32". (Newer versions probably drop the "32".)

I prefer to supply a host_alias of "i586-cygwin32", but I'm sure
there's nothing wrong with DJ's scripts.

Actually, the target subdirectory is not even needed in some cases.
I ran B19 for months without it. (I forced a target subdir of ".".
I believe that's why I was never able to build the winsup sources
with B19.  :-)

    "The GNU configure and build system" by Ian Lance Taylor
              < http://www.airs.com/ian/configure/ >

-glenn

-- 
 )      Glenn Spell <glenn@gs.fay.nc.us>      )   _       _____
 )   Fayetteville, North Carolina, U. S. A.   )_ (__\____o /_/_ |
 )  _  _  _  _  _  _  _  _  _  _  _  _  _  _  )   >-----._/_/__]>
 )- blue skies - happy trails - sweet dreams -)             `0  |

--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com

^ permalink raw reply	[flat|nested] 6+ messages in thread

* Re: i586-(pc-)cygwin
  1999-06-15 21:03 ` i586-(pc-)cygwin Mikey
  1999-06-15 22:10   ` i586-(pc-)cygwin Glenn Spell
@ 1999-06-30 22:10   ` Mikey
  1 sibling, 0 replies; 6+ messages in thread
From: Mikey @ 1999-06-30 22:10 UTC (permalink / raw)
  To: zaimi; +Cc: cygwin

What needs updating is the switches
to configure in DJ's autobuild script
just rename the dir  i586-pc-cygwin32
to i586-cygwin32 overwriting the old
files of the same name.

On Wed, 16 Jun 1999 05:49:45 +0000, you wrote:

>Hello,
>I have installed a recent
>cygwin-inst-YYYYMMDD.tar.gz.
>After unpacking it, it creates a folder
>"i586-pc-cygwin", which contains a "lib" subfolder
>and an "include" subfolder.
>My first cygwin-20.1 installation created a folder
>"i586-cygwin", which contains similar folders
>(actually, the old versions of the files contained
>in the more recent "i586-pc-cygwin").
>I am really sorry if my question looks too silly,
>but what could be the consequences of replacing
>"i586-cygwin" by "i586-pc-cygwin" ?
>The things I found so far that needs some update
>are :
>1. C_INCLUDE_PATH in my .bashrc
>2. my cygwin*.cf files under
>/usr/X11R6.4/lib/X11/config
>What else could need some updating ?
>Do I have for instance to change
>"/usr/lib/gcc-lib/i586-cygwin32" into
>"/usr/lib/gcc-lib/i586-pc-cygwin32" ?
>Note that this folder contains egcs binaries, and
>usually these binaries point directly to
>../../../../i586-cygwin32 for libraries, include
>files, and "ld.exe" among other things.
>Any comment ?
>(Again, sorry if these questions seem too naive).
>--
>Dr.-Ing. Sami Alex ZAIMI
>IAMP - Tohoku University - Sendai (Japan)


--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com

^ permalink raw reply	[flat|nested] 6+ messages in thread

* i586-(pc-)cygwin
  1999-06-15 20:50 i586-(pc-)cygwin Samy Alex ZAIMI
  1999-06-15 21:03 ` i586-(pc-)cygwin Mikey
@ 1999-06-30 22:10 ` Samy Alex ZAIMI
  1 sibling, 0 replies; 6+ messages in thread
From: Samy Alex ZAIMI @ 1999-06-30 22:10 UTC (permalink / raw)
  To: cygwin

Hello,
I have installed a recent
cygwin-inst-YYYYMMDD.tar.gz.
After unpacking it, it creates a folder
"i586-pc-cygwin", which contains a "lib" subfolder
and an "include" subfolder.
My first cygwin-20.1 installation created a folder
"i586-cygwin", which contains similar folders
(actually, the old versions of the files contained
in the more recent "i586-pc-cygwin").
I am really sorry if my question looks too silly,
but what could be the consequences of replacing
"i586-cygwin" by "i586-pc-cygwin" ?
The things I found so far that needs some update
are :
1. C_INCLUDE_PATH in my .bashrc
2. my cygwin*.cf files under
/usr/X11R6.4/lib/X11/config
What else could need some updating ?
Do I have for instance to change
"/usr/lib/gcc-lib/i586-cygwin32" into
"/usr/lib/gcc-lib/i586-pc-cygwin32" ?
Note that this folder contains egcs binaries, and
usually these binaries point directly to
../../../../i586-cygwin32 for libraries, include
files, and "ld.exe" among other things.
Any comment ?
(Again, sorry if these questions seem too naive).
--
Dr.-Ing. Sami Alex ZAIMI
IAMP - Tohoku University - Sendai (Japan)



--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com

^ permalink raw reply	[flat|nested] 6+ messages in thread

* Re: i586-(pc-)cygwin
  1999-06-15 22:10   ` i586-(pc-)cygwin Glenn Spell
@ 1999-06-30 22:10     ` Glenn Spell
  0 siblings, 0 replies; 6+ messages in thread
From: Glenn Spell @ 1999-06-30 22:10 UTC (permalink / raw)
  To: cygwin

On Jun 16 1999 at 03:34AM +0000, Mikey wrote:
> 
> What needs updating is the switches to configure in DJ's autobuild
> script

Not necessarily.

I believe config.guess/config.sub will render the canonical form of
"i586-pc-cygwin32". (Newer versions probably drop the "32".)

I prefer to supply a host_alias of "i586-cygwin32", but I'm sure
there's nothing wrong with DJ's scripts.

Actually, the target subdirectory is not even needed in some cases.
I ran B19 for months without it. (I forced a target subdir of ".".
I believe that's why I was never able to build the winsup sources
with B19.  :-)

    "The GNU configure and build system" by Ian Lance Taylor
              < http://www.airs.com/ian/configure/ >

-glenn

-- 
 )      Glenn Spell <glenn@gs.fay.nc.us>      )   _       _____
 )   Fayetteville, North Carolina, U. S. A.   )_ (__\____o /_/_ |
 )  _  _  _  _  _  _  _  _  _  _  _  _  _  _  )   >-----._/_/__]>
 )- blue skies - happy trails - sweet dreams -)             `0  |

--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com

^ permalink raw reply	[flat|nested] 6+ messages in thread

end of thread, other threads:[~1999-06-30 22:10 UTC | newest]

Thread overview: 6+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
1999-06-15 20:50 i586-(pc-)cygwin Samy Alex ZAIMI
1999-06-15 21:03 ` i586-(pc-)cygwin Mikey
1999-06-15 22:10   ` i586-(pc-)cygwin Glenn Spell
1999-06-30 22:10     ` i586-(pc-)cygwin Glenn Spell
1999-06-30 22:10   ` i586-(pc-)cygwin Mikey
1999-06-30 22:10 ` i586-(pc-)cygwin Samy Alex ZAIMI

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).