xonx-users Mailing List for XonX

SourceForge Headquarters 225 Broadway Suite 1600 San Diego, CA 92101 +1 (858) 422-6466

salutations xonx


http://break-ny.com/volume.php?break=r1y4f3dzpqz5bh3





David Mackler




Hello,
I represent <a title="Go to SoftFinder.com" href="http://softfinder.com/?utm_source=SF-developers&amp;utm_medium=mail&amp;utm_campaign=CertProgram" target="_blank">SoftFinder.com</a> and I am pleased to inform that your software has been certified by our team and included in our catalog. SoftFinder&rsquo;s directory is already hosting over one million of reliable applications and our website traffic increases by 100% each month.
At this stage we would like to invite you to join our Certified Partners Program, which is dedicated to chosen software authors, selected based on our internal criteria. By joining the program you are entitled to use services that will explicitly increase the number of your software downloads, enhance your product awareness and in consequence will add to your income. These would be as follows:
<ul>
<li>Promotion of your product on SoftFinder listing;</li>
<li>Editorial review of your software, additionally distributed through our Social Media channels;</li>
<li>Dedicated article on our blog;</li>
</ul>
As our Certified Partner you can benefit from all of the above options totally free of charge, provided that you insert the certified software label on your website in accordance with our guidelines. Please <a title="Certified Partners Budges" href="http://softfinder.com/images/certified-partner-2013.jpg?utm_source=SF-developers&amp;utm_medium=mail&amp;utm_campaign=CertProgram" target="_blank">see the available creatives</a> and contact us in order to obtain a selected label along with our instruction.
Please note, the above promotional conditions of the Certified Program will be applied only to developers, who join the program by the 30th of June, 2013.
If you are interested, please reply to this email at your earliest convenience and I will be happy to provide you with all materials and further information.
Kind regards,
Lukasz Kwiatkowski Product Manager



Dear Open Source developer,

I'm student of the Leuphana University in Lueneburg, Germany.

I'm writing my doctoral thesis about the innovativity of Project Communitie=
s.=20
I've picked your Project at random at sourceforge.net and would like to ask=
=20
you to take part of this pilot study.

To complete the questionair form will take you 10 to 15 minutes. You'll fin=
de=20
it under

http://dissertation.bjoern-benz.de/output/project_community/

Thank you for your participation,

Bj=C3=B6rn Benz

P.S. I will publish the results in approximately 6 months under =20
http://dissertation.bjoern-benz.de/results/project_community/

=2D-

Bj=C3=B6rn Benz
Leuphana Universit=C3=A4t L=C3=BCneburg
21335 L=C3=BCneburg

Mail: science at bjoern-benz.de



はじめまして美樹です。
掲示板で見て趣味合うかなって思ってメールしちゃいました。
 
イキナリでゴメンなさいm(__)m
こういう感じで知り合えるのに憧れてて初挑戦しちゃいました。
お返事もらえたら簡単な自己紹介しますネ(^_-)-☆
もしそんな気なかったらそう言ってもらえれば諦めますので。
もちろん仲良くなれた方が嬉しいけど。
お返事気長に待ってま〜す(^_^)/~
http://www.star-lightz.com/m-box





Super! Thanx a bunch! :-)

Any status on importing the patch into the tree? Its a pretty small 
change, so it won't really effect anything else. It can always be 
removed later, if need be.

:-)

JP


On 19 Apr 2005, at 15:28, Torrey Lyons wrote:

