Jarkko Hietaniemi wrote:
The attached script, suitable for Porting/, suitable for both blead
and maint, helps in the battle of keeping the non-UNIX platforms up
And in time I will learn to double check the address suggestions
the autocompletion feature gives me.
And indeed it detects quite a few missing symbols, for epoc,
Netware, symbian (!), plan9 and windows CE.
The (!) was why I wrote this :-)
Also, uconfig.sh probably needs to be updated, although I'm not
100% sure how to do this properly.
The attached script, suitable for Porting/, suitable for both blead
and maint, helps in the battle of keeping the non-UNIX platforms up
to date in their knowledge of Configure variables. Run it at the
top level directory and it will tell its best guess as to which of
those variables are missing
Which is not really portable with command line options, due to how
env(1) works on OS X:
$ test
#!/usr/bin/env perl -wl
print hello world
$ ./test
env: perl -wl: No such file or directory
That is both against the documentation (env(1)) and the UNIX spec,
so I think a bug report to
Joseph Alotta wrote:
On May 13, 2004, at 11:12 PM, Matt Doughty wrote:
here is my little bit for making a really short solution.
--Matt
#!perl
my $dir = shift() || .;
opendir(DIR, $dir);
print for(map { $_ . \n } sort { (stat($b))[9] = (stat($a))[9] }
grep { !/^.{1,2}$/ } readdir DIR );
*** malloc: vm_allocate(size=8421376) failed (error
code=3)
*** malloc[5576]: error: Can't allocate region
Out of memory!
The strange thing is that I'm not slurping up the
whole file,
Oh but you are...
I'm reading it line by line. But Perl
seems to be slurping the whole thing into
David Wheeler wrote:
On Apr 17, 2004, at 4:39 PM, Jarkko Hietaniemi wrote:
Wrong. Ponie is off the chart, or maybe more like 5.11,
That's one louda, innit?
I just wonder who's the drummer.
--
Jarkko Hietaniemi [EMAIL PROTECTED] http://www.iki.fi/jhi/ There is this special
biologist
Andrew M. Langmead wrote:
On Apr 17, 2004, at 8:57 AM, Chris Devers wrote:
I thought even numbered point releases were unstable, test releases.
The other way around. The odd numbered releases are the development
track. (When you try to run some script against them, something goes
This is great news, Edward, thank you! I just hope that 5.8.1 is
finalized and makes it in before 10.3 is finalized. I'd rather see an
You think I don't? :-)
official stable Perl release than a pre-release included with Panther.
--
Jarkko Hietaniemi [EMAIL PROTECTED] http://www.iki.fi/jhi
On Tue, Jul 01, 2003 at 03:24:34PM -0700, David Wheeler wrote:
On Tuesday, July 1, 2003, at 03:19 PM, Jarkko Hietaniemi wrote:
This is great news, Edward, thank you! I just hope that 5.8.1 is
finalized and makes it in before 10.3 is finalized. I'd rather see an
You think I don't
, too?
--
Jarkko Hietaniemi [EMAIL PROTECTED] http://www.iki.fi/jhi/ There is this special
biologist word we use for 'stable'. It is 'dead'. -- Jack Cohen
. I killed the testing and ran it again, and
this time it worked fine.
Jarkko, have you noticed this?
Nope. It would be nice to get a system call trace on such a hangup.
I.e. what is it doing?
--
Jarkko Hietaniemi [EMAIL PROTECTED] http://www.iki.fi/jhi/ There is this special
biologist word
On Sun, Dec 16, 2001 at 02:11:04AM -0600, Ken Williams wrote:
Hey Jarkko,
I recall a previous message[1] from Wilfredo Sanchez in which he said
that using the -flat-namespaces linker flag was the easy way to get
perl working on OS X, but that leaving it out was the right way. I
see
Anyone reading this list and running Rhapsody/Mac OS X Server?
(not Mac OS X 10.1, because I can test Perl on that myself)
If so, I would be grateful if you downloaded and tried the
below developer snapshot of Perl.
http:[EMAIL PROTECTED]
http:[EMAIL PROTECTED]
On Wed, Jun 13, 2001 at 08:26:12AM +, Nick Ing-Simmons wrote:
Edward Moy [EMAIL PROTECTED] writes:
Thread 0:
#0 0x4be055dc in _Perl_get_av ()
#1 0x4be055c4 in _Perl_get_av ()
#2 0x4bf51778 in _PerlIO_default_layers ()
#3 0x4bf5254c in _PerlIO_resolve_layers ()
#4
passed the current roadblock, not as a permanent solution. But I did
recompile with -2147483647-1 and it also finishes building. 3 test
scripts still fail:
Those failures are 'known ones'. Not that it makes it any better or
that they shouldn't be fixed, but now we are back at the point
Please let me know if I should send reports to a different address. I'm
sending to P5P ([EMAIL PROTECTED]) and CC-ing Jarkko and the
OSX-perl list.
Sounds okay.
`sh cflags libperl.dylib perly.o` perly.c
CCCMD = cc -DPERL_CORE -c -pipe -fno-common -DHAS_TELLDIR_PROTOTYPE -Wall
(gdb) run
Oops, I meant to say
run configpm configpm.tmp
to get the same segfault, and after that 'where'.
Starting program: /Users/lshatzer/perl/bleadperl/./miniperl
[Switching to thread 1 (process 12049 thread 0x1903)]
dyld: /Users/lshatzer/perl/bleadperl/./miniperl multiple
On Mon, Jun 11, 2001 at 06:43:43PM -0700, Wilfredo Sanchez wrote:
On Monday, June 11, 2001, at 02:24 PM, Jarkko Hietaniemi wrote:
Ho-hum. On closer inspection the dynaloader error messages look
much like
there's a big confusion going on: both the symbols of the newly
built
Looking at the GNUmakefile produced during Configure, I see this:
# The following are used to build and install shared libraries for
# dynamic loading.
LDDLFLAGS = -bundle -undefined suppress -L/usr/local/lib
SHRPLDFLAGS = -L/usr/local/lib
Ouch. This definitely isn't some irrelevant (test) failure.
I got this, too. From CrashCatcher:
**
Date/Time: 2001-06-11 13:30:00 -0700
PID: 13766
Command: miniperl
Exception: EXC_BAD_ACCESS (0x0001)
Codes: KERN_PROTECTION_FAILURE (0x0002) at 0x
Public service announcement: the development branch of Perl [1] now
builds out of the box in Mac OS X, with just Configure -de.
I integrated the various needed changes and Paul Schinder tested them
for me, kudos to Paul who never sleeps (he simply can't, given how
much he tests stuff).
Note
22 matches
Mail list logo