> At 1:33 AM -0700 4/19/05, John Davidorff Pell wrote:
>> I've posted a few bugs with the patch against 6.8.2 on the patch 
>> page. Here they are again:
>
> Yes, recall that this patch does not really properly work against 
> the 6.8 branch. (Despite its name. :-) ) It is intended for use 
> with the top of the tree, which does build and run properly now.
>
>> In .../apple/dri_glx.c, __driConfigOptions is declared as static, 
>> though in extras/Mesa/include/GL/internal/dri_interface.h it is 
>> not (its declared with extern, then used in .../glx/dri_glx.c). 
>> This causes the build on 6.8.2 to fail. :-!
>>
>> In .../darwin/quartz/applewm.c, appleWMProcs is declared as 
>> static, though in .../darwin/quartz/applewmExt.h it it not. This 
>> causes the build to fail. :-!
>>
>> I "fixed" both by commenting out static on that particular line. :-p
>
> Both of these issues were fixed in the top of the tree towards the 
> end of last week.
>
>> I have another problem that I'm not sure how to fix. In .../apple/ 
>> X11Application.m, `darwinSwapAltMeta' is used. This variable is 
>> defined in .../drwinKeyboard.c (note that's a .c file, not a .h 
>> file...?). I'm not sure what to include here to make this happy... 
>> Should I declare it again in X11Application.m? iDon't think so, b/ 
>> c darwinKeyboard.c uses it...
>>
>> in darwinKeyboard.c, darwinSwapAltMeta is declared `int 
>> darwinSwapAltMeta = 0;', and then checked at the end of the 
>> function `if (darwinSwapAltMeta)'. I'm guessing that this is 
>> supposed to pick up somewhere the setting! But, appearently it 
>> doesn't...? meThinks that X11Application.m is trying to set this 
>> very setting, but its not available. Did it used to be global? If 
>> I make it global, will Jesus hate me?
>
> This is declared in darwin.h in the top of tree:
>
> extern int darwinSwapAltMeta;
>
> --Torrey



--
Every time you share on a P2P network, God kills a kitten.
Please think of the kittens.



At 1:33 AM -0700 4/19/05, John Davidorff Pell wrote:
>I've posted a few bugs with the patch against 6.8.2 on the patch 
>page. Here they are again:

Yes, recall that this patch does not really properly work against the 
6.8 branch. (Despite its name. :-) ) It is intended for use with the 
top of the tree, which does build and run properly now.

>In .../apple/dri_glx.c, __driConfigOptions is declared as static, 
>though in extras/Mesa/include/GL/internal/dri_interface.h it is not 
>(its declared with extern, then used in .../glx/dri_glx.c). This 
>causes the build on 6.8.2 to fail. :-!
>
>In .../darwin/quartz/applewm.c, appleWMProcs is declared as static, 
>though in .../darwin/quartz/applewmExt.h it it not. This causes the 
>build to fail. :-!
>
>I "fixed" both by commenting out static on that particular line. :-p

Both of these issues were fixed in the top of the tree towards the 
end of last week.

>I have another problem that I'm not sure how to fix. In 
>.../apple/X11Application.m, `darwinSwapAltMeta' is used. This 
>variable is defined in .../drwinKeyboard.c (note that's a .c file, 
>not a .h file...?). I'm not sure what to include here to make this 
>happy... Should I declare it again in X11Application.m? iDon't think 
>so, b/c darwinKeyboard.c uses it...
>
>in darwinKeyboard.c, darwinSwapAltMeta is declared `int 
>darwinSwapAltMeta = 0;', and then checked at the end of the function 
>`if (darwinSwapAltMeta)'. I'm guessing that this is supposed to pick 
>up somewhere the setting! But, appearently it doesn't...? meThinks 
>that X11Application.m is trying to set this very setting, but its 
>not available. Did it used to be global? If I make it global, will 
>Jesus hate me?

This is declared in darwin.h in the top of tree:

extern int darwinSwapAltMeta;

--Torrey



I just posted the below, but I may have done it from the wrong e- 
mail, so if you didn't see it, read below! :-)

To add: darwinFakeMouse2Mask uses the function DarwinPArseModifierList 
(), which is defined in darwin.c... but not declared anywhere. I'm 
not sure where it went, I'm going to assume that it (like 
darwinSwapAltMeta) used to be global, but is no more.

Help?

JP




On 19 Apr 2005, at 01:33, John Davidorff Pell wrote:

> I've posted a few bugs with the patch against 6.8.2 on the patch 
> page. Here they are again:
>
> In .../apple/dri_glx.c, __driConfigOptions is declared as static, 
> though in extras/Mesa/include/GL/internal/dri_interface.h it is not 
> (its declared with extern, then used in .../glx/dri_glx.c). This 
> causes the build on 6.8.2 to fail. :-!
>
> In .../darwin/quartz/applewm.c, appleWMProcs is declared as static, 
> though in .../darwin/quartz/applewmExt.h it it not. This causes the 
> build to fail. :-!
>
> I "fixed" both by commenting out static on that particular line. :-p
>
> I have another problem that I'm not sure how to fix. In .../apple/ 
> X11Application.m, `darwinSwapAltMeta' is used. This variable is 
> defined in .../drwinKeyboard.c (note that's a .c file, not a .h 
> file...?). I'm not sure what to include here to make this happy... 
> Should I declare it again in X11Application.m? iDon't think so, b/c 
> darwinKeyboard.c uses it...
>
> in darwinKeyboard.c, darwinSwapAltMeta is declared `int 
> darwinSwapAltMeta = 0;', and then checked at the end of the 
> function `if (darwinSwapAltMeta)'. I'm guessing that this is 
> supposed to pick up somewhere the setting! But, appearently it 
> doesn't...? meThinks that X11Application.m is trying to set this 
> very setting, but its not available. Did it used to be global? If I 
> make it global, will Jesus hate me?
>
> JP
>
>
>
> --
> "They [our enemies] never stop thinking about new ways to harm our 
> country and our people, and neither do we. We must never stop 
> thinking about how best to offend our country." - George W. Bush 
> (August 5, 2004)
>
>




I've posted a few bugs with the patch against 6.8.2 on the patch 
page. Here they are again:

In .../apple/dri_glx.c, __driConfigOptions is declared as static, 
though in extras/Mesa/include/GL/internal/dri_interface.h it is not 
(its declared with extern, then used in .../glx/dri_glx.c). This 
causes the build on 6.8.2 to fail. :-!

In .../darwin/quartz/applewm.c, appleWMProcs is declared as static, 
though in .../darwin/quartz/applewmExt.h it it not. This causes the 
build to fail. :-!

I "fixed" both by commenting out static on that particular line. :-p

I have another problem that I'm not sure how to fix. In .../apple/ 
X11Application.m, `darwinSwapAltMeta' is used. This variable is 
defined in .../drwinKeyboard.c (note that's a .c file, not a .h 
file...?). I'm not sure what to include here to make this happy... 
Should I declare it again in X11Application.m? iDon't think so, b/c 
darwinKeyboard.c uses it...

in darwinKeyboard.c, darwinSwapAltMeta is declared `int 
darwinSwapAltMeta = 0;', and then checked at the end of the function 
`if (darwinSwapAltMeta)'. I'm guessing that this is supposed to pick 
up somewhere the setting! But, appearently it doesn't...? meThinks 
that X11Application.m is trying to set this very setting, but its not 
available. Did it used to be global? If I make it global, will Jesus 
hate me?

JP



--
"They [our enemies] never stop thinking about new ways to harm our 
country and our people, and neither do we. We must never stop 
thinking about how best to offend our country." - George W. Bush 
(August 5, 2004)



Hi

I run OpenDarwin 7.2.1 on a imac G4 800 - 17" flat panel and often run 
across a frozen screen if the screen goes black too long (through power 
management). If I have an already opened shell, I can still type 
killall X and restart Xdarwin but the output is completely frozen until 
then. I don't know if this is a frequent bug or not, but since I 
changed my enlightenment theme to "cronos" the problem is gone.

Thought it might be of some interrest to others.

yves




I have not been able to find a ~/.xinitrc. I've tried to search the whole
disk, but I've not found anything... Is there anything else that I could
do ?

tiennou ;-)




At 11:42 PM +0100 3/10/05, Etienne Samson wrote:
>I've just downloaded XFree 4.4.0 from Fink. I've successfully built it on
>MacOS 10.3.8/Darwin 7.8.0
>Now when I launch it (using Terminal.app), I'm getting this :
>
>2005-03-10 23:39:05.997 XDarwin[3928]
>XDarwin 1.3.0
>
>XFree86 Version 4.4.0 / X Window System
>(protocol Version 11, revision 0, vendor release 6600)
>Release Date: 29 February 2004
> If the server is older than 6-12 months, or if your hardware is
> newer than the above date, look for a newer version before
> reporting problems. (See http://www.XFree86.Org/FAQ)
>Operating System: Darwin Apple Computer, Inc.
>Could not find keymapping file Francais.keymapping.
>Reading keymap from the system.
>Loading GLX bundle glxCGL.bundle (using Apple's OpenGL)
>Display mode: Rootless Quartz -- Xplugin implementation
>PseudoramiX screen 0 added: 1024x747 @ (0,21).
>PseudoramiX screen 0 placed at X11 coordinate (0,0).
>[DRI] screen 0 installation complete
>Screen 0 added: 1024x747 @ (0,21)
>Screen 0 placed at X11 coordinate (0,0).
>Could not init font path element /usr/X11R6/lib/X11/fonts/CID/, removing
>from list!
>Quitting XDarwin...
>
>I don't really know what to do... I've checked permissions on the font
>path, they are all root:admin... Please help !

The font path error is harmless. It looks like your xinitrc file is 
broken. Have you provided a custom file in ~/.xinitrc? If so, try 
removing it. Your xinitrc file should be written to not complete. Ie. 
the last line should not have an & on the end of it. Once the xinitrc 
script completes, the X server quits normally as you see in the log.

--Torrey



Hi !

I've just downloaded XFree 4.4.0 from Fink. I've successfully built it on
MacOS 10.3.8/Darwin 7.8.0
Now when I launch it (using Terminal.app), I'm getting this :

2005-03-10 23:39:05.997 XDarwin[3928]
XDarwin 1.3.0

XFree86 Version 4.4.0 / X Window System
(protocol Version 11, revision 0, vendor release 6600)
Release Date: 29 February 2004
 If the server is older than 6-12 months, or if your hardware is
 newer than the above date, look for a newer version before
 reporting problems. (See http://www.XFree86.Org/FAQ)
Operating System: Darwin Apple Computer, Inc.
Could not find keymapping file Francais.keymapping.
Reading keymap from the system.
Loading GLX bundle glxCGL.bundle (using Apple's OpenGL)
Display mode: Rootless Quartz -- Xplugin implementation
PseudoramiX screen 0 added: 1024x747 @ (0,21).
PseudoramiX screen 0 placed at X11 coordinate (0,0).
[DRI] screen 0 installation complete
Screen 0 added: 1024x747 @ (0,21)
Screen 0 placed at X11 coordinate (0,0).
Could not init font path element /usr/X11R6/lib/X11/fonts/CID/, removing
from list!
Quitting XDarwin...

I don't really know what to do... I've checked permissions on the font
path, they are all root:admin... Please help !

tiennou ;-)




On 30 Dec 2004, at 13:27, Patrik Montgomery wrote:
>> Terminal.app launches /usr/bin/login, which is prolly the best thing 
>> to
>> do, as it is something that must be SUID anyway, and so should handle
>> all the things together that might require that. This has the
>> unfortunate side-effect of launching the default login shell... oh,
>> wait, that's what its supposed to do. ;-)
>>
> Are you sure that's what it does? I don't think Terminal.app does 
> anything
> that requires root access. I think it only launches the relevant shell 
> as a
> login shell - you don't get a login prompt when you open a Terminal 
> window,
> do you? If you check the archives for this list (should be at 
> sourceforge, right?),
> you will find an old discussion between Torrey, Greg Parker and yours 
> truly.
> The subject has been up before.
Yes, I'm sure that's what it does. I use pstree to show how its laid 
out. Attached is a pretty screen-shot from Activity Monitor. It does 
not, however, do this if in Preferences you have it launch a specific 
shell (even if that shell is your login shell). It does not just launch 
login, the command line used is "login -pf userName" -p makes it 
preserve the environment and -f makes it accept the user name, with no 
password, so long as it is being run by either root or that user. It 
does make your shell show up in who(1) or w(1). I'm not sure if those 
flags are portable, but if they are generally accepted or equivalents 
are available then that should be the norm, always, on every platform. 
This means that Xterm never has to query for the login shell, and it 
means that there are not ugly races in modifying utmp or whatever. It 
would even work on systems where that file does not exist and users are 
tracked by some other method.

JP



On 04-12-24 09.59, John Davidorff Pell (joh...@ma...) wrote:

> 
> On 23 Dec 2004, at 08:59, Torrey Lyons wrote:
> 
> 
>> At 7:08 PM -0800 12/22/04, John Davidorff Pell wrote:
>> 
>> 
>>> Hi!
>>> 
>>> I've got a few questions:
>>> 1) Why is Xterm SUID?
>> 
>> The short answer is so that it can chown the pseudo tty that it uses.
>> The long answer is that it does not absolutely need to do this and in
>> any case there are non-SUID ways to do this. Apple's X11 does not have
>> an SUID xterm and it just fails to chown the tty. The main symptom of
>> this is that if you use "who" you will not see your xterm sessions
>> listed. On the other hand if you open up a bunch of SUID xterm or
>> Terminal.app windows you will see them all listed in who. Terminal.app
>> is not SUID so there is clearly another way to do this. Most OS'es
>> have provided some non-SUID way to do this, but this is not standard.
>> If we knew how to do this on Mac OS X we could have xterm do this
>> instead.

Chowning the tty is not what makes terms show up to who. Who only reads out
the current users from /etc/utmp - which is 644 root, so xterm needs to be
root to write in it. Terminal doesn't write in utmp, so multiple Terminal
windows don't show up several times. Loginwindow (I think) writes in utmp
when you log in, so a graphical session shows up on who even if there are no
Terminal windows open. The same way sshd writes in utmp if you log in that
way. The logical thing would be to have XDM write in utmp - it's obviously
running as root anyway. Just launching X11 should not write in utmp - you're
not logging in again, you're just launching another process.

I don't know why xterm chowns the tty. There is probably a good historical
reason for it, but you can work without owning the tty today.

> Terminal.app launches /usr/bin/login, which is prolly the best thing to
> do, as it is something that must be SUID anyway, and so should handle
> all the things together that might require that. This has the
> unfortunate side-effect of launching the default login shell... oh,
> wait, that's what its supposed to do. ;-)

Are you sure that's what it does? I don't think Terminal.app does anything
that requires root access. I think it only launches the relevant shell as a
login shell - you don't get a login prompt when you open a Terminal window,
do you? 

If you check the archives for this list (should be at sourceforge, right?),
you will find an old discussion between Torrey, Greg Parker and yours truly.
The subject has been up before.
 
>>> 3) Shouldn't the default be not-SUID, and systems that require it
>>> explicitly set it to be SUID?
>> Perhaps, but since the Xserver is also SUID on many platforms it
>> sticks out less than as the only SUID X11 program on Mac OS X.
> SUID binaries are something that I have a pet-peeve about. I think that
> they should never be the default and, where required, are usually
> design-flaws.

What, you mean that xterm is not the perfect terminal? I'm shocked!

Really, xterm is very old. The source is hard to work with. Its one
redeeming feature is that it supports every terminal protocol since
cuniform, but that's a pretty big feature. Of course having a big userland
app like xterm suid is a big security risk, and I think everyone understands
that.

Note that rxvt is not suid root. If it were up to me, I'd make rxvt (or some
other modern terminal app) the new default xterm, modify XDM to write in the
user log (seems like the logical way to me - if you log in graphically to an
X11 terminal and use only shortcuts in the window manager to launch
programs, you don't write anything in utmp or even in wtmp, the user log)
and keep the old xterm as an optional install for those situations where you
need odd terminal protocols.

Alternatively, just determine the platforms where chowning the tty is
necessary and making it suid on those platforms only. Oh, and change the
default so it doesn't write into utmp - it can be done with a switch at
launch today.
-- 
Patrik Montgomery // pa...@ch...





On 23 Dec 2004, at 08:59, Torrey Lyons wrote:


> At 7:08 PM -0800 12/22/04, John Davidorff Pell wrote:
>
>
>> Hi!
>>
>> I've got a few questions:
>> 1) Why is Xterm SUID?
>>
>>
>
> The short answer is so that it can chown the pseudo tty that it uses. 
> The long answer is that it does not absolutely need to do this and in 
> any case there are non-SUID ways to do this. Apple's X11 does not have 
> an SUID xterm and it just fails to chown the tty. The main symptom of 
> this is that if you use "who" you will not see your xterm sessions 
> listed. On the other hand if you open up a bunch of SUID xterm or 
> Terminal.app windows you will see them all listed in who. Terminal.app 
> is not SUID so there is clearly another way to do this. Most OS'es 
> have provided some non-SUID way to do this, but this is not standard. 
> If we knew how to do this on Mac OS X we could have xterm do this 
> instead.

Terminal.app launches /usr/bin/login, which is prolly the best thing to 
do, as it is something that must be SUID anyway, and so should handle 
all the things together that might require that. This has the 
unfortunate side-effect of launching the default login shell... oh, 
wait, that's what its supposed to do. ;-)



>> 2) Shouldn't that be explicitly disabled on Darwin?
>>
>>
> Perhaps. We left it that way since it had always been that way and it 
> does modify behavior if you change it. You can change this yourself by 
> putting the following line in your xc/config/cf/host.def file before 
> you build:
>
> #define InstallXtermSetUID YES

Do you mean to set this to NO? Thanx, I wasn't sure how to turn that 
off. :-)




>> 3) Shouldn't the default be not-SUID, and systems that require it 
>> explicitly set it to be SUID?
>>
>>
>>
>
> Perhaps, but since the Xserver is also SUID on many platforms it 
> sticks out less than as the only SUID X11 program on Mac OS X.
>
>

SUID binaries are something that I have a pet-peeve about. I think that 
they should never be the default and, where required, are usually 
design-flaws.

Thanx,
JP








----
It's all fun and games 'til someone writes to a NULL pointer!






At 7:08 PM -0800 12/22/04, John Davidorff Pell wrote:
>Hi!
>
>I've got a few questions:
>1) Why is Xterm SUID?

The short answer is so that it can chown the pseudo tty that it uses. 
The long answer is that it does not absolutely need to do this and in 
any case there are non-SUID ways to do this. Apple's X11 does not 
have an SUID xterm and it just fails to chown the tty. The main 
symptom of this is that if you use "who" you will not see your xterm 
sessions listed. On the other hand if you open up a bunch of SUID 
xterm or Terminal.app windows you will see them all listed in who. 
Terminal.app is not SUID so there is clearly another way to do this. 
Most OS'es have provided some non-SUID way to do this, but this is 
not standard. If we knew how to do this on Mac OS X we could have 
xterm do this instead.

>2) Shouldn't that be explicitly disabled on Darwin?

Perhaps. We left it that way since it had always been that way and it 
does modify behavior if you change it. You can change this yourself 
by putting the following line in your xc/config/cf/host.def file 
before you build:

#define InstallXtermSetUID YES

>3) Shouldn't the default be not-SUID, and systems that require it 
>explicitly set it to be SUID?

Perhaps, but since the Xserver is also SUID on many platforms it 
sticks out less than as the only SUID X11 program on Mac OS X.

--Torrey



Hi!

I've got a few questions:
1) Why is Xterm SUID?
2) Shouldn't that be explicitly disabled on Darwin?
3) Shouldn't the default be not-SUID, and systems that require it 
explicitly set it to be SUID?


Thanx,
JP





--
When life hands you lemons, ask for a bottle of gin and tonic.




On Dec 22, 2004, at 11:49 AM, Torrey Lyons wrote:

> XonX: A good resource for more technical questions. The is really the 
> only place that purports to be a gathering place for developers of 
> Darwin/Mac OS X specific X11 technologies. As the lines blur between 
> what is Darwin specific, lots of discussion of interest happens on the 
> X.Org lists these days.
>
> Xorg: Where the current development effort is taking place. The top of 
> the Xorg tree is the "cutting edge".
>
> XFree86: The XDarwin DDX is synchronized with the Xorg tree at major 
> releases. Over the long term it is not clear if Xorg and XFree86 will 
> diverge or remain separate but parallel efforts.
>
> x11-users /at/ apple: A good and fairly active list, but mostly filled 
> with fairly simple questions.
>
> xdarwin.org: Not affiliated with the other efforts. This is more of a 
> third party providing a community resource.

Thanks, this is a very useful summary. Have you considered putting 
information like this on the XonX home page? It seems like XonX could 
potentially be a good clearinghouse for Mac X information. That's 
something that's sorely lacking at the moment. When I came to OS X 
from linux I was really disappointed at how little current, organized 
information there was about running X.

Cheers,
-n8

--
 >>>-- Nathaniel Gray -- Caltech Computer Science ------>
 >>>-- Mojave Project -- http://mojave.cs.caltech.edu -->




At 1:41 AM -0800 12/22/04, Nathaniel Gray wrote:
>In order to make progress on such a goal I'm trying to understand 
>the way X works, particularly on OS X but also in general. As part 
>of that I want to find out where I should ask questions, and where I 
>should look to find out where X on OS X development is heading. So 
>I'm trying to figure out where the center of the world is as far as 
>X on OS X is concerned. There seem to be tons of possibilities:
>	XonX
>	Xorg
>	XFree86
>	x11-users /at/ apple
>	xdarwin.org
>
>Can somebody advise me on where the action really is? ;^)

Unfortunately there is no one place anymore. I'd say it is like:

XonX: A good resource for more technical questions. The is really the 
only place that purports to be a gathering place for developers of 
Darwin/Mac OS X specific X11 technologies. As the lines blur between 
what is Darwin specific, lots of discussion of interest happens on 
the X.Org lists these days.

Xorg: Where the current development effort is taking place. The top 
of the Xorg tree is the "cutting edge".

XFree86: The XDarwin DDX is synchronized with the Xorg tree at major 
releases. Over the long term it is not clear if Xorg and XFree86 will 
diverge or remain separate but parallel efforts.

x11-users /at/ apple: A good and fairly active list, but mostly 
filled with fairly simple questions.

xdarwin.org: Not affiliated with the other efforts. This is more of a 
third party providing a community resource.

--Torrey



Hi,

I'm an OS X user who uses X every day and wants to see further advances 
in the way X apps can integrate with OS X. Most of the really powerful 
and useful open-source apps out there are X apps, and I really want to 
have them running on my desktop seamlessly. Of course, the integration 
will always be a bit awkward because of the different widget toolkits 
and such, but I would at least like to have the ability to provide each 
X app running on my system (or at least those that have been "ported" 
in some way) with an icon in the dock that focuses the topmost window 
of the app when I click on it, for example.

In order to make progress on such a goal I'm trying to understand the 
way X works, particularly on OS X but also in general. As part of that 
I want to find out where I should ask questions, and where I should 
look to find out where X on OS X development is heading. So I'm trying 
to figure out where the center of the world is as far as X on OS X is 
concerned. There seem to be tons of possibilities:
	XonX
	Xorg
	XFree86
	x11-users /at/ apple
	xdarwin.org

Can somebody advise me on where the action really is? ;^)

Thanks in advance,
-n8

--
 >>>-- Nathaniel Gray -- Caltech Computer Science ------>
 >>>-- Mojave Project -- http://mojave.cs.caltech.edu -->




At 11:15 AM -0800 12/2/04, John Davidorff Pell wrote:
>What does it break? I'm building Xorg right now and I'm wondering 
>what the "correct" fix is. Also, I'm not sure if "cpp3" exists if 
>one chooses not to install gcc 3.1 from the dev-tools even on 
>panther. the correct behaviour would be to use "cpp-3.1", if we must 
>use 3.1, no?

I'm considering the patch below. It works fine for me on Panther with 
gcc 3.3/3.1. I believe it should work correctly everywhere. Can 
anyone confirm on whether it works with gcc 3.5 and/or on Tiger? Any 
other suggestions?

Thanks,
Torrey

diff -u -d -b -w -r1.5 darwin.cf

--- darwin.cf   30 Oct 2004 01:41:46 -0000      1.5
+++ darwin.cf   3 Dec 2004 21:13:42 -0000
@@ -157,15 +157,17 @@

  /*
   * Our cpp isn't in /lib/cpp and early versions don't like -undef.
- * The default cpp-3.3 that ships with Panther inserts spurious #pragmas,
- * so we use the 3.1-based version.
+ * The gcc 3.3 cpp that Apple ships inserts spurious #pragmas,
+ * so we use the 3.1-based version in this case.
   */
-#if OSMajorVersion >= 7
+#if (GccMajorVersion == 3) && (GccMinorVersion == 3)
  # define CppCmd                 /usr/bin/cpp3
-# define StandardCppOptions     -traditional -D__GNUC__
  #else
  # define CppCmd                 /usr/bin/cpp
  #endif
+#if (GccMajorVersion == 3) && (GccMinorVersion == 3) || (GccMajorVersion > 3)
+# define StandardCppOptions     -traditional -D__GNUC__
+#endif
  #if HasGcc3
  # define RawCppCmd              CppCmd -undef
  #else



At 11:40 PM -0800 12/2/04, John Davidorff Pell wrote:
>I'm having trouble building CVS + X11.app patch. It builds 
>successfully, installs successfully, but does not work. As best as I 
>can tell, it doesn't try to build libXaw, and so fails (quietly) 
>building Xterm, and so xinitrc exits immediately, giving my a full 3 
>seconds of a working X server per double-click.

I can't reproduce your build failure. What OS version are you using? 
Its often hard to find the actual error message "make World" log as 
the build will continue past fatal errors and report success at the 
end anyway. I usually use:

grep -w Error world.log

Let me know (off list if you want) what errors this gives so we can 
diagnose the build problem. In any case, the patches you applied 
don't have anything to do with library builds, so there is likely 
some other issue with building libXaw.

--Torrey



At 11:40 PM -0800 12/2/04, John Davidorff Pell wrote:
>Howdy all,
>
>First, is this an acceptable list for asking questions that are more 
>general in nature?

Sure.

>I'm having trouble building CVS + X11.app patch. It builds 
>successfully, installs successfully, but does not work. As best as I 
>can tell, it doesn't try to build libXaw, and so fails (quietly) 
>building Xterm, and so xinitrc exits immediately, giving my a full 3 
>seconds of a working X server per double-click.

You can change your .xinitrc file to start something that actually 
runs as a quick workaround.

>Is this b/c of broken CVS or am I doing something wrong?

Sounds like broken CVS, I'll check. Freedesktop's CVS server was down 
after the system was broken into just before Thanksgiving. There 
might still be some residual issue.

--Torrey



Howdy all,

First, is this an acceptable list for asking questions that are more 
general in nature?

I'm having trouble building CVS + X11.app patch. It builds 
successfully, installs successfully, but does not work. As best as I 
can tell, it doesn't try to build libXaw, and so fails (quietly) 
building Xterm, and so xinitrc exits immediately, giving my a full 3 
seconds of a working X server per double-click.

Is this b/c of broken CVS or am I doing something wrong?

Thanx,
JP

P.S. CVS is as of 2 Dec 01:55. X11.app patch applied with no errors, 
but fuzz'd a little.




--
". . . Through the cold and darkness
we will look back on this day
and fall into oblivion.
Through a brilliance beyond twilight
we will rise again,
ready to face the dangers that befall on us . . ."




What does it break? I'm building Xorg right now and I'm wondering what 
the "correct" fix is. Also, I'm not sure if "cpp3" exists if one 
chooses not to install gcc 3.1 from the dev-tools even on panther. the 
correct behaviour would be to use "cpp-3.1", if we must use 3.1, no?

Thanx,
JP

On 2 Dec 2004, at 08:53, Benjamin Reed wrote:



> John Davidorff Pell wrote:
>
>> xc/config/cf/darwin.cf has a slight bug. It uses "cpp3" for its C 
>> preprocessor, which unfortunately does not exist on my system. It 
>> should be using cpp-3.3. If somebody with commit could change it that 
>> would be great.
>> It says that it does not like cpp from 3.3, but that doesn't help. 
>> Either X11 should get used to gcc 3.3, as its a more recent compiler, 
>> or it should use gcc 4.0. Tiger dev-tools will not ship with gcc 3.1, 
>> so it needs to get fixed eventually. Actually, I'm not entirely sure 
>> that Panther dev-tools include cpp3, because the binary is named 
>> cpp-3.1 and cpp-3.3 (I can't check at the moment if there is a 
>> symlink).
>>
>
> It should use cpp4 on tiger, yes.
>
> cpp3 is broken, it adds some pragma stuff that breaks generating 
> anything other than code with it (X uses cpp to create shell scripts 
> and other things...)
>
> The problem is not that cpp3 is inherently bad, it's that apple's cpp3 
> has a bug.
>
> -- 
> Benjamin Reed, a.k.a. Ranger Rick
> ra...@be... / http://ranger.befunk.com/
> "You can scoff, Lister, that's nothing new.  They laughed at
> Galileo.  They laughed at Edison.  They laughed at Columbo."
> "Who's Columbo?" "The man with the dirty mac who discovered
> America."   -- Rimmer, on _Red Dwarf_
>
>
> -------------------------------------------------------
> SF email is sponsored by - The IT Product Guide
> Read honest & candid reviews on hundreds of IT Products from real 
> users.
> Discover which products truly live up to the hype. Start reading now. 
> http://productguide.itmanagersjournal.com/
> _______________________________________________
> XonX-Users mailing list
> Xon...@li...
> https://lists.sourceforge.net/lists/listinfo/xonx-users
>





--
God is dead, now the war shall never end.





2001	Jan	Feb	Mar	Apr	May	Jun	Jul	Aug	Sep	Oct (30)	Nov (48)	Dec (28)
2002	Jan (8)	Feb (29)	Mar (13)	Apr (6)	May (19)	Jun (3)	Jul (27)	Aug (10)	Sep (48)	Oct (14)	Nov (22)	Dec (7)
2003	Jan (4)	Feb (7)	Mar	Apr (4)	May (7)	Jun (2)	Jul (4)	Aug (3)	Sep	Oct (1)	Nov	Dec (25)
2004	Jan (19)	Feb (2)	Mar (4)	Apr	May (3)	Jun	Jul	Aug	Sep (20)	Oct	Nov	Dec (18)
2005	Jan	Feb	Mar (4)	Apr (4)	May	Jun	Jul	Aug	Sep	Oct	Nov	Dec
2007	Jan	Feb	Mar	Apr (1)	May	Jun	Jul	Aug	Sep	Oct	Nov	Dec (1)
2012	Jan	Feb	Mar	Apr	May	Jun	Jul	Aug	Sep	Oct	Nov (1)	Dec
2013	Jan (1)	Feb	Mar	Apr	May (1)	Jun	Jul	Aug	Sep	Oct	Nov	Dec
2014	Jan	Feb	Mar	Apr (1)	May	Jun	Jul	Aug	Sep	Oct	Nov	Dec
2015	Jan	Feb	Mar	Apr	May	Jun	Jul	Aug	Sep	Oct (1)	Nov	Dec
2016	Jan	Feb	Mar	Apr	May (1)	Jun	Jul	Aug	Sep	Oct	Nov	Dec

xonx-users Mailing List for XonX

xonx-users — XonX user questions and general discussion